Root code execution via unvalidated saveStaticConfig path
Published Apr 15, 2020 · Updated Nov 15, 2024
Directory traversal in Cisco UCS Director before 6.7.4.0 allows attackers to execute code as root through crafted REST API requests. The saveStaticConfig method uses a user-supplied path in file operations without validating traversal outside the intended directory. Cisco describes authenticated access, while ZDI reports no authentication requirement; successful exploitation runs code as root.
Summary
What happened
Directory traversal in Cisco UCS Director before 6.7.4.0 allows attackers to execute code as root through crafted REST API requests. The saveStaticConfig method uses a user-supplied path in file operations without validating traversal outside the intended directory. Cisco describes authenticated access, while ZDI reports no authentication requirement; successful exploitation runs code as root.
The record
- CVE
- CVE-2020-3248
- Published
- Apr 15, 2020
- Updated
- Nov 15, 2024
- Vendor
- ClamAV
- Product
- Cisco UCS Director
- Classifications
- CWE-20, CWE-22, T1190
- Attack vector
- network
- Privileges
- Unavailable
Timeline
How it unfolded
- Apr 15, 2020CVE publishedPublication date reported by the CVE source.
- Nov 15, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=n/a
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo