{"answers":{"affected":"2 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-15233 in the wild and no public exploit code.","fix":"Upgrade github.com/ory/fosite to 0.34.1 or later.","what":"CVE-2020-15233 is a medium-severity vulnerability in ory fosite, published on 2 Oct 2020. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2020-15233 and fix it if it is affected.\n\nWhat it is: CVE-2020-15233 is a medium-severity vulnerability in ory fosite, published on 2 Oct 2020. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2020-15233 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/ory/fosite (Go): affected from 0.30.3; fixed in 0.34.1\n- github.com/ory/fosite (Go): affected from 0.30.3; fixed in 0.34.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-2020-15233/ (Markdown: https://insights.sbomify.com/CVE-2020-15233/index.md)","id":"CVE-2020-15233","markdown":"https://insights.sbomify.com/CVE-2020-15233/index.md","name":"CVE-2020-15233","record":{"aliases":["GHSA-rfq3-w54c-f9q5"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Go OAuth2 framework","requires_auth":"high_privilege","summary":"Attackers with loopback access can bypass OAuth2 redirect URL validation by manipulating query parameters and host casing in the ORY Fosite library.","user_interaction":"required","vuln_class":"open_redirect"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"fosite","vendor":"ory"}],"cvss":{"score":6.1,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-601","name":"URL Redirection to Untrusted Site"},{"id":"CWE-20","name":"Improper Input Validation"}],"description":"ORY Fosite is a security first OAuth2 \u0026 OpenID Connect framework for Go. In Fosite from version 0.30.2 and before version 0.34.1, there is an issue in which an an attacker can override the registered redirect URL by performing an OAuth flow and requesting a redirect URL that is to the loopback adapter. Attackers can provide both custom URL query parameters to their loopback redirect URL, as well as actually overriding the host of the registered redirect URL. These attacks are only applicable in scenarios where the attacker has access over the loopback interface. This vulnerability has been patched in ORY Fosite v0.34.1.","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":"OAuth2 Redirect URL validity does not respect query parameters and character casing for loopback addresses","id":"CVE-2020-15233","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"open_redirect","year":"2020"},"n_packages":2,"n_references":2,"next":{"headline":"Redirect URL matching ignores character casing","id":"CVE-2020-15234"},"packages":[{"ecosystem":"Go","fixed":["0.34.1"],"introduced":["0.30.3"],"last_affected":[],"package":"github.com/ory/fosite","purl":null,"source":"GHSA-rfq3-w54c-f9q5"},{"ecosystem":"Go","fixed":["0.34.1"],"introduced":["0.30.3"],"last_affected":[],"package":"github.com/ory/fosite","purl":"pkg:golang/github.com/ory/fosite","source":"GHSA-rfq3-w54c-f9q5"}],"prev":{"headline":"XML External Entity attack in mapfish-print","id":"CVE-2020-15232"},"products":["fosite"],"published":"2020-10-02","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":8,"headline":"Ignored storage errors on token revokation in ORY Fosite","id":"CVE-2020-15223","kev_date_added":null,"published":"2020-09-24"},{"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":"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 with loopback access can bypass OAuth2 redirect URL validation by manipulating query parameters and host casing in the ORY Fosite library.","url":"https://insights.sbomify.com/CVE-2020-15233/"}