CVE-2021-22001
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 · uneditedIn UAA versions prior to 75.3.0, sensitive information like relaying secret of the provider was revealed in response when deletion request of an identity provider( IdP) of type “oauth 1.0” was sent to UAA server.
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 confidenceIn UAA versions prior to 75.3.0, an information disclosure vulnerability exists where sensitive provider credentials (specifically the relaying secret) are returned in the HTTP response body when a DELETE request is made to remove an identity provider of type 'oauth 1.0'. This allows unauthenticated or authenticated attackers with access to the deletion endpoint to capture sensitive authentication secrets from the response.
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< 16.18.0< 75.3.0CVSS 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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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.
-
Determine your UAA versionCheck the installed UAA version by reviewing your Cloud Foundry deployment manifests or running 'uaa --version' or checking the UAA service metadataAffected if The installed UAA version is prior to 75.3.0 (e.g., 75.2.x, 75.1.x, etc.)
-
Determine your Cloud Foundry Deployment versionCheck your CF Deployment version through your deployment configuration or bosh deployments outputAffected if CF Deployment version is prior to 16.18.0
-
Identify OAuth 1.0 identity providersQuery the UAA identity provider configuration using the UAA admin API or by reviewing stored identity provider configurationsAffected if Any identity provider of type 'oauth1.0' is configured in your UAA
-
Check for recent identity provider deletionsReview UAA audit logs or HTTP access logs for DELETE requests to /oauth/idp/ endpoints, particularly for oauth1.0 type providersAffected if DELETE requests to /oauth/idp/ endpoints have been logged, especially if the response bodies contained credential-like data
You are affected if your UAA version is below 75.3.0 (or CF Deployment below 16.18.0) AND you have OAuth 1.0 identity providers configured, as DELETE operations on those providers would expose sensitive relaying secrets in the response body.
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 data16.18.075.3.0
Upgrade UAA to version 75.3.0 or later. Until patching is possible, restrict access to the identity provider deletion API endpoint and monitor for suspicious requests to /oauth/idp/ endpoints.
- Consultation2.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-22001 — 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-22001 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