Service interruption via unbounded OIDC discovery responses
Published May 10, 2024 · Updated Aug 2, 2024
Uncontrolled resource consumption in Chainguard Octo STS before 0.1.0 allows remote attackers to interrupt the service via OIDC discovery. The provider.Get path accepts an issuer from an unverified token and lets OIDC discovery read an unbounded HTTP response body from that issuer. No authentication or user interaction is required, but denial of service depends on a malicious issuer serving oversized data and enough request volume to exhaust CPU or memory.
Summary
What happened
Uncontrolled resource consumption in Chainguard Octo STS before 0.1.0 allows remote attackers to interrupt the service via OIDC discovery. The provider.Get path accepts an issuer from an unverified token and lets OIDC discovery read an unbounded HTTP response body from that issuer. No authentication or user interaction is required, but denial of service depends on a malicious issuer serving oversized data and enough request volume to exhaust CPU or memory.
The record
- CVE
- CVE-2024-34079
- Published
- May 10, 2024
- Updated
- Aug 2, 2024
- Vendor
- Chainguard
- Product
- Octo STS
- Classifications
- CWE-400, CWE-20, T1499.003
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 10, 2024CVE publishedPublication date reported by the CVE source.
- Aug 2, 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=< 0.1.0
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