CVE-2021-32482
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCloudera Manager 5.x, 6.x, 7.1.x, 7.2.x, and 7.3.x allows XSS via the path parameter.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceCloudera Manager versions 5.x through 7.3.x contains a reflected cross-site scripting (XSS) vulnerability in the path parameter. An attacker could inject malicious JavaScript into the path parameter which would be executed in the context of the victim's browser session when the crafted URL is visited.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 5.0.0, <= 5.16.2>= 6.0.0, <= 6.3.4>= 7.1.0, <= 7.1.4>= 7.2.0, <= 7.2.4>= 7.3.0, <= 7.3.4CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check Cloudera Manager version via command lineRun 'cloudera-manager --version' or check /usr/lib/cloudera-manager/cmf/VERSION file if accessibleAffected if The reported version falls within any of these ranges: 5.0.0-5.16.2, 6.0.0-6.3.4, 7.1.0-7.1.4, 7.2.0-7.2.4, or 7.3.0-7.3.4
-
Check Cloudera Manager version via web UILog into Cloudera Manager admin UI and navigate to Support > About or the version information pageAffected if The displayed version matches any of the affected ranges listed above
-
Identify if path parameter endpoint is accessibleSend a test request to the Cloudera Manager host with a benign string in the path parameter, such as 'http://<cm-host>:7180/testpath'Affected if The application responds and reflects the path parameter value in the response without sanitization
-
Inspect HTTP response for unsanitized path reflectionUse a browser developer tool or curl to capture the HTTP response from the path parameter endpoint and examine if the input appears unencoded in the HTMLAffected if The path parameter value is reflected directly in the response body without HTML encoding (e.g., appears as <script> tags or unescaped special characters)
You are affected if your Cloudera Manager version falls within 5.0.0-5.16.2, 6.0.0-6.3.4, 7.1.0-7.1.4, 7.2.0-7.2.4, or 7.3.0-7.3.4 AND the path parameter endpoint reflects unsanitized input in HTTP responses.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply available patches from Cloudera or implement output encoding/sanitization on the path parameter before reflecting it in HTTP responses. Validate that path input conforms to expected patterns and does not contain HTML/script tags.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-32482 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-32482 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data