CVE-2021-22098
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 · uneditedUAA server versions prior to 75.4.0 are vulnerable to an open redirect vulnerability. A malicious user can exploit the open redirect vulnerability by social engineering leading to take over of victims’ accounts in certain cases along with redirection of UAA users to a malicious sites.
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 confidenceUAA (User Account and Authentication) server versions prior to 75.4.0 contain an open redirect vulnerability. Attackers can craft malicious URLs containing controlled redirect parameters that cause the UAA server to forward users to attacker-controlled domains instead of the legitimate destination. This can be leveraged in social engineering attacks to steal credentials or session tokens, potentially leading to account takeover.
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.20.0< 75.5.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
- 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.
-
Identify UAA server versionQuery the UAA server version endpoint or check the installed UAA package version using your deployment tooling (e.g., bosh deployments, cf CLI, or RPM/dpkg query on the UAA VM)Affected if The installed UAA version is below 75.5.0 or the Cf Deployment version is below 16.20.0
-
Verify redirect functionality is exposedInspect the UAA configuration file (uaa.yml) for any redirect_uri or login.redirect configurations that accept user-supplied parametersAffected if Redirect URIs are configured to accept dynamic user input rather than strict allowlists
-
Check for open redirect patterns in URL parametersReview any logs or traffic captures for incoming requests to UAA endpoints (such as /oauth/authorize or /login) containing redirect parameters with external domainsAffected if Requests with redirect parameters pointing to untrusted domains are being processed by the UAA server
-
Inspect UAA login page configurationExamine the UAA login manifest or configuration for the 'login' component settings, specifically any 'redirect' or 'uri' parameters that control where users are forwarded after authenticationAffected if The login component allows arbitrary redirect targets without validation
A user is affected if their UAA server version is below 75.5.0 (or Cf Deployment below 16.20.0) AND the server processes redirect parameters that can point to external domains.
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.20.075.5.0
Upgrade UAA server to version 75.4.0 or later to remediate the open redirect vulnerability.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-22098 — 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-22098 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