CriticalGHSA-86fh-j58m-7pf5CVE-2021-36372
Improper Privilege Management in Apache Ozone
Published 23 Nov 2021 · Updated 31 Jan 2024
Is your project on an affected org.apache.ozone:ozone-main?
Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected package
- Affected
- <1.2.0
- Fixed in
- 1.2.0
Update to the fixed version for your release line, for example:
mvn versions:use-dep-version -Dincludes=org.apache.ozone:ozone-main -DdepVersion=1.2.0 -DforceVersion=trueDetails
In Apache Ozone versions prior to 1.2.0, Initially generated block tokens are persisted to the metadata database and can be retrieved with authenticated users with permission to the key. Authenticated users may use them even after access is revoked.
Is GHSA-86fh-j58m-7pf5 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected org.apache.ozone:ozone-main, and gives you the command that fixes it.
More advisories for org.apache.ozone:ozone-main
- MediumCVE-2023-39196Apache Ozone Improper Authentication vulnerability · 7 Feb 2024
- CriticalCVE-2021-39231Exposure of sensitive information in Apache Ozone · 23 Nov 2021
- CriticalCVE-2021-39233Incorrect Authorization in Apache Ozone · 23 Nov 2021
- MediumCVE-2021-41532Apache Ozone exposes OM, SCM and Datanode metadata · 23 Nov 2021
- MediumCVE-2021-39235Incorrect permissions in Apache Ozone · 23 Nov 2021
- HighCVE-2021-39232Incorrect Authorization in Apache Ozone · 23 Nov 2021
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.