Authenticated file read via URL fragment confusion
Published May 29, 2020 · Updated Aug 4, 2024
Arbitrary file read in Snyk Broker before 4.72.2 allows remote authenticated users to read files via crafted request URLs. The request filter validates a whitelisted path placed after a fragment identifier while forwarding the pre-fragment filePath value to the brokered service. Access to Snyk's internal network is required, and successful exploitation exposes readable files without modifying or interrupting the service.
Summary
What happened
Arbitrary file read in Snyk Broker before 4.72.2 allows remote authenticated users to read files via crafted request URLs. The request filter validates a whitelisted path placed after a fragment identifier while forwarding the pre-fragment filePath value to the brokered service. Access to Snyk's internal network is required, and successful exploitation exposes readable files without modifying or interrupting the service.
The record
- CVE
- CVE-2020-7648
- Published
- May 29, 2020
- Updated
- Aug 4, 2024
- Vendor
- Snyk
- Product
- Snyk Broker
- Classifications
- CWE-22, T1213.003
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- May 29, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=All versions before 4.72.2
What conditions does exploitation require?
What is affected?
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
- Snyk URL-fragment request exampleproof 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