Sploit.io - Search

Product: u-boot, version: 2010.12

CVE-2019-6268

Severity: HIGH

Description: RAD SecFlow-2 devices with Hardware 0202, Firmware 4.1.01.63, and U-Boot 2010.12 allow URIs beginning with /.. for Directory Traversal, as demonstrated by reading /etc/shadow.

CVSS Score: N/A

Priority

D

CISA Data

EPSS Data

  • EPSS: 0.005060000
  • Percentile: 0.656520000
  • Date: 2026-02-11

ExploitDB

No data available.

HackerOne Data

  • Rank: 8686
  • Reports submitted count: 0
  • Unknown: 0
  • None: 0
  • Low: 0
  • Medium: 0
  • High: 0
  • Critical: 0

GitHub PoCs

    Nuclei Templates

    No data available.

    VulnCheck Data

    Affected Products:

    • n/a n/a - Versions: n/a

    References:

    Risk Assessment

    1. Risk Assessment
    The vulnerability CVE-2019-6268 is a Directory Traversal vulnerability present in RAD SecFlow-2 devices running Firmware 4.1.01.63 and utilizing U-Boot 2010.12. It allows attackers to access files outside of the intended webroot by crafting URIs beginning with "/..". The nature of this vulnerability is high risk because it directly impacts confidentiality. Successful exploitation allows an attacker to read sensitive files, such as /etc/shadow, which contains hashed passwords. The likelihood of exploitation is moderate to high, as path traversal vulnerabilities are relatively common and easily exploitable, particularly if the device is exposed to the network. The ease of exploitation is also relatively high, as the attack vector is network-based and does not require authentication. The business impact could be significant; compromised passwords could lead to further access and potentially full compromise of the device and network it protects. Confidentiality is the primary impact, but if attacker gains access to other configuration files, integrity could also be impacted. Availability is less directly impacted, though a resource intensive attack could potentially cause a denial-of-service. The CVSS v3.1 score is 7.5, indicating a High severity vulnerability.

    2. Potential Attack Scenarios
    An attacker, utilizing network access, can exploit this vulnerability to read the /etc/shadow file. The attack process begins with the attacker sending an HTTP request to the SecFlow-2 device, using a URI that starts with "/..". For example, the attacker could request `http://<SecFlow-2 IP Address>/.. /etc/shadow`. The SecFlow-2 device, due to insufficient URI sanitization, will traverse up one directory and then locate and return the contents of the /etc/shadow file. The attacker can then use tools to crack the hashed passwords within /etc/shadow, potentially gaining access to the device via SSH or other services. This provides a stepping stone for further network access, depending on the privileges associated with the compromised account. The potential outcome is complete compromise of the SecFlow-2 device and potential access to the network it is protecting.

    3. Mitigation Recommendations
    Immediate action should be taken to patch or upgrade the affected devices. Upgrade the RAD SecFlow-2 firmware to a version that addresses the directory traversal vulnerability. If a direct upgrade isn’t immediately possible, consider implementing a web application firewall (WAF) in front of the SecFlow-2 device to filter out requests containing "/.." in the URI. Implement strong input validation on the SecFlow-2 device to properly sanitize URIs and prevent directory traversal attempts. Restrict network access to the SecFlow-2 device, limiting it to trusted networks and hosts. Regularly monitor the SecFlow-2 device's logs for suspicious activity, specifically looking for requests containing "/..". Further resources can be found at: https://www.owasp.org/index.php/Path_Traversal and https://packetstormsecurity.com/files/177440/RAD-SecFlow-2-Path-Traversal.html.

    4. Executive Summary
    RAD SecFlow-2 devices with Firmware 4.1.01.63 are vulnerable to a Directory Traversal attack (CVE-2019-6268). This vulnerability allows attackers to read sensitive files, such as the password file, potentially leading to full compromise of the device and its network connections. The risk is high due to the ease of exploitation and the potential impact on confidentiality. We recommend immediate patching or upgrading of the SecFlow-2 firmware. If patching is delayed, implementing a Web Application Firewall and restricting network access are crucial steps. Addressing this vulnerability is important to protect the SecFlow-2 device, its data, and the wider network it secures from unauthorized access and potential disruption. Prompt action minimizes the risk of a security breach and protects our organization’s valuable assets.