Unauthenticated file disclosure via syslog.php path traversal
Published Feb 17, 2020 · Updated Aug 4, 2024
Path traversal in SyncServer S100 2.90.70.3, S200 1.30, S250 1.25, S300 2.65.0, and S350 2.80.1 allows remote attackers to read files. The syslog.php endpoint fails to sanitize traversal sequences in the FileName parameter before retrieving the requested file. No authentication or user interaction is required; public evidence establishes disclosure of files accessible to the web service but not file modification.
Summary
What happened
Path traversal in SyncServer S100 2.90.70.3, S200 1.30, S250 1.25, S300 2.65.0, and S350 2.80.1 allows remote attackers to read files. The syslog.php endpoint fails to sanitize traversal sequences in the FileName parameter before retrieving the requested file. No authentication or user interaction is required; public evidence establishes disclosure of files accessible to the web service but not file modification.
The record
- CVE
- CVE-2020-9030
- Published
- Feb 17, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-22, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 17, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- Symmetricom SyncServer path-traversal proof of conceptproof of concept · unverified
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