CVE-2021-41230

OIDC claims not updated from Identity Provider in Pomerium

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
• Email us at [email protected]

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.

The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions. Typical impact: unauthorized data access or execution of privileged operations.

CVE-2021-41230 has a CVSS score of 5.3 (Medium). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.15.6); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

v0.15.6

1. What is CVE-2021-41230? CVE-2021-41230 is a medium-severity incorrect authorization vulnerability in github.com/pomerium/pomerium (go), affecting versions >= 0.14.0, < 0.15.6. It is fixed in 0.15.6. The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions.
2. How severe is CVE-2021-41230? CVE-2021-41230 has a CVSS score of 5.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of github.com/pomerium/pomerium are affected by CVE-2021-41230? github.com/pomerium/pomerium (go) versions >= 0.14.0, < 0.15.6 is affected.
4. Is there a fix for CVE-2021-41230? Yes. CVE-2021-41230 is fixed in 0.15.6. Upgrade to this version or later.
5. Is CVE-2021-41230 exploitable, and should I be worried? Whether CVE-2021-41230 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2021-41230 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2021-41230? Upgrade github.com/pomerium/pomerium to 0.15.6 or later.

Other vulnerabilities in github.com/pomerium/pomerium