Ozone S3 Gateway allows bucket and key access to non authenticated users
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- High · None · None
- Fix status
- No fix listed
Attack profile from CVSS 3.1 · NVD. Fix status from CNA. Impact type from CWE-285.
Summary
The S3 buckets and keys in a secure Apache Ozone Cluster must be inaccessible to anonymous access by default. The current security vulnerability allows access to keys and buckets through a curl command or an unauthenticated HTTP request. This enables unauthorized access to buckets and keys thereby exposing data to anonymous clients or users. This affected Apache Ozone prior to the 1.1.0 release.
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
Remediation
No fixed version listed by the sources yet.
Timeline
- 2026-10-02 Threatist record created from CVE-2020-17517
- 2026-10-03 Alias added: GHSA-h253-pq36-ggpj
References
More Apache Ozone vulnerabilities
- TI-2021-14726 Original block tokens are persisted and can be retrieved CVSS 3.1CRITICAL 9.8
- TI-2021-16618 Container-related datanode operations can be called without authorization CVSS 3.1CRITICAL 9.1
- TI-2021-16616 Missing authentication/authorization on internal RPC endpoints CVSS 3.1CRITICAL 9.1
- TI-2021-16621 Owners of the S3 tokens are not validated CVSS 3.1HIGH 8.8
- TI-2021-16617 Missing admin check for SCM related admin commands CVSS 3.1HIGH 8.8
- TI-2024-30207 Apache Ozone: Improper authentication when generating S3 secrets CVSS 3.1HIGH 8.1
Sources
- CVE-2020-17517 · CVE Program
- CVE-2020-17517 · NVD
- FIRST EPSS
- GHSA-h253-pq36-ggpj · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences