org.sonar.l10n.javascript.rules.javascript.S4507.html Maven / Gradle / Ivy

Go to download

Show more of this group Show more artifacts with this name
Show all versions of javascript-checks Show documentation

There is a newer version: 10.20.0.29356

Development tools and frameworks usually have options to make debugging easier for developers. Although these features are useful during
development, they should never be enabled for applications deployed in production. Debug instructions or error messages can leak detailed information
about the system, like the application’s path or file names.
Ask Yourself Whether

   The code or configuration enabling the application debug features is deployed on production servers or distributed to end users. 
   The application runs by default with debug features activated. 

There is a risk if you answered yes to any of those questions.
Recommended Secure Coding Practices
Do not enable debugging features on production servers or applications distributed to end users.
Sensitive Code Example
errorhandler Express.js middleware should not be used in production:
const express = require('express');
const errorhandler = require('errorhandler');

let app = express();
app.use(errorhandler()); // Sensitive

Compliant Solution
errorhandler Express.js middleware used only in development mode:
const express = require('express');
const errorhandler = require('errorhandler');

let app = express();

if (process.env.NODE_ENV === 'development') {
  app.use(errorhandler());
}

See

   OWASP - Top 10 2021 Category A5 - Security Misconfiguration 
   OWASP - Top 10 2017 Category A3 - Sensitive Data
  Exposure 
   CWE - CWE-489 - Active Debug Code 
   CWE - CWE-215 - Information Exposure Through Debug Information