Private-network data disclosure via followed redirects
Published Jan 21, 2022 · Updated Sep 16, 2024
Server-side request forgery in @isomorphic-git/cors-proxy before 2.7.1 allows remote attackers to read private-network data. The middleware.js fetch follows a first-hop server's attacker-controlled HTTP redirect without validating the Location destination. The proxy must accept the request from outside its private network, and the attacker must control the first-hop server; successful exploitation probes internal services and returns their responses.
Summary
What happened
Server-side request forgery in @isomorphic-git/cors-proxy before 2.7.1 allows remote attackers to read private-network data. The middleware.js fetch follows a first-hop server's attacker-controlled HTTP redirect without validating the Location destination. The proxy must accept the request from outside its private network, and the attacker must control the first-hop server; successful exploitation probes internal services and returns their responses.
The record
- CVE
- CVE-2021-23664
- Published
- Jan 21, 2022
- Updated
- Sep 16, 2024
- Vendor
- isomorphic-git
- Product
- @isomorphic-git/cors-proxy
- Classifications
- CWE-918, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 21, 2022CVE publishedPublication date reported by the CVE source.
- Sep 16, 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=unspecified <2.7.1
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 HTTP request proof of conceptproof of concept · demonstrated
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