CVE-2021-20432
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 · uneditedIBM Spectrum Protect Plus 10.1.0 through 10.1.7 uses Cross-Origin Resource Sharing (CORS) which could allow an attacker to carry out privileged actions and retrieve sensitive information as the domain name is not being limited to only trusted domains. IBM X-Force ID: 196344.
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 · high confidenceIBM Spectrum Protect Plus versions 10.1.0 through 10.1.7 contains a CORS misconfiguration where the Access-Control-Allow-Origin header is not restricted to trusted domains. This allows any external website to make cross-origin requests to the application, enabling attackers to perform privileged actions and exfiltrate sensitive data.
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>= 10.1.0, <= 10.1.7CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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.
-
Confirm IBM Spectrum Protect Plus versionLocate the installation directory and check the version file or use the command line tool provided by the product to retrieve the installed version (e.g., 'vpxlversion' or check the About section in the admin console). Compare the version number to the affected range 10.1.0 through 10.1.7.Affected if The installed version falls within 10.1.0 to 10.1.7 inclusive.
-
Identify the web interface endpointDetermine the base URL of the IBM Spectrum Protect Plus web console (typically https://hostname:port/). This is the endpoint that will handle CORS requests.Affected if The web interface is accessible and accepts HTTP requests.
-
Inspect CORS response headersSend an HTTP request from an untrusted origin (e.g., using curl with a custom Origin header like 'curl -H "Origin: https://malicious-site.com" -I https://target:port/endpoint') and examine the response headers, specifically looking for Access-Control-Allow-Origin.Affected if The response contains Access-Control-Allow-Origin header with a wildcard (*) value or the exact untrusted origin you sent in the request.
-
Test for unrestricted origin reflectionSend multiple requests with different arbitrary Origin headers (e.g., https://attacker.com, https://test.com) and check if the server reflects these origins back in the Access-Control-Allow-Origin response header without validation.Affected if The server returns the arbitrary Origin values in the Access-Control-Allow-Origin header without rejecting or validating them.
-
Verify origin whitelist configurationCheck the application configuration files or admin settings for any defined whitelist of allowed origins. Look for CORS-related configuration in the product documentation or configuration directory.Affected if No whitelist exists or the whitelist is empty, allowing any origin to pass through.
A user is affected if IBM Spectrum Protect Plus version 10.1.0-10.1.7 is installed and the server returns the Access-Control-Allow-Origin header with a wildcard or echoes back arbitrary origin values without validation.
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 dataRestrict the Access-Control-Allow-Origin header to explicitly enumerate only trusted domains, or implement proper origin validation using a whitelist approach.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-20432 — 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-20432 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