CVE-2021-41230GHSA-J6WP-3859-VXFGGO-2021-0258
OIDC claims not updated from Identity Provider in Pomerium
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 0.15.6
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Pomerium is an open source identity-aware access proxy. In affected versions 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. This issue has been resolved in v0.15.6. For users unable to upgrade clear data on `databroker` service by clearing redis or restarting the in-memory databroker to force claims to be updated.
Timeline
- CVE published
- Record last updated
Affected versions
- pomerium pomerium
From 0.14.0 · fixed in 0.15.6
- github.com/pomerium/pomeriumGo
From 0.14.0 · fixed in 0.15.6
- github.com/pomerium/pomeriumGo
fixed in 0.15.6