OIDC claims not updated from Identity Provider in Pomerium
### Impact Changes to the OIDC claims of a user after initial login are not reflected in policy evaluation when using [`allowed_idp_claims`](https://www.pomerium.com/reference/#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 `databroker` service 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](https://github.com/pomerium/pomerium) * Email us at [security@pomerium.com](mailto:security@pomerium.com)
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2021-41230US | high8.8OT elevated | — | ||
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 us… | ||||
references
External citations — patches, advisories, analysis.
- https://github.com/pomerium/pomeriumPACKAGE
- https://github.com/pomerium/pomerium/commit/f20542c4bf2cc691e4c324f7ec79e02e46d95511WEB
- https://github.com/pomerium/pomerium/pull/2724WEB
- https://github.com/pomerium/pomerium/security/advisories/GHSA-j6wp-3859-vxfgWEB
- https://nvd.nist.gov/vuln/detail/CVE-2021-41230ADVISORY
- https://pkg.go.dev/vuln/GO-2021-0258WEB
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan