Skip to content

OIDC claims not updated from Identity Provider in Pomerium

Moderate severity GitHub Reviewed Published Nov 5, 2021 in pomerium/pomerium • Updated Feb 15, 2023

Package

gomod github.com/pomerium/pomerium (Go)

Affected versions

>= 0.14.0, < 0.15.6

Patched versions

0.15.6

Description

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 databroker service by clearing redis or restarting the in-memory databroker to force claims to be updated

References

pomerium/pomerium#2724

For more information

If you have any questions or comments about this advisory:

References

@travisgroth travisgroth published to pomerium/pomerium Nov 5, 2021
Published by the National Vulnerability Database Nov 5, 2021
Reviewed Nov 8, 2021
Published to the GitHub Advisory Database Nov 10, 2021
Last updated Feb 15, 2023

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N

EPSS score

0.104%
(43rd percentile)

Weaknesses

CVE ID

CVE-2021-41230

GHSA ID

GHSA-j6wp-3859-vxfg

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.