CVE-2019-25355

7.5

Genivia · gSOAP

gSOAP 2.8 contains a directory traversal vulnerability that allows unauthenticated attackers to retrieve sensitive system files via crafted HTTP requests.

Executive summary

A directory traversal vulnerability in Genivia gSOAP 2.8 allows unauthenticated remote attackers to access sensitive system files, posing a significant risk to information confidentiality.

Vulnerability

The application is susceptible to a path traversal flaw (CWE-22) in its HTTP handling logic, which permits an unauthenticated attacker to bypass directory restrictions. By sending a crafted GET request containing multiple double-dot sequences, an attacker can access arbitrary files on the underlying host system, such as /etc/passwd.

Business impact

Successful exploitation of this vulnerability can lead to the unauthorized disclosure of sensitive configuration files, credentials, or system data. Given the CVSS score of 7.5, this high-severity flaw carries significant risk, as it provides attackers with critical information that can be used to facilitate further system compromise or lateral movement.

Remediation

Immediate Action: Update the gSOAP toolkit to the latest available version provided by Genivia, as vendor-supplied patches are the only definitive resolution.

Proactive Monitoring: Review web server access logs for anomalous GET requests containing repeated "../" sequences, which are indicators of directory traversal attempts.

Compensating Controls: Deploy a Web Application Firewall (WAF) with rules configured to inspect and block HTTP requests containing path traversal characters or suspicious directory navigation patterns.

Exploitation status

Public Exploit Available: Yes, a published proof-of-concept exploit is available via Exploit-DB (EDB-ID 47653).

Analyst recommendation

Organizations utilizing gSOAP 2.8 must prioritize the application of vendor updates to remediate this directory traversal flaw immediately. The presence of a public proof-of-concept significantly lowers the barrier to entry for potential attackers, making the immediate implementation of patching or compensating WAF controls essential to protecting the confidentiality of the affected host environment.

Sources

Originally found and disclosed by Numan Türle, per the CVE Program record.