{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-26877 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-26877 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-26877 is a medium-severity vulnerability in n/a, published on 29 Jun 2022."},"fix_prompt":"Check this codebase for CVE-2020-26877 and fix it if it is affected.\n\nWhat it is: CVE-2020-26877 is a medium-severity vulnerability in n/a, published on 29 Jun 2022. \nExploitation: There is no known exploitation of CVE-2020-26877 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-26877/ (Markdown: https://insights.sbomify.com/CVE-2020-26877/index.md)","id":"CVE-2020-26877","markdown":"https://insights.sbomify.com/CVE-2020-26877/index.md","name":"CVE-2020-26877","record":{"aliases":["GHSA-hg6g-fgr6-h93g"],"analysis":null,"analysis_generated_by":null,"assigner":"mitre","cpe":[{"product":"oauth_2.0_server","vendor":"apifest"}],"cvss":{"score":6.1,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-601","name":"URL Redirection to Untrusted Site"}],"description":"ApiFest OAuth 2.0 Server 0.3.1 does not validate the redirect URI in accordance with RFC 6749 and is susceptible to an open redirector attack. Specifically, it directly sends an authorization code to the redirect URI submitted with the authorization request, without checking whether the redirect URI is registered by the client who initiated the request. This allows an attacker to craft a request with a manipulated redirect URI (redirect_uri parameter), which is under the attacker's control, and consequently obtain the leaked authorization code when the server redirects the client to the manipulated redirect URI with an authorization code. NOTE: this is similar to CVE-2019-3778.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"ApiFest OAuth 2.0 Server 0.3.1 does not validate the redirect URI in accordance with RFC 6749 and is susceptible to an open redirector attack.","id":"CVE-2020-26877","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2020"},"n_packages":0,"n_references":3,"next":{"headline":"Command injection in n/a","id":"CVE-2020-26878"},"packages":[],"prev":{"headline":"Business logic in n/a","id":"CVE-2020-26876"},"products":["n/a"],"published":"2022-06-29","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":["n/a"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2020-26877/"}