{"answers":{"affected":"3 open source packages ship an affected version, including github.com/ory/fosite. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-15223 in the wild and no public exploit code.","fix":"Upgrade github.com/ory/fosite to 0.34.0 or later.","what":"CVE-2020-15223 is a high-severity vulnerability in ory fosite, published on 24 Sep 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2020-15223 and fix it if it is affected.\n\nWhat it is: CVE-2020-15223 is a high-severity vulnerability in ory fosite, published on 24 Sep 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2020-15223 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/ory/fosite (Go): affected all versions; fixed in 0.34.0\n- github.com/ory/fosite (Go): affected all versions; fixed in 0.34.0\n- github.com/ory/fosite (Go): affected all versions; fixed in 0.34.0\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-2020-15223/ (Markdown: https://insights.sbomify.com/CVE-2020-15223/index.md)","id":"CVE-2020-15223","markdown":"https://insights.sbomify.com/CVE-2020-15223/index.md","name":"CVE-2020-15223","record":{"aliases":["GHSA-7mqr-2v3q-v2wm","GO-2021-0109"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Go OAuth2 framework","requires_auth":"none","summary":"Attackers may retain valid tokens after revocation attempts if storage errors occur, bypassing security controls in ORY Fosite.","user_interaction":"required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"fosite","vendor":"ory"}],"cvss":{"score":8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-754","name":"Improper Check for Unusual or Exceptional Conditions"},{"id":"CWE-755","name":"Improper Handling of Exceptional Conditions"}],"description":"In ORY Fosite (the security first OAuth2 \u0026 OpenID Connect framework for Go) before version 0.34.0, the `TokenRevocationHandler` ignores errors coming from the storage. This can lead to unexpected 200 status codes indicating successful revocation while the token is still valid. Whether an attacker can use this for her advantage depends on the ability to trigger errors in the store. This is fixed in version 0.34.0","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":"Ignored storage errors on token revokation in ORY Fosite","id":"CVE-2020-15223","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"business_logic","year":"2020"},"n_packages":3,"n_references":3,"next":{"headline":"Socket syscalls can leak enclave memory contents in Open Enclave","id":"CVE-2020-15224"},"packages":[{"ecosystem":"Go","fixed":["0.34.0"],"introduced":["0"],"last_affected":[],"package":"github.com/ory/fosite","purl":null,"source":"GHSA-7mqr-2v3q-v2wm"},{"ecosystem":"Go","fixed":["0.34.0"],"introduced":["0"],"last_affected":[],"package":"github.com/ory/fosite","purl":"pkg:golang/github.com/ory/fosite","source":"GHSA-7mqr-2v3q-v2wm"},{"ecosystem":"Go","fixed":["0.34.0"],"introduced":["0"],"last_affected":[],"package":"github.com/ory/fosite","purl":"pkg:golang/github.com/ory/fosite","source":"GO-2021-0109"}],"prev":{"headline":"Replay of private_key_jwt possible in ORY Fosite","id":"CVE-2020-15222"},"products":["fosite"],"published":"2020-09-24","related":[{"cvss_score":8.1,"headline":"Replay of private_key_jwt possible in ORY Fosite","id":"CVE-2020-15222","kev_date_added":null,"published":"2020-09-24"},{"cvss_score":6.1,"headline":"OAuth2 Redirect URL validity does not respect query parameters and character casing for loopback addresses","id":"CVE-2020-15233","kev_date_added":null,"published":"2020-10-02"},{"cvss_score":6.1,"headline":"Redirect URL matching ignores character casing","id":"CVE-2020-15234","kev_date_added":null,"published":"2020-10-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":["ory"]},"summary":"Attackers may retain valid tokens after revocation attempts if storage errors occur, bypassing security controls in ORY Fosite.","url":"https://insights.sbomify.com/CVE-2020-15223/"}