CVE-2021-29652
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 · uneditedPomerium from version 0.10.0-0.13.3 has an Open Redirect in the user sign-in/out process
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 confidencePomerium versions 0.10.0 through 0.13.3 contain an open redirect vulnerability in the user sign-in and sign-out processes. Attackers can craft malicious URLs to redirect authenticated users to arbitrary external sites, enabling phishing attacks. The vulnerability stems from insufficient validation of redirect parameters during authentication flows.
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>= 0.10.0, <= 0.13.3CVSS 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 installed Pomerium versionRun 'pomerium --version' or check the container/image metadata, or inspect the binary if deployed on-premiseAffected if Version is 0.10.0 through 0.13.3 inclusive
-
Confirm sign-in and sign-out endpoints are exposedCheck your Pomerium configuration for routes or listeners exposing the /.pomerium/authorize, /oauth2/callback, or similar authentication endpoints. Review your reverse proxy or load balancer rules for paths related to authenticationAffected if Authentication endpoints are publicly accessible and redirect parameters can be passed
-
Test for unvalidated redirect capabilityUse a test account to attempt a sign-in flow with an external redirect parameter (such as ?redirect_url=http://evil.com). Inspect whether Pomerium honors the external URL in the final redirectAffected if Pomerium accepts and redirects to an arbitrary external domain after authentication instead of only allowing internal domains
-
Review Pomerium access logs for suspicious redirect patternsSearch logs for authentication-related requests containing 'redirect' parameters pointing to non-local domains. Look for patterns where external URLs appear in the query string during /oauth2/* or /callback pathsAffected if Logs show external redirect URLs being processed during authentication flows
You are affected if Pomerium version is between 0.10.0 and 0.13.3 and your sign-in/sign-out endpoints accept and honor arbitrary redirect URLs 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 dataUpgrade Pomerium to version 0.13.4 or later. If immediate patching is not possible, implement URL allowlist validation for redirect parameters at the load balancer or proxy layer.
- Consultation4.0 h
- Implementation6.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 $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-29652 — 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-29652 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