Práticas de Codificação Segura em Node.js
Implemente boas práticas para evitar vulnerabilidades comuns, como XSS, CSRF e injeção de SQL, no seu código Node.js.
Práticas de Codificação Segura em Node.js é uma aula grátis de Node.js Backend Development Bootcamp no CoddyKit. Esta é a aula 2 de 4. Você pode ler a aula completa abaixo gratuitamente — depois pratica ao vivo no navegador com um editor de código integrado e um tutor de IA 24/7. Faz parte do caminho de aprendizado de Node.js Backend Development Bootcamp, e seu progresso é sincronizado entre a web e o app CoddyKit. O curso de Node.js Backend Development Bootcamp inclui 4 aulas no total.
Partes desta aula ainda não foram traduzidas e aparecem em inglês.
Why Secure Coding Matters
Welcome! In this lesson, we'll dive into critical secure coding practices for Node.js. Writing secure code is just as important as writing functional code.
Understanding and preventing common vulnerabilities protects your application and your users from malicious attacks.
- Data Breaches: Exposed sensitive information.
- Service Downtime: Attacks can crash your application.
- Reputation Damage: Loss of user trust.
Cross-Site Scripting (XSS)
Cross-Site Scripting (XSS) is a common web vulnerability where attackers inject malicious scripts (usually JavaScript) into web pages viewed by other users.
When a user's browser loads the affected page, the malicious script executes, potentially stealing cookies, session tokens, or altering page content.
- Reflected XSS: Script immediately executed from user input.
- Stored XSS: Malicious script saved in database, then served to users.
- DOM-based XSS: Vulnerability in client-side code modifying the DOM.
Prevent XSS: Escape Output
The primary defense against XSS is to never trust user input and always escape it before rendering it to HTML.
This means converting characters like <, >, &, and " into their HTML entity equivalents (e.g., <, >). This way, the browser interprets them as text, not executable code.
Try running this example:
function escapeHtml(str) {
return str
.replace(/&/g, "&")
.replace(/</g, "<")
.replace(/>/g, ">")
.replace(/"/g, """)
.replace(/'/g, "'");
}
const userInput = "<h1>Hello</h1><script>alert('XSS!');</script>";
const safeOutput = escapeHtml(userInput);
console.log("Original Input:\n", userInput);
console.log("\nEscaped Output (safe for HTML):\n", safeOutput);Prevent XSS: CSP
Beyond escaping, a Content Security Policy (CSP) adds another layer of defense against XSS.
CSP is an HTTP header that tells browsers which dynamic resources (scripts, styles, images) are allowed to load and from where. It can significantly mitigate the impact of XSS attacks by blocking unauthorized script execution.
Example header: Content-Security-Policy: default-src 'self'; script-src 'self' trusted.cdn.com;
SQL Injection Explained
SQL Injection (SQLi) is a web security vulnerability that allows an attacker to interfere with the queries an application makes to its database.
By injecting malicious SQL code into input fields, an attacker can trick the database into executing unintended commands, such as revealing sensitive data, modifying data, or even deleting tables.
A common example is altering a login query to bypass authentication without knowing the password.
Prevent SQLi: Parameterized Queries
The most effective way to prevent SQL Injection is by using parameterized queries (also known as prepared statements).
Instead of directly embedding user input into the SQL string, you use placeholders for values. The database then treats these placeholders as data, not as executable SQL code, preventing any malicious injection.
ORMs (Object-Relational Mappers) like Mongoose for MongoDB or Sequelize for SQL databases handle this automatically.
/*
This is a conceptual example for parameterized queries.
In a real app, you'd use a database driver or ORM (e.g., 'pg' for PostgreSQL).
*/
function executeSafeQuery(dbClient, userId) {
// Using a placeholder (?) ensures the input is treated as data, not code.
const query = "SELECT * FROM users WHERE id = ?";
console.log(`Executing SQL: "${query}" with param: "${userId}"`);
// In a real scenario, dbClient.query would execute this safely.
}
// Mock database client for demonstration purposes
const mockDbClient = {
query: (sql, params, callback) => {
// Simulate actual query execution logic here
console.log(" (Mock DB: Input handled safely)");
callback(null, [{ id: params, name: "John Doe" }]);
}
};
const maliciousUserId = "1 OR 1=1"; // This would be dangerous if not parameterized
const safeUserId = "1";
console.log("Attempting a 'malicious' ID (will be treated as a string value): ");
executeSafeQuery(mockDbClient, maliciousUserId);
console.log("\nAttempting a safe ID: ");
executeSafeQuery(mockDbClient, safeUserId);Cross-Site Request Forgery (CSRF)
Cross-Site Request Forgery (CSRF) is an attack that tricks a logged-in user into performing an unintended action on a web application.
Imagine you're logged into your bank. An attacker sends you a malicious link (e.g., in an email). If you click it, the attacker's site can make a request to your bank using your authenticated session, forcing you to transfer money without your knowledge.
The key is that the browser automatically sends your session cookies with the request to the bank's domain.
Prevent CSRF: CSRF Tokens
To prevent CSRF, we use CSRF tokens. A unique, unpredictable token is generated by the server for each user session and embedded in forms or headers.
When the user submits a request, the server verifies if the submitted token matches the one stored in the user's session. If they don't match, the request is rejected.
Since an attacker cannot know or forge this unique token for another user, they cannot trick the user into making a valid request.
/*
This is a conceptual example for CSRF token handling.
It is not runnable as a standalone script without a web server (e.g., Express).
*/
// 1. Server generates and stores a token in the user's session:
function generateCsrfToken() {
// In a real app, use a crypto-secure random string generator.
return Math.random().toString(36).substring(2, 15) + Math.random().toString(36).substring(2, 15);
}
const userSession = { id: "user123", csrfToken: null };
userSession.csrfToken = generateCsrfToken();
console.log("Server generated CSRF token for user:", userSession.csrfToken);
// 2. Server embeds this token in forms sent to the client:
const formHtml = `<form action="/transfer" method="POST">
<input type="hidden" name="_csrf" value="${userSession.csrfToken}">
<input type="number" name="amount">
<button type="submit">Transfer</button>
</form>`;
console.log("\nForm snippet with token (sent to client):\n", formHtml);
// 3. On submission, the server validates the token:
function validateCsrfToken(submittedToken, sessionToken) {
return submittedToken === sessionToken;
}
const userSubmittedToken = userSession.csrfToken; // Simulate valid submission
const attackerSubmittedToken = "fake_token_from_attacker";
console.log("\nValidation results:");
console.log(" Valid submission:", validateCsrfToken(userSubmittedToken, userSession.csrfToken));
console.log(" Attacker's submission:", validateCsrfToken(attackerSubmittedToken, userSession.csrfToken));Other Security Headers
Beyond the core vulnerabilities, several other HTTP security headers can enhance your Node.js application's security:
X-Content-Type-Options: nosniff: Prevents browsers from "sniffing" a response's content type, which can prevent XSS attacks.X-Frame-Options: DENY: Prevents your site from being embedded in an<iframe>, protecting against clickjacking attacks.Strict-Transport-Security (HSTS): Forces browsers to only connect to your site using HTTPS, preventing downgrade attacks.
These headers are typically set using middleware in frameworks like Express.js.
Security Vulnerability Check
Which of the following is the most effective defense against SQL Injection attacks?
Secure Coding Recap
Great job! You've learned about crucial secure coding practices in Node.js.
- XSS: Prevent by escaping all user-generated content before rendering to HTML, and use CSP.
- SQL Injection: Prevent by always using parameterized queries or ORMs.
- CSRF: Prevent by implementing CSRF tokens for state-changing requests.
- Remember to also use other security headers like
X-Content-Type-OptionsandX-Frame-Optionsfor a more robust defense.
Always assume user input is malicious and validate/sanitize/escape it appropriately!
Perguntas Frequentes
A aula “Práticas de Codificação Segura em Node.js” é grátis?
Sim — o texto completo de “Práticas de Codificação Segura em Node.js” é grátis para ler aqui na web. Para praticá-la interativamente (um editor de código integrado e um tutor de IA 24/7) e desbloquear o restante do curso de Node.js Backend Development Bootcamp, atualize para CoddyKit PRO. O curso de Node.js Backend Development Bootcamp inclui 4 aulas no total.
O que vou aprender em “Práticas de Codificação Segura em Node.js”?
Implemente boas práticas para evitar vulnerabilidades comuns, como XSS, CSRF e injeção de SQL, no seu código Node.js. Você pratica Node.js Backend Development Bootcamp com código prático que executa diretamente no navegador, e um tutor de IA 24/7 responde suas dúvidas enquanto trabalha na aula.
Preciso ter experiência prévia para começar Node.js Backend Development Bootcamp?
Nenhuma experiência prévia é necessária. Node.js Backend Development Bootcamp no CoddyKit é estruturado para alunos iniciantes até avançados, então você pode começar aqui ou desde o início e aprender no seu ritmo. Esta é a aula 2 de 4.
Quanto tempo leva a aula “Práticas de Codificação Segura em Node.js”?
A maioria das aulas CoddyKit leva cerca de 5–10 minutos. Cada uma é compacta e interativa, então você faz progresso constante e retoma exatamente de onde parou entre web e app.
Posso escrever e executar código nesta aula de Node.js Backend Development Bootcamp?
Sim. Cada aula de Node.js Backend Development Bootcamp inclui um editor de código integrado, então você escreve e executa código real direto no navegador e recebe feedback de IA instantaneamente — nenhuma configuração local necessária.
Todas as aulas deste curso
- Entendendo os 10 Principais Riscos da OWASP
- Práticas de Codificação Segura em Node.js
- Criptografia e Hashing de Dados
- Limitação de taxa e proteção contra força bruta