Input validation and sanitization in Node.js - Step-by-Step Execution

Concept Flow - Input validation and sanitization

Receive user input

↓

Validate input format?

No→Reject input with error

Yes↓

Sanitize input to remove bad data

↓

Use cleaned input safely

↓

Respond to user

Input is first checked if it meets rules, then cleaned to remove harmful parts before use.

Execution Sample

Node.js

import { check, validationResult } from 'express-validator';

app.post('/submit', [
  check('email').trim().isEmail().normalizeEmail(),
  check('age').trim().isInt({ min: 1 }).toInt()
], (req, res) => {
  const errors = validationResult(req);
  if (!errors.isEmpty()) {
    return res.status(400).json({ errors: errors.array() });
  }
  // Use cleaned input safely, e.g., req.body.age is now a number
  res.json({ message: 'Success', data: req.body });
});

This code validates and sanitizes 'email' (trims, checks format, normalizes) and 'age' (trims, checks positive integer, converts to int) before processing. Invalid input is rejected with errors.

Execution Table

Step	Action	Input Example	Validation Result	Sanitization Result	Next Step
1	Receive input	{ email: '[e-mail]', age: '25' }	Not checked yet	Not sanitized yet	Validate input
2	Validate 'email'	[e-mail]	Valid email	N/A	Validate 'age'
3	Validate 'age'	25	Valid integer >=1	N/A	Sanitize input
4	Sanitize 'email'	[e-mail]	Valid	[e-mail]	Sanitize 'age'
5	Sanitize 'age'	25	Valid	25	Use cleaned input
6	Use input safely	{ email: '[e-mail]', age: 25 }	Valid	Cleaned	Respond to user
7	Respond	Success message	N/A	N/A	End

💡 Input rejected if validation fails; otherwise sanitized and used safely.

Variable Tracker

Variable	Start	After Validation	After Sanitization	Final
email	undefined	[e-mail] (valid)	[e-mail] (clean)	[e-mail]
age	undefined	'25' (valid)	25 (number)	25
errors	undefined	empty (no errors)	empty	empty

Key Moments - 3 Insights

Why do we check validation before sanitization?

Validation ensures input meets rules before cleaning. See execution_table steps 2 and 3 where validation happens first to catch bad input early.

What happens if validation fails?

Input is rejected immediately with an error. This is shown in the exit_note and implied by the flow after step 1 if validation is No.

Why convert 'age' from string to number during sanitization?

Sanitization cleans and converts input to correct types for safe use. See variable_tracker where 'age' changes from string '25' to number 25 after sanitization.

Visual Quiz - 3 Questions

Look at the execution_table at step 3, what is the validation result for 'age'?

A Invalid integer

B Valid integer >=1

C Missing value

D Not checked yet

💡 Hint

Check the 'Validation Result' column at step 3 in execution_table.

At which step does the input get sanitized?

A Step 2

B Step 6

C Step 4

D Step 1

💡 Hint

Look for 'Sanitize input' action in execution_table rows.

If the email was 'bad-email', what would happen at step 2?

A Validation fails and input is rejected

B Validation passes

C Sanitization fixes it automatically

D Input is accepted without changes

💡 Hint

Refer to key_moments about validation failing and exit_note.

Concept Snapshot

Input validation checks if data meets rules (like email format).
Sanitization cleans data (removes bad parts, converts types).
Validate first to catch errors early.
Sanitize before using input to keep app safe.
Reject invalid input to avoid problems.
Use libraries like express-validator in Node.js.

Full Transcript

Input validation and sanitization in Node.js means first checking if user data fits expected rules, like a proper email or positive number. If it passes, we clean the data to remove harmful parts or convert types. This process helps keep the app safe and working well. The flow starts by receiving input, validating each field, then sanitizing it, and finally using the cleaned data. If validation fails, the input is rejected immediately. This step-by-step ensures only good data is processed.

Practice

1. What is the main purpose of input validation in a Node.js application?

easy

A. To check if the input data is correct and safe before processing

B. To store user data in the database

C. To format the output data for display

D. To speed up the server response time

Solution

1. Step 1: Understand input validation

   Input validation ensures that the data received from users meets expected rules and is safe to use.

2. Step 2: Identify the purpose in Node.js

   In Node.js, input validation prevents bad or harmful data from causing errors or security issues.

3. Final Answer:

   To check if the input data is correct and safe before processing -> Option A

4. Quick Check:

   Input validation = check data safety [OK]

Hint: Validation means checking data correctness and safety [OK]

Common Mistakes:

• Confusing validation with data storage
• Thinking validation formats output
• Assuming validation improves speed

2. Which of the following is the correct way to import the express-validator middleware in a Node.js file using ES modules?

easy

A. const { check } = require('express-validator');

B. import check from 'express-validator';

C. const check = require('express-validator/check');

