Compliance Impact

The vulnerability causes the Graph Explorer proxy server to silently fall back from HTTPS to HTTP when certificate files are missing, resulting in sensitive information being transmitted in cleartext. This exposure of sensitive data through interception can lead to non-compliance with data protection standards and regulations such as GDPR and HIPAA, which require secure transmission of personal and sensitive information.

To maintain compliance, it is critical to upgrade to Graph Explorer version 3.0.1 or later, which fixes this issue by preventing the fallback to HTTP and ensuring secure HTTPS communication.

Useful 0 Not Useful 0

Executive Summary

This vulnerability occurs in the Graph Explorer proxy server before version 3.0.1, where if HTTPS is enabled but the required certificate files are missing, the server silently falls back to using HTTP instead of HTTPS.

As a result, sensitive information that was intended to be transmitted securely over HTTPS can be sent in cleartext over HTTP, making it vulnerable to interception by remote threat actors.

The issue affects versions from 1.1.0 up to but not including 3.0.1 and has been fixed in version 3.0.1.

Useful 0 Not Useful 0

Impact Analysis

This vulnerability can lead to the exposure of sensitive information because data that should be encrypted and protected by HTTPS is instead transmitted in plaintext over HTTP.

Attackers who intercept this unencrypted traffic can obtain confidential data, which could lead to data breaches, loss of privacy, and potential misuse of the intercepted information.

Users of affected Graph Explorer versions are advised to upgrade to version 3.0.1 or later to prevent this risk.

Useful 0 Not Useful 0

Detection Guidance

This vulnerability can be detected by monitoring network traffic for unexpected fallback from HTTPS to HTTP when using Graph Explorer versions prior to 3.0.1. Specifically, if requests intended to be sent over HTTPS are instead transmitted in cleartext over HTTP, this indicates the vulnerability is present.

To detect this on your system, you can check if your Graph Explorer deployment is using HTTPS properly and verify that certificate files are correctly loaded. Additionally, ensure that the HOST environment variable is set in Docker run commands to enable proper certificate generation.

Suggested commands include using network monitoring tools like tcpdump or Wireshark to capture traffic and filter for HTTP requests to the Graph Explorer server, for example:

• tcpdump -i <interface> 'tcp port 80 and host <graph-explorer-host>'
• wireshark filter: http && ip.addr == <graph-explorer-host>

Also, inspect your Docker container logs and configuration to confirm that HTTPS is enabled and certificates are properly mounted and recognized.

Useful 0 Not Useful 0

Mitigation Strategies

The primary and recommended mitigation is to upgrade Graph Explorer to version 3.0.1 or later, where this issue has been fixed.

If upgrading immediately is not possible, you should:

• Verify that your deployment is configured to use HTTPS and that certificate files are present and correctly loaded.
• Ensure the HOST environment variable is set in Docker run commands to enable proper certificate generation.
• Avoid using non-default configuration paths that rely on automatic self-signed certificate generation, as this can cause fallback to HTTP.

Useful 0 Not Useful 0