Authorization Flaw in github.com/pomerium/pomerium (CVE-2021-41230)
Summary
Vulnerability in github.com/pomerium/pomerium (CVE-2021-41230). Confidential information can be exposed externally. Exploitable via allowed_idp_claims. Mitigation: upgrade to 0.15.6 or later.
Original description
The description as published by the source.
Impact
Changes to the OIDC claims of a user after initial login are not reflected in policy evaluation when using allowed_idp_claims as part of policy. If using allowed_idp_claims and a user's claims are changed, Pomerium can make incorrect authorization decisions.
Patches
v0.15.6
Workarounds
- Clear data on
databrokerservice by clearing redis or restarting the in-memory databroker to force claims to be updated
References
https://github.com/pomerium/pomerium/pull/2724
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-41230 has been found in github.com/pomerium/pomerium.
Attackers can target a specific entry point like allowed_idp_claims over the network to misuse the product.
Confidential information can be exposed externally.
What to do: upgrade github.com/pomerium/pomerium to 0.15.6 or later.
If unsure, ask your IT team or search "github.com/pomerium/pomerium CVE-2021-41230" on the vendor's site.
CVE-2021-41230 (github.com/pomerium/pomerium) — CWE-863
Attack vector: remote (network-reachable) / no user interaction
Attack surface: allowed_idp_claims / databroker
Patched: 0.15.6 — apply immediately
Workaround: - Clear data on databroker service by clearing redis or restarting the in-memory databroker to force claims to be updated
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.
Incorrect authorization (CWE-863) exists in github.com/pomerium/pomerium. Attackers reach the vulnerable code path via allowed_idp_claims.
Check the vendor advisory for the affected versions of github.com/pomerium/pomerium. Attack surface: allowed_idp_claims / databroker.
Severity: ?. Confidential information can be exposed externally.
Update to 0.15.6.
Workaround: - Clear data on databroker service by clearing redis or restarting the in-memory databroker to force claims to be updated
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 temporary workaround mitigate
- Clear data on `databroker` service by clearing redis or restarting the in-memory databroker to force claims to be updatedパッチが適用されるまでの応急処置として、- Clear data on
databrokerservice by clearing redis or restarting the in-memory databroker to force claims to be updated を実施。回避策の副作用 (機能低下) を確認した上で。 -
3Apply patch patch
Upgrade github.com/pomerium/pomerium to 0.15.6ステージング環境で 0.15.6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com
- web pkg.go.dev