{"answers":{"affected":"2 open source packages ship an affected version, including manifest.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-27408 exists.","fix":"Upgrade manifest to 4.9.2 or later.","what":"CVE-2025-27408 is a medium-severity vulnerability in mnfst manifest, published on 28 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-27408 and fix it if it is affected.\n\nWhat it is: CVE-2025-27408 is a medium-severity vulnerability in mnfst manifest, published on 28 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-27408 exists.\n\nAffected packages and fixed versions:\n- manifest (npm): affected all versions; fixed in 4.9.2\n- manifest (npm): affected all versions; fixed in 4.9.2\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-2025-27408/ (Markdown: https://insights.sbomify.com/CVE-2025-27408/index.md)","id":"CVE-2025-27408","markdown":"https://insights.sbomify.com/CVE-2025-27408/index.md","name":"CVE-2025-27408","record":{"aliases":["GHSA-h8h6-7752-g28c"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Manifest backend","requires_auth":"none","summary":"Attackers can crack user passwords more easily due to unsalted SHA3 hashing if they access the database, affecting Manifest backend users.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":4.8,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-759","name":"Use of a One-Way Hash without a Salt"}],"description":"Manifest offers users a one-file micro back end. Prior to version 4.9.2, Manifest employs a weak password hashing implementation that uses SHA3 without a salt. This exposes user passwords to a higher risk of being cracked if an attacker gains access to the database. Without the use of a salt, identical passwords across multiple users will result in the same hash, making it easier for attackers to identify and exploit patterns, thereby accelerating the cracking process. Version 4.9.2 fixes the issue.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Manifest Uses a One-Way Hash without a Salt","id":"CVE-2025-27408","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"weak_cryptography","year":"2025"},"n_packages":2,"n_references":2,"next":{"headline":"Joplin Server Vulnerable to Path Traversal","id":"CVE-2025-27409"},"packages":[{"ecosystem":"npm","fixed":["4.9.2"],"introduced":["0"],"last_affected":[],"package":"manifest","purl":null,"source":"GHSA-h8h6-7752-g28c"},{"ecosystem":"npm","fixed":["4.9.2"],"introduced":["0"],"last_affected":[],"package":"manifest","purl":"pkg:npm/manifest","source":"GHSA-h8h6-7752-g28c"}],"prev":{"headline":"Remote code execution when loading a crafted GraphQL schema","id":"CVE-2025-27407"},"products":["manifest"],"published":"2025-02-28","related":[],"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":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-03-04","vendors":["mnfst"]},"summary":"Attackers can crack user passwords more easily due to unsalted SHA3 hashing if they access the database, affecting Manifest backend users.","url":"https://insights.sbomify.com/CVE-2025-27408/"}