{"answers":{"affected":"2 open source packages ship an affected version, including apidoc-core. It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-57317 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-57317 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-57317 is a high-severity vulnerability in n/a, published on 25 Sep 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-57317 and fix it if it is affected.\n\nWhat it is: CVE-2025-57317 is a high-severity vulnerability in n/a, published on 25 Sep 2025. 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-2025-57317 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- apidoc-core (npm): affected all versions up to 0.15.0; no fix listed\n- apidoc-core (npm): affected all versions up to 0.15.0; no fix listed\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-57317/ (Markdown: https://insights.sbomify.com/CVE-2025-57317/index.md)","id":"CVE-2025-57317","markdown":"https://insights.sbomify.com/CVE-2025-57317/index.md","name":"CVE-2025-57317","record":{"aliases":["GHSA-5q53-78f2-6gf8"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"API documentation parser","requires_auth":"none","summary":"Attackers can cause denial of service via prototype pollution in the apidoc-core library's preProcess function.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"apidoc-core","vendor":"apidocjs"}],"cvss":{"score":7.5,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-400","name":"Uncontrolled Resource Consumption"}],"description":"apidoc-core is the core parser library to generate apidoc result following the apidoc-spec. A Prototype Pollution vulnerability in the preProcess function of apidoc-core versions thru 0.15.0 allows attackers to inject properties on Object.prototype via supplying a crafted payload, causing denial of service (DoS) as the minimum consequence.","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":false,"headline":"apidoc-core is vulnerable to prototype pollution","id":"CVE-2025-57317","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"other","year":"2025"},"n_packages":2,"n_references":2,"next":{"headline":"csvjson vulnerable to prototype injection","id":"CVE-2025-57318"},"packages":[{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["0.15.0"],"package":"apidoc-core","purl":null,"source":"GHSA-5q53-78f2-6gf8"},{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["0.15.0"],"package":"apidoc-core","purl":"pkg:npm/apidoc-core","source":"GHSA-5q53-78f2-6gf8"}],"prev":{"headline":"Cross-site request forgery in n/a","id":"CVE-2025-57310"},"products":["n/a"],"published":"2025-09-25","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":"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-09-25","vendors":["n/a"]},"summary":"Attackers can cause denial of service via prototype pollution in the apidoc-core library's preProcess function.","url":"https://insights.sbomify.com/CVE-2025-57317/"}