CVE-2024-28995 is a path traversal vulnerability vulnerability in SolarWinds Serv-U. CISA added it to the Known Exploited Vulnerabilities catalogue on 17 July 2024, which means attackers have used it in real attacks. SolarWinds Serv-U contains a path traversal vulnerability that allows an attacker access to read sensitive files on the host machine.
What makes path traversal dangerous in a file-transfer product
Path traversal is dangerous because it can let an attacker step outside an intended file boundary and reach files the application should never expose. In a managed file-transfer product, that can turn a single request into access to local configuration, logs, keys, and other sensitive host data.
In practice, the weakness is not just that files can be read. It is that a product designed to broker trust between users, folders, and automation may accidentally become a disclosure path into the underlying server itself.
How exposure usually occurs
Exposure starts with asset scope, because organisations must first know where SolarWinds Serv-U is deployed and whether it is reachable from untrusted networks. Internet-exposed instances deserve the fastest review, especially when the product supports external file exchange or remote administration.
For a term like this, vendor advisory details and the NIST National Vulnerability Database or the CVE Program are the authoritative places to confirm record details, while a vulnerability-management process determines which instances are still exposed and what compensating controls are in place.
Because the issue was added to CISA’s KEV catalogue, it should be treated as actively exploited rather than as a purely theoretical flaw. That changes priority: exposure review, isolation, and remediation become time-sensitive operations, not routine backlog work.
Remediation and compensating controls
The safest response is to remove the vulnerable condition by applying the vendor’s fixed guidance as soon as the environment allows. Until then, reduce exposure by restricting who can reach the service, tightening trust boundaries around file handling, and removing unnecessary access paths into the host.
When patching is delayed, compensating controls matter most where the service is internet-facing or where sensitive data is stored on the same system. If the product cannot be isolated cleanly, treat it as a high-risk exception rather than a low-severity maintenance item.
Operationally, the point is not to “wait for the patch window”, but to narrow the blast radius so a traversal bug cannot become full host disclosure.
Detection and post-exploitation review
Detection should focus on signs that files outside the expected transfer directories were accessed, especially configuration files, application secrets, and diagnostic artefacts. Review web and application logs for unusual path syntax, repeated failed reads, and requests that do not match normal user workflow.
After remediation, organisations should still assume that sensitive host content may have been exposed and review for follow-on compromise. The right response is not only to close the vulnerability, but also to check whether leaked material could enable later access elsewhere in the environment.
If the product stored credentials, tokens, certificates, or session-related material on the host, those secrets should be reviewed and rotated where compromise is plausible. A disclosure bug often becomes an identity problem after the first successful read.
Risk and Threat Considerations
This vulnerability matters because file disclosure in a transfer platform can expose more than documents. Attackers may use the read access to collect configuration data, secrets, and internal paths that support follow-on intrusion or lateral movement.
Failure mechanism: Path normalization or file-path validation fails, allowing crafted input to resolve outside the intended directory and reveal local files on the server.
Impact: Sensitive files may be read, enabling credential theft, environment mapping, and downstream compromise of adjacent systems or accounts.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
NIST SP 800-53 Rev 5, CIS Controls v8 and OWASP ASVS set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-53 Rev 5 | SI-10 — Information Input Validation | Path traversal is prevented by validating and constraining file-path input. |
| SI-4 — System Monitoring | Monitoring is needed to spot anomalous file access and traversal attempts. | |
| Recommendation — Enforce SI-10 to reject path input that can escape the intended directory boundary. Use SI-4 to alert on abnormal file-path requests and unexpected local-file reads. | ||
| CIS Controls v8 | CIS-16 — Application Software Security | Application flaws like traversal are addressed through secure coding and validation practices. |
| CIS-13 — Network Monitoring and Defense | Exposure and exploitation of a public-facing service require traffic and activity monitoring. | |
| Recommendation — Apply CIS-16 to harden file-handling code and prevent unsafe path resolution. Use CIS-13 to detect suspicious requests against exposed Serv-U instances. | ||
| OWASP ASVS | V4 — API and Web Service | Traversal in a web-exposed service is controlled through request handling and access restrictions. |
| Recommendation — Validate file-oriented requests under V4 to ensure path access stays inside approved boundaries. | ||
Practitioner Guidance
Why practitioners should care: Treat KEV-listed path traversal in a file-exposure product as a disclosure event, not just an application bug. The main risk is often the material that sits beside the application, including keys, configs, and operational metadata.
What to watch for: Review whether the instance is internet-facing, whether logs show anomalous file paths, and whether any exposed host material could be reused elsewhere. If exposure is confirmed or suspected, assume the incident may extend beyond the original server.
Related resources from NHI Mgmt Group
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on October 17, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org