{"answers":{"affected":"3 open source packages ship an affected version, including pysaml2. It affects 3 products.","exploited":"There is no known exploitation of CVE-2020-5390 in the wild and no public exploit code.","fix":"Upgrade pysaml2 to 5.0.0 or later.","what":"CVE-2020-5390 is a high-severity vulnerability in Canonical Ubuntu Linux, published on 13 Jan 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-5390 and fix it if it is affected.\n\nWhat it is: CVE-2020-5390 is a high-severity vulnerability in Canonical Ubuntu Linux, published on 13 Jan 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2020-5390 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- pysaml2 (PyPI): affected all versions; fixed in 5.0.0\n- pysaml2 (PyPI): affected all versions; fixed in 5.0.0\n- pysaml2 (PyPI): affected all versions; fixed in 5.0.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-5390/ (Markdown: https://insights.sbomify.com/CVE-2020-5390/index.md)","id":"CVE-2020-5390","markdown":"https://insights.sbomify.com/CVE-2020-5390/index.md","name":"CVE-2020-5390","record":{"aliases":["DEBIAN-CVE-2020-5390","DLA-2119-1","DSA-4630-1","GHSA-qf7v-8hj3-4xw7","PYSEC-2020-94","UBUNTU-CVE-2020-5390","USN-4245-1"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Python SAML library","requires_auth":"none","summary":"Attackers can bypass SAML signature verification via XML Signature Wrapping, allowing them to forge authenticated assertions in applications using PySAML2.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"ubuntu_linux","vendor":"canonical"},{"product":"debian_linux","vendor":"debian"},{"product":"pysaml2","vendor":"pysaml2_project"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-347","name":"Improper Verification of Cryptographic Signature"}],"description":"PySAML2 before 5.0.0 does not check that the signature in a SAML document is enveloped and thus signature wrapping is effective, i.e., it is affected by XML Signature Wrapping (XSW). The signature information and the node/object that is signed can be in different places and thus the signature verification will succeed, but the wrong data will be used. This specifically affects the verification of assertion that have been signed.","ecosystems":["PyPI"],"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":"Improper Verification of Cryptographic Signature in PySAML2","id":"CVE-2020-5390","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":"canonical:ubuntu_linux","products":["canonical:ubuntu_linux","debian:debian_linux"],"type":"security_feature_bypass","year":"2020"},"n_packages":3,"n_references":8,"next":{"headline":"Cross-site request forgery in n/a","id":"CVE-2020-5391"},"packages":[{"ecosystem":"PyPI","fixed":["5.0.0"],"introduced":["0"],"last_affected":[],"package":"pysaml2","purl":null,"source":"GHSA-qf7v-8hj3-4xw7"},{"ecosystem":"PyPI","fixed":["5.0.0"],"introduced":["0"],"last_affected":[],"package":"pysaml2","purl":"pkg:pypi/pysaml2","source":"GHSA-qf7v-8hj3-4xw7"},{"ecosystem":"PyPI","fixed":["5.0.0"],"introduced":["0"],"last_affected":[],"package":"pysaml2","purl":"pkg:pypi/pysaml2","source":"PYSEC-2020-94"}],"prev":{"headline":"Information disclosure in OMIMSSC (OpenManage Integration for Microsoft System Center)","id":"CVE-2020-5389"},"products":["n/a"],"published":"2020-01-13","related":[{"cvss_score":9.8,"headline":"SaltStack Salt Authentication Bypass","id":"CVE-2020-11651","kev_date_added":"2021-11-03","published":"2020-04-30"},{"cvss_score":9.8,"headline":"OpenSMTPD Remote Code Execution","id":"CVE-2020-7247","kev_date_added":"2022-03-25","published":"2020-01-29"},{"cvss_score":9.8,"headline":"Exim Out-of-bounds Write","id":"CVE-2019-16928","kev_date_added":"2022-03-03","published":"2019-09-27"},{"cvss_score":9.8,"headline":"Exim Buffer Overflow","id":"CVE-2018-6789","kev_date_added":"2021-11-03","published":"2018-02-08"},{"cvss_score":9.8,"headline":"Oracle Java SE and Java SE Embedded Remote Code Execution","id":"CVE-2015-2590","kev_date_added":"2022-03-03","published":"2015-07-16"},{"cvss_score":9.8,"headline":"Oracle JRE Remote Code Execution","id":"CVE-2013-0422","kev_date_added":"2022-05-25","published":"2013-01-10"},{"cvss_score":9.8,"headline":"Oracle Java SE Runtime Environment (JRE) Arbitrary Code Execution","id":"CVE-2011-3544","kev_date_added":"2022-03-03","published":"2011-10-19"}],"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":"PyPA Advisory Database","prefix":"PYSEC"},{"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":"Attackers can bypass SAML signature verification via XML Signature Wrapping, allowing them to forge authenticated assertions in applications using PySAML2.","url":"https://insights.sbomify.com/CVE-2020-5390/"}