Description

The application uses console functions: log, info, warning. The usage of these functions in productions environments may lead to information leakages and reveal vulnerable methods, technologies, or logic.

Impact

Gather technical information to craft more complex attack vectors.

Recommendation

Avoid the use of console functions in production environments. Instead, encourage the use of logs to register errors and exceptional events

Threat

Authenticated attacker from the Internet.

Expected Remediation Time

⏱️ 15 minutes.

Details

In front-end programming, JavaScript's Console object provides access to the browser's debugging console[^1]. Arguments passed to log, warn and error methods are visible to the user that is using the website, it's also visible to attackers.

As per Fluid Attacks' criteria[^2] the application must not disclose internal system information such as stack traces because this information can be leveraged to further exploit other vulnerabilities.

Developers tend to do debugging the following way:

try { /* Business logic code goes here ... */ }
catch (err) {
  console.error(err);
}

But this ends in lots of information that attackers use to better understand the inner workings on the system, aiding them in creating and improving attack vectors.

Error: <rect> attribute x: Expected length, "NaN".
(anonymous) @ cdnjs.cloudflare.com/ajax/libs/d3/5.16.0/d3.min.js:2
Error: <rect> attribute y: Expected length, "NaN".
(anonymous) @ cdnjs.cloudflare.com/ajax/libs/d3/5.16.0/d3.min.js:2
Error: <rect> attribute transform: Expected number, "rotate(NaN, NaN, NaN)".
...

Requirements

Fixes