Skip to content
Fencer Intel
medium 6.8

CVE-2021-39234 json

Raw block data can be read bypassing ACL/authorization

published 4y ago modified 4mo ago also GHSA-c8cw-2c5j-xff3 , EUVD-2021-2334

cvss
6.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.4%
EPSS 1.4% chance of exploitation in 30 days, percentile 72%
public exploits
0
none known

Summary

In Apache Ozone versions prior to 1.2.0, Authenticated users knowing the ID of an existing block can craft specific request allowing access those blocks, bypassing other security checks like ACL.

Patch / fix

  • maven org.apache.ozone:ozone-main 1.2.0
  • apache ozone 1.2.0

Is CVE-2021-39234 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

1.41% chance of exploitation in the next 30 days, higher than 72% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 6.8 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N
NVD 2.0 4.9 AV:N/AC:M/Au:S/C:P/I:P/A:N
GitHub 3.1 6.8 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N

Affected packages

ecosystem package affected fixed in
maven org.apache.ozone:ozone-main
<1.2.0
1.2.0

Affected products

  • Apache Software Foundation Apache Ozone

Classification

Weakness
  • CWE-20 Improper Input Validation
  • CWE-863 Incorrect Authorization

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.