D. import { check } from 'express-validator';

Solution

1. Step 1: Identify modern import syntax

   Node.js with ES modules uses import { check } from 'express-validator'; to import named exports.

2. Step 2: Check other options

   const { check } = require('express-validator'); uses CommonJS require but destructuring is possible only if CommonJS is used; import check from 'express-validator'; imports default which express-validator does not export; const check = require('express-validator/check'); uses a wrong path.

3. Final Answer:

   import { check } from 'express-validator'; -> Option D

4. Quick Check:

   Use ES module import for express-validator [OK]

Hint: Use ES module import syntax with curly braces for named exports [OK]

Common Mistakes:

• Using require instead of import in ES modules
• Importing default instead of named export
• Using incorrect module paths

3. Consider this Node.js code snippet using express-validator:

app.post('/submit', [
  check('email').isEmail(),
  check('age').isInt({ min: 18 })
], (req, res) => {
  const errors = validationResult(req);
  if (!errors.isEmpty()) {
    return res.status(400).json({ errors: errors.array() });
  }
  res.send('Data is valid');
});

What will be the response if the user sends { "email": "userexample.com", "age": 17 }?

medium

A. Status 400 with error about missing fields

B. Status 400 with errors about invalid email and age

C. Status 500 server error

D. Status 200 with message 'Data is valid'

Solution

1. Step 1: Analyze validation rules

   The code checks if 'email' is a valid email and 'age' is an integer >= 18.

2. Step 2: Check input values

   The email 'userexample.com' is missing '@', so invalid. Age 17 is less than 18, so invalid.

3. Final Answer:

   Status 400 with errors about invalid email and age -> Option B

4. Quick Check:

   Invalid email and age cause 400 error [OK]

Hint: Invalid inputs trigger 400 with error details [OK]

Common Mistakes:

• Assuming invalid data passes validation
• Confusing status codes
• Ignoring validationResult usage

4. You wrote this code to sanitize input but it doesn't remove spaces as expected:

app.post('/data', [
  check('username').trim().escape()
], (req, res) => {
  // ...
});

What is the likely reason the spaces are not removed?

medium

A. You must call sanitize() before trim()

B. escape() removes spaces but trim() does not

C. The trim() method removes spaces only from start and end, not inside the string

D. The check() function does not support trim()

Solution

1. Step 1: Understand trim() behavior

   The trim() method removes whitespace only from the start and end of a string, not inside it.

2. Step 2: Check escape() effect

   escape() converts special characters but does not remove spaces inside the string.

3. Final Answer:

   The trim() method removes spaces only from start and end, not inside the string -> Option C

4. Quick Check:

   trim() trims edges, not inner spaces [OK]

Hint: trim() only removes spaces at string ends [OK]

Common Mistakes:

• Expecting trim() to remove all spaces
• Misunderstanding escape() purpose
• Thinking check() lacks trim() support

5. You want to create a Node.js API endpoint that accepts a username and email. The username must be alphanumeric and trimmed, and the email must be valid and normalized. Which express-validator chain correctly applies validation and sanitization?

hard

A. [ check('username').trim().isAlphanumeric(), check('email').normalizeEmail().isEmail() ]

B. [ check('username').isAlphanumeric().trim(), check('email').isEmail().normalizeEmail() ]

C. [ check('username').escape().isAlphanumeric(), check('email').isEmail().trim() ]

D. [ check('username').isAlphanumeric().escape(), check('email').trim().normalizeEmail() ]

Solution

1. Step 1: Validate username and email correctly

   Username must be alphanumeric and trimmed, so trim() before or after is okay but isAlphanumeric() must check the trimmed string. Email must be checked with isEmail() and normalized with normalizeEmail().

2. Step 2: Analyze options

   [ check('username').trim().isAlphanumeric(), check('email').normalizeEmail().isEmail() ] applies trim() before isAlphanumeric() which ensures validation on trimmed string; [ check('username').isAlphanumeric().trim(), check('email').isEmail().normalizeEmail() ] applies isAlphanumeric() before trim(), which may validate untrimmed input; also, normalizeEmail() should come before isEmail() to validate normalized email; [ check('username').escape().isAlphanumeric(), check('email').isEmail().trim() ] escapes username unnecessarily and trims email which is not needed; [ check('username').isAlphanumeric().escape(), check('email').trim().normalizeEmail() ] escapes username and trims email incorrectly.

3. Final Answer:

   [ check('username').trim().isAlphanumeric(), check('email').normalizeEmail().isEmail() ] -> Option A

4. Quick Check:

   Trim before validation for username; normalize before validation for email [OK]

Hint: Trim before validation for username; normalize before validation for email [OK]

Common Mistakes:

• Applying sanitization after validation incorrectly
• Using escape() unnecessarily
• Trimming email instead of normalizing