{"answers":{"affected":"2 open source packages ship an affected version, including socket.io-file. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-24807 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-24807 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-24807 is a high-severity vulnerability in n/a, published on 6 Oct 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2020-24807 and fix it if it is affected.\n\nWhat it is: CVE-2020-24807 is a high-severity vulnerability in n/a, published on 6 Oct 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2020-24807 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- socket.io-file (npm): affected all versions up to 2.0.31; no fix listed\n- socket.io-file (npm): affected all versions up to 2.0.31; 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-2020-24807/ (Markdown: https://insights.sbomify.com/CVE-2020-24807/index.md)","id":"CVE-2020-24807","markdown":"https://insights.sbomify.com/CVE-2020-24807/index.md","name":"CVE-2020-24807","record":{"aliases":["GHSA-6495-8jvh-f28x"],"analysis":{"component_type":"library","fix_type":"end_of_life","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Node.js file upload library","requires_auth":"none","summary":"Remote attackers can execute arbitrary code by uploading executable files due to client-side validation bypass in the socket.io-file package.","user_interaction":"required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"socket.io-file","vendor":"socket.io-file_project"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"The socket.io-file package through 2.0.31 for Node.js relies on client-side validation of file types, which allows remote attackers to execute arbitrary code by uploading an executable file via a modified JSON name field. NOTE: This vulnerability only affects products that are no longer supported by the maintainer","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":"File restriction bypass in socket.io-file","id":"CVE-2020-24807","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"file_upload","year":"2020"},"n_packages":2,"n_references":4,"next":{"headline":"Server-side request forgery in n/a","id":"CVE-2020-24815"},"packages":[{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["2.0.31"],"package":"socket.io-file","purl":null,"source":"GHSA-6495-8jvh-f28x"},{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["2.0.31"],"package":"socket.io-file","purl":"pkg:npm/socket.io-file","source":"GHSA-6495-8jvh-f28x"}],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2020-24804"},"products":["n/a"],"published":"2020-10-06","related":[{"cvss_score":7.5,"headline":"Path Traversal in socket.io-file","id":"CVE-2020-15779","kev_date_added":null,"published":"2020-07-15"}],"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":["n/a"]},"summary":"Remote attackers can execute arbitrary code by uploading executable files due to client-side validation bypass in the socket.io-file package.","url":"https://insights.sbomify.com/CVE-2020-24807/"}