Skip to main content

Technical information leak - Content response

Description

It is possible to obtain technical information such as:

  • System component versions (HTTP headers, service banner, etc.)
  • Specific information about the configuration of server components (php.ini, web.config)

Impact

Gather technical information to craft new attack vectors.

Recommendation

Remove web services and files that exposes technical information.

Threat

Anonymous attacker from the Internet.

Expected Remediation Time

⌚ 60 minutes.

Score

Default score using CVSS 3.1. It may change depending on the context of the vulnerability.

Base

  • Attack vector: N
  • Attack complexity: L
  • Privileges required: N
  • User interaction: N
  • Scope: U
  • Confidentiality: L
  • Integrity: L
  • Availability: N

Temporal

  • Exploit code madurity: X
  • Remediation level: X
  • Report confidence: X

Result

  • Vector string: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N/E:X/RL:X/RC:X
  • Score:
    • Base: 6.5
    • Temporal: 6.5
  • Severity:
    • Base: Medium
    • Temporal: Medium

Code Examples

Compliant code

The source code does not contain functions or files that expose sensitive information like configuration settings

function debug_to_console($data) {
$output = $data;
if (is_array($output))
$output = implode(',', $output);
echo "Output message";
}

Non compliant code

The source code includes code to debug the php.ini configuration files

function debug_to_console($data) {
$output = $data;
if (is_array($output))
$output = implode(',', $output);
echo "<script>console.log('Debug Objects: " . $output . "' );</script>";
}

debug_to_console(phpinfo());

Requirements