{"answers":{"affected":"2 open source packages ship an affected version, including Sustainsys.Saml2. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-5261 in the wild and no public exploit code.","fix":"Upgrade Sustainsys.Saml2 to 2.5.0 or later.","what":"CVE-2020-5261 is a high-severity authentication bypass vulnerability in Sustainsys Saml2, published on 25 Mar 2020. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-5261 and fix it if it is affected.\n\nWhat it is: CVE-2020-5261 is a high-severity authentication bypass vulnerability in Sustainsys Saml2, published on 25 Mar 2020. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2020-5261 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- Sustainsys.Saml2 (NuGet): affected from 2.0.0; fixed in 2.5.0\n- Sustainsys.Saml2 (NuGet): affected from 2.0.0; fixed in 2.5.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-5261/ (Markdown: https://insights.sbomify.com/CVE-2020-5261/index.md)","id":"CVE-2020-5261","markdown":"https://insights.sbomify.com/CVE-2020-5261/index.md","name":"CVE-2020-5261","record":{"aliases":["GHSA-g6j2-ch25-5mmv"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"SAML2 authentication library","requires_auth":"low_privilege","summary":"Attackers can replay SAML tokens to bypass authentication and take over user accounts in applications using the Sustainsys.Saml2 library.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"saml2","vendor":"sustainsys"}],"cvss":{"score":8.2,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-294","name":"Authentication Bypass by Capture-replay"}],"description":"Saml2 Authentication services for ASP.NET (NuGet package Sustainsys.Saml2) greater than 2.0.0, and less than version 2.5.0 has a faulty implementation of Token Replay Detection. Token Replay Detection is an important defence in depth measure for Single Sign On solutions. The 2.5.0 version is patched. Note that version 1.0.1 is not affected. It has a correct Token Replay Implementation and is safe to use. Saml2 Authentication services for ASP.NET (NuGet package Sustainsys.Saml2) greater than 2.0.0, and less than version 2.5.0 have a faulty implementation of Token Replay Detection. Token Replay Detection is an important defense measure for Single Sign On solutions. The 2.5.0 version is patched. Note that version 1.0.1 and prior versions are not affected. These versions have a correct Token Replay Implementation and are safe to use.","ecosystems":["NuGet"],"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":"Missing Token Replay Detection","id":"CVE-2020-5261","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"NuGet","product":null,"products":[],"type":"auth_bypass","year":"2020"},"n_packages":2,"n_references":3,"next":{"headline":"GitHub personal access token leaking into temporary EasyBuild (debug) logs","id":"CVE-2020-5262"},"packages":[{"ecosystem":"NuGet","fixed":["2.5.0"],"introduced":["2.0.0"],"last_affected":[],"package":"Sustainsys.Saml2","purl":null,"source":"GHSA-g6j2-ch25-5mmv"},{"ecosystem":"NuGet","fixed":["2.5.0"],"introduced":["2.0.0"],"last_affected":[],"package":"Sustainsys.Saml2","purl":"pkg:nuget/Sustainsys.Saml2","source":"GHSA-g6j2-ch25-5mmv"}],"prev":{"headline":"malicious URLs may cause Git to present stored credentials to the wrong server","id":"CVE-2020-5260"},"products":["Saml2"],"published":"2020-03-25","related":[{"cvss_score":7.5,"headline":"Sustainsys.Saml2 Insufficient Identity Provider Issuer Validation","id":"CVE-2023-41890","kev_date_added":null,"published":"2023-09-19"},{"cvss_score":6.5,"headline":"Subject Confirmation Method not validated in Saml2 Authentication Services for ASP.NET","id":"CVE-2020-5268","kev_date_added":null,"published":"2020-04-21"}],"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":["Sustainsys"]},"summary":"Attackers can replay SAML tokens to bypass authentication and take over user accounts in applications using the Sustainsys.Saml2 library.","url":"https://insights.sbomify.com/CVE-2020-5261/"}