{"answers":{"affected":"3 open source packages ship an affected version, including github.com/pomerium/pomerium. It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-41230 in the wild and no public exploit code.","fix":"Upgrade github.com/pomerium/pomerium to 0.15.6 or later.","what":"CVE-2021-41230 is a medium-severity missing authorization vulnerability in pomerium, published on 5 Nov 2021. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-41230 and fix it if it is affected.\n\nWhat it is: CVE-2021-41230 is a medium-severity missing authorization vulnerability in pomerium, published on 5 Nov 2021. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2021-41230 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/pomerium/pomerium (Go): affected all versions; fixed in 0.15.6\n- github.com/pomerium/pomerium (Go): affected from 0.14.0; fixed in 0.15.6\n- github.com/pomerium/pomerium (Go): affected from 0.14.0; fixed in 0.15.6\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2021-41230/ (Markdown: https://insights.sbomify.com/CVE-2021-41230/index.md)","id":"CVE-2021-41230","markdown":"https://insights.sbomify.com/CVE-2021-41230/index.md","name":"CVE-2021-41230","record":{"aliases":["GHSA-j6wp-3859-vxfg","GO-2021-0258"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Identity-aware access proxy","requires_auth":"low_privilege","summary":"Pomerium fails to update OIDC claims after login, allowing users to bypass authorization policies if their identity provider claims change.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"pomerium","vendor":"pomerium"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"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.","ecosystems":["Go"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"OIDC claims not updated from Identity Provider in Pomerium","id":"CVE-2021-41230","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"missing_authorization","year":"2021"},"n_packages":3,"n_references":2,"next":{"headline":"OpenMage LTS DataFlow upload remote code execution vulnerability","id":"CVE-2021-41231"},"packages":[{"ecosystem":"Go","fixed":["0.15.6"],"introduced":["0"],"last_affected":[],"package":"github.com/pomerium/pomerium","purl":"pkg:golang/github.com/pomerium/pomerium","source":"GO-2021-0258"},{"ecosystem":"Go","fixed":["0.15.6"],"introduced":["0.14.0"],"last_affected":[],"package":"github.com/pomerium/pomerium","purl":null,"source":"GHSA-j6wp-3859-vxfg"},{"ecosystem":"Go","fixed":["0.15.6"],"introduced":["0.14.0"],"last_affected":[],"package":"github.com/pomerium/pomerium","purl":"pkg:golang/github.com/pomerium/pomerium","source":"GHSA-j6wp-3859-vxfg"}],"prev":{"headline":"Memory leak in BlueZ","id":"CVE-2021-41229"},"products":["pomerium"],"published":"2021-11-05","related":[{"cvss_score":10,"headline":"Incorrect Authorization with specially crafted requests","id":"CVE-2023-33189","kev_date_added":null,"published":"2023-05-30"},{"cvss_score":6.5,"headline":"Exposure of Sensitive Information in Pomerium","id":"CVE-2022-24797","kev_date_added":null,"published":"2022-03-31"},{"cvss_score":6.1,"headline":"JWT leak via Open Redirect in Programmatic access","id":"CVE-2021-29651","kev_date_added":null,"published":"2021-04-02"},{"cvss_score":6.1,"headline":"pomerium_signature is not verified in middleware in github.com/pomerium/pomerium","id":"CVE-2021-29652","kev_date_added":null,"published":"2021-04-02"},{"cvss_score":5.7,"headline":"Pomerium exposed OAuth2 access and ID tokens in user info endpoint response","id":"CVE-2024-39315","kev_date_added":null,"published":"2024-07-02"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"Go Vulnerability Database","prefix":"GO"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["pomerium"]},"summary":"Pomerium fails to update OIDC claims after login, allowing users to bypass authorization policies if their identity provider claims change.","url":"https://insights.sbomify.com/CVE-2021-41230/"}