Partial file disclosure via unfiltered Accept header
Published May 29, 2020 · Updated Aug 4, 2024
Arbitrary file read in Snyk Broker before 4.79.0 allows remote authenticated users to disclose file fragments through GitHub commit history. The Broker allowlist accepted GitHub Commits API requests without constraining the Accept header, enabling patch media types to return portions of repository files. Exploitation requires access to Snyk's internal network and yields partial disclosure without reported modification or service interruption.
Summary
What happened
Arbitrary file read in Snyk Broker before 4.79.0 allows remote authenticated users to disclose file fragments through GitHub commit history. The Broker allowlist accepted GitHub Commits API requests without constraining the Accept header, enabling patch media types to return portions of repository files. Exploitation requires access to Snyk's internal network and yields partial disclosure without reported modification or service interruption.
The record
- CVE
- CVE-2020-7651
- Published
- May 29, 2020
- Updated
- Aug 4, 2024
- Vendor
- Snyk
- Product
- Snyk Broker
- Classifications
- CWE-22
- Attack vector
- network
- Privileges
- authenticated
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.79.0
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
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