CVE-2021-36372CWE-273

Original block tokens are persisted and can be retrieved

published November 19, 2021

CVSS
—
EPSS
3%
Percentile
84.8
In the wild
Unconfirmed
What it is

⚠️ A hidden treasure trove of block tokens could be misused by previously authorized users! Even after revocation, they can still access these tokens and gain unauthorized access. 🔑 Think of it as a library where users have borrowed books, and even after their memberships expire, they can still sneak back in and grab the same books they've borrowed before. These block tokens are like those books, lingering long after access rights should have been revoked. This means that if a user's access is revoked, they can still exploit any remaining block tokens to access sensitive data or resources. The potential for data leakage is real and could lead to unauthorized actions within Apache Ozone environments, making it critical to manage permissions carefully.

Put simply

Think of it as a library where users have borrowed books, and even after their memberships expire, they can still sneak back in and grab the same books they've borrowed before. These block tokens are like those books, lingering long after access rights should have been revoked. In Apache Ozone versions prior to 1.2.0, block tokens generated and stored in the metadata database can be retrieved by authenticated users with permissions to the key, even when their access is no longer valid. This lack of proper token management allows former users to misuse tokens long after they've lost access.

What to do

This means that if a user's access is revoked, they can still exploit any remaining block tokens to access sensitive data or resources. The potential for data leakage is real and could lead to unauthorized actions within Apache Ozone environments, making it critical to manage permissions carefully. To patch this, upgrade to Apache Ozone version 1.2.0 or later, where this issue is resolved. After upgrading, review your token management processes to ensure proper permissions are enforced consistently. Regular audits on user access can also help mitigate similar risks in the future. You've got this! With these steps, you'll be well on your way to securing your Ozone environment. 🛡️

The record
Technical detail
CVSS
Not scored
CVSS v4.0
Not supplied
EPSS
0.02526 · 84.8th percentile
Weakness
CWE-273 · Improper Check for Dropped Privileges
Published
2021-11-19T09:20Z
EPSS history
Timeline
  • 19 NOV 09:20Z
    Original block tokens are persisted and can be retrieved
    cvelistv5