{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-12556 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-12556 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-12556 is a medium-severity vulnerability in n/a, published on 16 May 2019. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-12556 and fix it if it is affected.\n\nWhat it is: CVE-2018-12556 is a medium-severity vulnerability in n/a, published on 16 May 2019. 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-2018-12556 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-2018-12556/ (Markdown: https://insights.sbomify.com/CVE-2018-12556/index.md)","id":"CVE-2018-12556","markdown":"https://insights.sbomify.com/CVE-2018-12556/index.md","name":"CVE-2018-12556","record":{"aliases":["GHSA-8mxx-g9vw-r875","UBUNTU-CVE-2018-12556"],"analysis":{"component_type":"developer_tool","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Yarn package manager","requires_auth":"none","summary":"Attackers can distribute malicious Yarn packages by signing them with arbitrary keys, bypassing signature verification in the installation script.","user_interaction":"not_required","vuln_class":"supply_chain"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"website","vendor":"yarnpkg"}],"cvss":{"score":5.9,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.0"},"cwes":[{"id":"CWE-347","name":"Improper Verification of Cryptographic Signature"}],"description":"The signature verification routine in install.sh in yarnpkg/website through 2018-06-05 only verifies that the yarn release is signed by any (arbitrary) key in the local keyring of the user, and does not pin the signature to the yarn release key, which allows remote attackers to sign tampered yarn release packages with their own key.","ecosystems":[],"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":"Supply chain in n/a","id":"CVE-2018-12556","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"supply_chain","year":"2018"},"n_packages":0,"n_references":6,"next":{"headline":"Information disclosure in n/a","id":"CVE-2018-12557"},"packages":[],"prev":{"headline":"DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2018-12555"},"products":["n/a"],"published":"2019-05-16","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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-05","vendors":["n/a"]},"summary":"Attackers can distribute malicious Yarn packages by signing them with arbitrary keys, bypassing signature verification in the installation script.","url":"https://insights.sbomify.com/CVE-2018-12556/"}