OzoneApplication · Apache
CVE-2020-17517
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceApache Ozone prior to 1.1.0 contains a default access control flaw where S3 buckets and keys in secure clusters remain accessible via unauthenticated HTTP requests. Attackers can use curl or direct HTTP calls to bypass authentication and read or access bucket/key data that should be protected in a secure cluster configuration.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
OzoneApplication
< 1.1.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Apache Ozone versionRun 'ozone version' or check the installed RPM/deb package version, or look for ozone-*.jar files in the installation directoryAffected if Version is prior to 1.1.0 (e.g., 1.0.x, 0.x.x)
-
Verify S3 Gateway is enabledCheck if the S3 gateway service is listed as running via 'ozone admin services' or check for processes listening on port 9878 (default S3 HTTP port)Affected if S3 gateway is running and accepting HTTP connections
-
Confirm security is enabled in the clusterCheck ozone-site.xml for 'ozone.security.enabled' set to 'true', or verify Kerberos/other security configuration is activeAffected if Cluster is configured as secure with security enabled
-
Test unauthenticated S3 bucket accessRun a curl command against the S3 endpoint without credentials: curl http://<s3-gateway>:9878/bucket/ or curl http://<s3-gateway>:9878/ to list bucketsAffected if The request returns bucket listing or key data without authentication (HTTP 200 with data rather than 401/403)
-
Check ozone-site.xml for anonymous access settingInspect ozone-site.xml for 'ozone.s3g.public.access' or similar settings that explicitly allow or deny public/anonymous access to bucketsAffected if Setting allows public access or is not explicitly set to deny anonymous access in a secure cluster
A user is affected if running Apache Ozone version prior to 1.1.0 with the S3 gateway enabled in a secure cluster configuration, and unauthenticated HTTP requests can read bucket or key data.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data1.1.0
Upgrade Apache Ozone to version 1.1.0 or later, which enforces proper default access controls preventing anonymous access to buckets and keys.
Fix this in Ozone
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-17517 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-17517 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data