{"answers":{"affected":"2 open source packages ship an affected version, including aaptjs. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-36378 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-36378 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-36378 is a critical command injection vulnerability in n/a, published on 31 Oct 2021. 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-36378 and fix it if it is affected.\n\nWhat it is: CVE-2020-36378 is a critical command injection vulnerability in n/a, published on 31 Oct 2021. 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-36378 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- aaptjs (npm): affected all versions up to 1.3.1; no fix listed\n- aaptjs (npm): affected all versions up to 1.3.1; 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-36378/ (Markdown: https://insights.sbomify.com/CVE-2020-36378/index.md)","id":"CVE-2020-36378","markdown":"https://insights.sbomify.com/CVE-2020-36378/index.md","name":"CVE-2020-36378","record":{"aliases":["GHSA-4qwq-q4pr-rr7r"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"npm aaptjs library","requires_auth":"none","summary":"Attackers can execute arbitrary code via the filePath parameter in the aaptjs npm package, requiring developers to upgrade the library.","user_interaction":"not_required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"aaptjs","vendor":"aaptjs_project"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-78","name":"Improper Neutralization of Special Elements used in an OS Command"}],"description":"An issue was discovered in the packageCmd function in shenzhim aaptjs 1.3.1, allows attackers to execute arbitrary code via the filePath parameters.","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":"Vulnerability in packageCmd function leads to arbitrary code execution via filePath parameters","id":"CVE-2020-36378","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"command_injection","year":"2020"},"n_packages":2,"n_references":1,"next":{"headline":"Vulnerability in remove function leads to arbitrary code execution via filePath parameters","id":"CVE-2020-36379"},"packages":[{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["1.3.1"],"package":"aaptjs","purl":null,"source":"GHSA-4qwq-q4pr-rr7r"},{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["1.3.1"],"package":"aaptjs","purl":"pkg:npm/aaptjs","source":"GHSA-4qwq-q4pr-rr7r"}],"prev":{"headline":"Vulnerability in dump function leads to arbitrary code execution via filePath parameters","id":"CVE-2020-36377"},"products":["n/a"],"published":"2021-10-31","related":[{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2020-26707","kev_date_added":null,"published":"2021-10-31"},{"cvss_score":9.8,"headline":"Vulnerability in list function leads to arbitrary code execution via filePath parameters","id":"CVE-2020-36376","kev_date_added":null,"published":"2021-10-31"},{"cvss_score":9.8,"headline":"Vulnerability in dump function leads to arbitrary code execution via filePath parameters","id":"CVE-2020-36377","kev_date_added":null,"published":"2021-10-31"},{"cvss_score":9.8,"headline":"Vulnerability in remove function leads to arbitrary code execution via filePath parameters","id":"CVE-2020-36379","kev_date_added":null,"published":"2021-10-31"},{"cvss_score":9.8,"headline":"Vulnerability in crunch function leads to arbitrary code execution via filePath parameters","id":"CVE-2020-36380","kev_date_added":null,"published":"2021-10-31"},{"cvss_score":9.8,"headline":"Vulnerability in singleCrunch function leads to arbitrary code execution via filePath parameters","id":"CVE-2020-36381","kev_date_added":null,"published":"2021-10-31"}],"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":"Attackers can execute arbitrary code via the filePath parameter in the aaptjs npm package, requiring developers to upgrade the library.","url":"https://insights.sbomify.com/CVE-2020-36378/"}