Information Disclosure in github.com/pomerium/pomerium (CVE-2021-29651)
Summary
Vulnerability in github.com/pomerium/pomerium (CVE-2021-29651). Confidential information can be exposed externally. Mitigation: upgrade to 0.13.4 or later.
Original description
The description as published by the source.
Impact
Using programmatic access on protected sites, one can get a signed login URL with pomerium_redirect_uri set to an arbitrary URL. Then, if the user has already logged into Pomerium, they will be redirected to the specified pomerium_redirect_uri with a JWT attached. This allows an outside attacker to get a signed login URL that, upon visiting it, will redirect a victim to the attacker’s site. This creates an issue of Open Redirect and, more seriously, JWT leakage.
With a leaked JWT, the attacker will be able to unveil the victim’s identity (.e.g. email address) by supplying the JWT to the authenticate service or verify.pomerium.com. In addition, if an application integrating Pomerium only verifies the iss claim and others but not the aud claim, the attacker will be able to access it as the victim.
Specific Go Packages Affected
github.com/pomerium/pomerium/proxy
Patches
Patched in Pomerium v0.13.4
For more information
If you have any questions or comments about this advisory
- Open an issue in pomerium
- Email us at security@pomerium.com
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2021-29651 has been found in github.com/pomerium/pomerium.
Confidential information can be exposed externally.
What to do: upgrade github.com/pomerium/pomerium to 0.13.4 or later.
If unsure, ask your IT team or search "github.com/pomerium/pomerium CVE-2021-29651" on the vendor's site.
CVE-2021-29651 (github.com/pomerium/pomerium) — CWE-200
Attack vector: remote (network-reachable)
Patched: 0.13.4 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Information disclosure (CWE-200) exists in github.com/pomerium/pomerium.
Check the vendor advisory for the affected versions of github.com/pomerium/pomerium.
Severity: ?. Confidential information can be exposed externally.
Update to 0.13.4.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/pomerium/pomerium' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/pomerium/pomerium' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/pomerium/pomeriumを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/pomerium/pomerium to 0.13.4ステージング環境で 0.13.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- web github.com
- web github.com