Arbitrary internal requests via API-key host injection
Published Apr 25, 2022 · Updated Aug 3, 2024
SSRF in Gibbon before 3.4.4 allows attackers to send arbitrary HTTP requests through applications accepting user-supplied API keys. Gibbon splits the API key at hyphens and concatenates the unchecked suffix into base_api_url as a Mailchimp data-center subdomain. Exposure requires a consuming application to pass user-controlled API keys; crafted suffixes redirect Faraday requests to internal or attacker hosts.
Summary
What happened
SSRF in Gibbon before 3.4.4 allows attackers to send arbitrary HTTP requests through applications accepting user-supplied API keys. Gibbon splits the API key at hyphens and concatenates the unchecked suffix into base_api_url as a Mailchimp data-center subdomain. Exposure requires a consuming application to pass user-controlled API keys; crafted suffixes redirect Faraday requests to internal or attacker hosts.
The record
- CVE
- CVE-2022-27311
- Published
- Apr 25, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-918
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 25, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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
- Doyensec Gibbon SSRF reproductionproof 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