NVD / CVE Program· CNA apache

CVE-2021-39235: Access mode of block tokens are not enforced

MediumCVSS 6.5 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 26/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 1.5% (FIRST EPSS); higher than 75.4% of all records.
Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
Fixed version: org.apache.ozone:ozone-main (Maven) 1.2.0.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to org.apache.ozone:ozone-main (Maven) 1.2.0 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

GHSA-c6j7-4fr9-c76p

Published: Nov 19, 2021
Updated: Jun 17, 2026
EPSS: 1.5% · 75th percentile
CWE: CWE-732

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 26 / 40 · 6.5 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 1.5%

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
apache	ozone	cpe:2.3:a:apache:ozone

Versions reported by the vendor

Affected version ranges reported by the assigning authority (apache). Independent of NVD's CPE analysis and usually ahead of it.

Apache Software Foundation Apache Ozone
- 1.0 and later · up to and including 1.0affected

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

apache ozonebefore 1.2.0

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Maven	org.apache.ozone:ozone-main	before 1.2.0	1.2.0

Same product

apache: all records

Other highest-scoring records for the same primary product.

CVE-2021-36372Original block tokens are persisted and can be retrieved
40Plan
CVE-2021-39233Container-related datanode operations can be called without authorization
37Monitor
CVE-2021-39231Missing authentication/authorization on internal RPC endpoints
37Monitor

Published before and after this one in the same product

← EarlierCVE-2021-39232Nov 19, 2021 · Missing admin check for SCM related admin commands
36Monitor
← EarlierCVE-2021-39234Nov 19, 2021 · Raw block data can be read bypassing ACL/authorization
27Monitor
Later →CVE-2021-39236Nov 19, 2021 · Owners of the S3 tokens are not validated
36Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
Maven:org.apache.ozone:ozone-main	1.2.0	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.