Detection Guidance

This vulnerability involves publicly accessible endpoints in the Securly Chrome Extension version 3.0.7 that allow unauthenticated access to sensitive data, including SHA-1 hashes obfuscated with a simple Caesar cipher.

To detect this vulnerability on your network or system, you can scan for the presence of the Securly Chrome Extension version 3.0.7 and attempt to access its exposed endpoints without authentication.

Since the vulnerability involves HTTP endpoints exposing sensitive data, network traffic monitoring tools like Wireshark or tcpdump can be used to capture and analyze traffic to identify unencrypted requests to these endpoints.

Suggested commands include:

• Using curl to test access to known endpoints: curl http://localhost:<port>/<endpoint>
• Using nmap to scan for open HTTP ports on the system: nmap -p 80,8080 <target-ip>
• Using tcpdump to capture HTTP traffic: sudo tcpdump -i <interface> tcp port 80 -w capture.pcap
• Using Wireshark to analyze captured traffic for unencrypted sensitive data.

Useful 0 Not Useful 0

Compliance Impact

The vulnerability exposes sensitive data through publicly accessible endpoints without authentication, which could lead to unauthorized access to protected information.

Such exposure and inadequate protection of sensitive data may result in non-compliance with data protection regulations like GDPR and HIPAA, which require strict controls to safeguard personal and sensitive information.

Useful 0 Not Useful 0

Executive Summary

Version 3.0.7 of the Securly Chrome Extension has multiple publicly accessible endpoints that allow anyone to access sensitive data without authentication.

The sensitive data exposed are SHA-1 hashes that are only lightly obfuscated using a simple Caesar cipher, which can be easily reversed to reveal the original hash values and thus the protected data.

Useful 0 Not Useful 0

Impact Analysis

This vulnerability can lead to unauthorized access to sensitive information because the exposed SHA-1 hashes can be easily decoded.

Attackers could recover protected data by reversing the weak obfuscation, potentially leading to data breaches or misuse of sensitive information.

Useful 0 Not Useful 0

Mitigation Strategies

Immediate mitigation steps include:

• Disable or uninstall version 3.0.7 of the Securly Chrome Extension until a patched version is available.
• Restrict network access to the exposed endpoints to prevent unauthenticated access.
• Monitor network traffic for suspicious access to the vulnerable endpoints.
• Apply any available updates or patches from the vendor addressing this vulnerability.

Useful 0 Not Useful 0