{"answers":{"affected":"2 open source packages ship an affected version, including hex_core. It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-1000013 in the wild and no public exploit code.","fix":"Upgrade hex_core to 0.4.0 or later.","what":"CVE-2019-1000013 is a high-severity vulnerability in n/a, published on 4 Feb 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2019-1000013 and fix it if it is affected.\n\nWhat it is: CVE-2019-1000013 is a high-severity vulnerability in n/a, published on 4 Feb 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2019-1000013 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- hex_core (Hex): affected all versions; fixed in 0.4.0\n- hex_core (Hex): affected all versions; fixed in 0.4.0\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-2019-1000013/ (Markdown: https://insights.sbomify.com/CVE-2019-1000013/index.md)","id":"CVE-2019-1000013","markdown":"https://insights.sbomify.com/CVE-2019-1000013/index.md","name":"CVE-2019-1000013","record":{"aliases":["GHSA-q3cc-rr2c-87r6"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Hex package manager","requires_auth":"none","summary":"Attackers can modify packages undetected via malicious mirrors, leading to code execution when victims fetch packages.","user_interaction":"required","vuln_class":"supply_chain"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"hex_core","vendor":"hex"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-345","name":"Insufficient Verification of Data Authenticity"}],"description":"Hex package manager hex_core version 0.3.0 and earlier contains a Signing oracle vulnerability in Package registry verification that can result in Package modifications not detected, allowing code execution. This attack appears to be exploitable via victim fetches packages from malicious/compromised mirror. This vulnerability appears to have been fixed in 0.4.0.","ecosystems":["Hex"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Hex authenticity of signed packages not validated","id":"CVE-2019-1000013","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Hex","product":null,"products":[],"type":"supply_chain","year":"2019"},"n_packages":2,"n_references":2,"next":{"headline":"Supply chain in n/a","id":"CVE-2019-1000014"},"packages":[{"ecosystem":"Hex","fixed":["0.4.0"],"introduced":["0"],"last_affected":[],"package":"hex_core","purl":null,"source":"GHSA-q3cc-rr2c-87r6"},{"ecosystem":"Hex","fixed":["0.4.0"],"introduced":["0"],"last_affected":[],"package":"hex_core","purl":"pkg:hex/hex_core","source":"GHSA-q3cc-rr2c-87r6"}],"prev":{"headline":"Supply chain in n/a","id":"CVE-2019-1000012"},"products":["n/a"],"published":"2019-02-04","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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Attackers can modify packages undetected via malicious mirrors, leading to code execution when victims fetch packages.","url":"https://insights.sbomify.com/CVE-2019-1000013/"}