{"answers":{"affected":"2 open source packages ship an affected version, including samlify. It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-1000452 in the wild and no public exploit code.","fix":"Upgrade samlify to 2.4.0-rc5 or later.","what":"CVE-2017-1000452 is a high-severity authentication bypass vulnerability in n/a, published on 2 Jan 2018. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-1000452 and fix it if it is affected.\n\nWhat it is: CVE-2017-1000452 is a high-severity authentication bypass vulnerability in n/a, published on 2 Jan 2018. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2017-1000452 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- samlify (npm): affected all versions; fixed in 2.4.0-rc5\n- samlify (npm): affected all versions; fixed in 2.4.0-rc5\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-2017-1000452/ (Markdown: https://insights.sbomify.com/CVE-2017-1000452/index.md)","id":"CVE-2017-1000452","markdown":"https://insights.sbomify.com/CVE-2017-1000452/index.md","name":"CVE-2017-1000452","record":{"aliases":["GHSA-8jjf-w7j6-323c"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"SAML authentication library","requires_auth":"low_privilege","summary":"Attackers can impersonate arbitrary users via XML Signature Wrapping in the Samlify SAML authentication library.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"samlify","vendor":"samlify_project"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-91","name":"XML Injection"}],"description":"An XML Signature Wrapping vulnerability exists in Samlify 2.2.0 and earlier, and in predecessor Express-saml2 which could allow attackers to impersonate arbitrary users.","ecosystems":["npm"],"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":"Samlify vulnerable to Authentication Bypass by allowing tokens to be reused with different usernames","id":"CVE-2017-1000452","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"auth_bypass","year":"2017"},"n_packages":2,"n_references":2,"next":{"headline":"Code injection in n/a","id":"CVE-2017-1000453"},"packages":[{"ecosystem":"npm","fixed":["2.4.0-rc5"],"introduced":["0"],"last_affected":[],"package":"samlify","purl":null,"source":"GHSA-8jjf-w7j6-323c"},{"ecosystem":"npm","fixed":["2.4.0-rc5"],"introduced":["0"],"last_affected":[],"package":"samlify","purl":"pkg:npm/samlify","source":"GHSA-8jjf-w7j6-323c"}],"prev":{"headline":"fs-git command injection vulnerability","id":"CVE-2017-1000451"},"products":["n/a"],"published":"2018-01-02","related":[{"cvss_score":9.9,"headline":"samlify SAML Signature Wrapping attack","id":"CVE-2025-47949","kev_date_added":null,"published":"2025-05-19"},{"cvss_score":8.7,"headline":"samlify: XML Injection in AttributeValue Allows Privilege Escalation in Signed SAML Assertions","id":"CVE-2026-46490","kev_date_added":null,"published":"2026-06-08"}],"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-09-17","vendors":["n/a"]},"summary":"Attackers can impersonate arbitrary users via XML Signature Wrapping in the Samlify SAML authentication library.","url":"https://insights.sbomify.com/CVE-2017-1000452/"}