MediumGHSA-c6j7-4fr9-c76pCVE-2021-39235

Incorrect permissions in Apache Ozone

Published 23 Nov 2021 · Updated 14 Nov 2023

Is your project on an affected org.apache.ozone:ozone-main?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

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=true

Details

In Apache Ozone before 1.2.0, Ozone Datanode doesn't check the access mode parameter of the block token. Authenticated users with valid READ block token can do any write operation on the same block.

Is GHSA-c6j7-4fr9-c76p 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
  • CriticalCVE-2021-36372Improper Privilege Management in Apache Ozone · 23 Nov 2021
  • HighCVE-2021-39232Incorrect Authorization in Apache Ozone · 23 Nov 2021
All 8 advisories for org.apache.ozone:ozone-main

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.