{"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-2024-39315 in the wild and no public exploit code.","fix":"Upgrade github.com/pomerium/pomerium to 0.26.1 or later.","what":"CVE-2024-39315 is a medium-severity vulnerability in pomerium, published on 2 Jul 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2024-39315 and fix it if it is affected.\n\nWhat it is: CVE-2024-39315 is a medium-severity vulnerability in pomerium, published on 2 Jul 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2024-39315 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.26.1\n- github.com/pomerium/pomerium (Go): affected all versions; fixed in 0.26.1\n- github.com/pomerium/pomerium (Go): affected all versions; fixed in 0.26.1\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-2024-39315/ (Markdown: https://insights.sbomify.com/CVE-2024-39315/index.md)","id":"CVE-2024-39315","markdown":"https://insights.sbomify.com/CVE-2024-39315/index.md","name":"CVE-2024-39315","record":{"aliases":["GHSA-rrqr-7w59-637v","GO-2024-2965"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Identity access proxy","requires_auth":"low_privilege","summary":"Pomerium exposed OAuth2 tokens in user info endpoint, allowing attackers to potentially impersonate users if combined with XSS in proxied apps.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"pomerium","vendor":"pomerium"}],"cvss":{"score":5.7,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-201","name":"Insertion of Sensitive Information Into Sent Data"}],"description":"Pomerium is an identity and context-aware access proxy. Prior to version 0.26.1, the Pomerium user info page (at `/.pomerium`) unintentionally included serialized OAuth2 access and ID tokens from the logged-in user's session. These tokens are not intended to be exposed to end users. This issue may be more severe in the presence of a cross-site scripting vulnerability in an upstream application proxied through Pomerium. If an attacker could insert a malicious script onto a web page proxied through Pomerium, that script could access these tokens by making a request to the `/.pomerium` endpoint. Upstream applications that authenticate only the ID token may be vulnerable to user impersonation using a token obtained in this manner. Note that an OAuth2 access token or ID token by itself is not sufficient to hijack a user's Pomerium session. Upstream applications should not be vulnerable to user impersonation via these tokens provided the application verifies the Pomerium JWT for each request, the connection between Pomerium and the application is secured by mTLS, or the connection between Pomerium and the application is otherwise secured at the network layer. The issue is patched in Pomerium v0.26.1. No known workarounds are available.","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":"Pomerium exposed OAuth2 access and ID tokens in user info endpoint response","id":"CVE-2024-39315","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"information_disclosure","year":"2024"},"n_packages":3,"n_references":2,"next":{"headline":"Rack ReDoS Vulnerability in HTTP Accept Headers Parsing","id":"CVE-2024-39316"},"packages":[{"ecosystem":"Go","fixed":["0.26.1"],"introduced":["0"],"last_affected":[],"package":"github.com/pomerium/pomerium","purl":null,"source":"GHSA-rrqr-7w59-637v"},{"ecosystem":"Go","fixed":["0.26.1"],"introduced":["0"],"last_affected":[],"package":"github.com/pomerium/pomerium","purl":"pkg:golang/github.com/pomerium/pomerium","source":"GHSA-rrqr-7w59-637v"},{"ecosystem":"Go","fixed":["0.26.1"],"introduced":["0"],"last_affected":[],"package":"github.com/pomerium/pomerium","purl":"pkg:golang/github.com/pomerium/pomerium","source":"GO-2024-2965"}],"prev":{"headline":"toy-blog administrative token leaked through the command line parameter","id":"CVE-2024-39314"},"products":["pomerium"],"published":"2024-07-02","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.3,"headline":"OIDC claims not updated from Identity Provider in Pomerium","id":"CVE-2021-41230","kev_date_added":null,"published":"2021-11-05"}],"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-08-02","vendors":["pomerium"]},"summary":"Pomerium exposed OAuth2 tokens in user info endpoint, allowing attackers to potentially impersonate users if combined with XSS in proxied apps.","url":"https://insights.sbomify.com/CVE-2024-39315/"}