Common Node.js security vulnerabilities in Node.js

Introduction

Node.js apps can have weak spots that let bad people cause trouble. Knowing these helps keep your app safe.

When building a web server that handles user data

When connecting to databases from your Node.js app

When accepting input from users or external sources

When deploying your app to the internet

When using third-party packages in your project

Syntax

Node.js

No specific code syntax applies here; this is about understanding common security issues in Node.js apps.

Security issues often come from how code is written or configured, not just syntax.

Always keep Node.js and packages updated to reduce risks.

Examples

These are common types of security problems you might find in Node.js apps.

Node.js

1. Injection attacks
2. Cross-Site Scripting (XSS)
3. Insecure deserialization
4. Using outdated packages
5. Improper error handling

Shows how unsafe string building can let attackers run harmful commands.

Node.js

Example: SQL Injection
const userInput = "' OR '1'='1";
const query = `SELECT * FROM users WHERE name = '${userInput}'`;
// This can let attackers get all users.

Sample Program

This example shows a basic Node.js server using Express and Helmet. Helmet helps protect against some common security issues by setting safe headers.

Node.js

import express from 'express';
import helmet from 'helmet';

const app = express();

// Use Helmet to set secure HTTP headers
app.use(helmet());

// Simple route
app.get('/', (req, res) => {
  res.send('Hello, secure world!');
});

app.listen(3000, () => {
  console.log('Server running on http://localhost:3000');
});

Important Notes

Always validate and sanitize user input to prevent injection attacks.

Keep dependencies updated to avoid known vulnerabilities.

Use security middleware like Helmet to add protection layers easily.

Summary

Node.js apps can have security risks if not careful.

Common issues include injection, XSS, and outdated packages.

Use good coding habits and tools to keep apps safe.

Practice

1. Which of the following is a common security vulnerability in Node.js applications?

easy

A. Memory Leak

B. SQL Injection

C. Slow Network

D. Syntax Error

Solution

1. Step 1: Understand common vulnerabilities

   SQL Injection is a well-known security risk where attackers inject malicious SQL code.

2. Step 2: Identify relevant options

   Memory leaks and slow networks are performance issues, syntax errors are coding mistakes, not security vulnerabilities.

3. Final Answer:

   SQL Injection -> Option B

4. Quick Check:

   Common Node.js security risk = SQL Injection [OK]

Hint: Security risks often involve data injection or unauthorized access [OK]

Common Mistakes:

• Confusing performance issues with security vulnerabilities
• Thinking syntax errors are security problems
• Ignoring injection attacks

2. Which syntax correctly prevents Cross-Site Scripting (XSS) in a Node.js Express app when rendering user input in a template?

easy

A. res.send(`${escape(userInput)}`);

B. res.render('page', { data: userInput });

C. res.send(`${userInput}`);

D. res.send(userInput);

Solution

1. Step 1: Identify safe rendering method

   Escaping user input before inserting into HTML prevents XSS attacks.

2. Step 2: Compare options

   Only res.send(`
   ${escape(userInput)}`); uses an escape function to sanitize input before sending.

3. Final Answer:

   res.send(`
   ${escape(userInput)}
   `); -> Option A

4. Quick Check:

   Escape user input to prevent XSS = res.send(`
   ${escape(userInput)}
   `); [OK]

Hint: Always escape user input before rendering in HTML [OK]

Common Mistakes:

• Sending raw user input directly in HTML
• Assuming template rendering auto-escapes input
• Not using escape functions

3. What will be the output of this Node.js code snippet vulnerable to prototype pollution?

const obj = {};
const payload = JSON.parse('{"__proto__": {"polluted": "yes"}}');
Object.assign(obj, payload);
console.log({}.polluted);

medium

A. Throws an error

B. undefined

C. null

D. "yes"

Solution

1. Step 1: Understand prototype pollution

   Assigning __proto__ property modifies the prototype of all objects.

2. Step 2: Analyze code behavior

   Object.assign merges payload into obj, changing Object prototype to include polluted property.

3. Step 3: Check console.log output

   Accessing {}.polluted reads from prototype, outputs "yes".

4. Final Answer:

   "yes" -> Option D

5. Quick Check:

   Prototype pollution sets property globally = "yes" [OK]

Hint: Prototype pollution changes all objects' properties unexpectedly [OK]

Common Mistakes:

• Expecting undefined instead of polluted value
• Not recognizing __proto__ effect
• Assuming error thrown on prototype pollution

4. Identify the security flaw in this Express middleware code:

app.use((req, res, next) => {
  const token = req.headers['authorization'];
  if (token) {
    req.user = jwt.verify(token, 'secret');
  }
  next();
});

medium

A. Not checking token expiration

B. Using synchronous jwt.verify instead of async

C. Missing error handling for invalid token

D. Not sanitizing user input

Solution

1. Step 1: Review token verification

   jwt.verify can throw if token is invalid, but no try-catch is used.

2. Step 2: Identify missing error handling

   Without try-catch, invalid tokens cause app crash or unhandled exceptions.

3. Final Answer:

   Missing error handling for invalid token -> Option C

4. Quick Check:

   Always catch errors from jwt.verify [OK]

Hint: Wrap jwt.verify in try-catch to handle invalid tokens [OK]

Common Mistakes:

• Ignoring exceptions from jwt.verify
• Assuming synchronous call is insecure
• Confusing input sanitization with token validation

5. You want to secure a Node.js app against outdated package vulnerabilities. Which approach is best to keep dependencies safe?

hard

A. Run 'npm audit' regularly and update vulnerable packages

B. Ignore warnings and only update major versions yearly

C. Manually edit package-lock.json to remove vulnerabilities

D. Use only packages without any dependencies

Solution

1. Step 1: Understand package vulnerability management

   npm audit scans for known vulnerabilities in dependencies.

2. Step 2: Choose best practice

   Regularly running npm audit and updating packages fixes security issues promptly.

3. Step 3: Evaluate other options

   Ignoring warnings risks attacks, manual edits are error-prone, and avoiding dependencies is impractical.

4. Final Answer:

   Run 'npm audit' regularly and update vulnerable packages -> Option A

5. Quick Check:

   Use npm audit and update often = Run 'npm audit' regularly and update vulnerable packages [OK]

Hint: Use npm audit and update packages regularly [OK]

Common Mistakes:

• Ignoring audit warnings
• Editing lock files manually
• Avoiding dependencies completely