Arbitrary file reads via permissive proxy allowlist
Published May 29, 2020 · Updated Aug 4, 2024
Path traversal in Snyk Broker 4.72.0 through 4.73.0 allows remote authenticated users to read arbitrary JSON and YAML files through proxied requests. The affected client templates authorize wildcard repository-content paths based only on a .json, .yaml, or .yml suffix, so crafted paths pass the request allowlist. Access to the private Broker tunnel is required, and exploitation exposes matching files readable with the configured integration credentials.
Summary
What happened
Path traversal in Snyk Broker 4.72.0 through 4.73.0 allows remote authenticated users to read arbitrary JSON and YAML files through proxied requests. The affected client templates authorize wildcard repository-content paths based only on a .json, .yaml, or .yml suffix, so crafted paths pass the request allowlist. Access to the private Broker tunnel is required, and exploitation exposes matching files readable with the configured integration credentials.
The record
- CVE
- CVE-2020-7650
- Published
- May 29, 2020
- Updated
- Aug 4, 2024
- Vendor
- Snyk
- Product
- Snyk Broker
- Classifications
- CWE-22, T1213
- 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 after 4.72.0 including and before 4.73.1
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