Hex package manager version 0.14.0 through 0.18.2 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.19.
CVE-2019-1000012
HIGHNVD 8.88.8—
EchelonGraph scoreMEDIUM confidence
Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2022-05-13. NVD baseline CVSS 8.8; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
8.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 8.8Exploit: NoneExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.8
- EG Score
- 8.8(medium)
- EPSS
- 54.8%
- KEV
- Not listed
Published
February 4, 2019
Last Modified
November 21, 2024
References (4)
- cve@mitrehttps://github.com/hexpm/hex/pull/646
- cve@mitrehttps://github.com/hexpm/hex/pull/651
- af854a3a-2127-422b-91ae-364da2661108https://github.com/hexpm/hex/pull/646
- af854a3a-2127-422b-91ae-364da2661108https://github.com/hexpm/hex/pull/651
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Frequently asked(5)
What is CVE-2019-1000012?
CVE-2019-1000012 is a high vulnerability published on February 4, 2019. Hex package manager version 0.14.0 through 0.18.2 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…
When was CVE-2019-1000012 disclosed?
CVE-2019-1000012 was first published in the National Vulnerability Database on February 4, 2019, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2019-1000012 actively exploited?
CVE-2019-1000012 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 54.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2019-1000012?
CVE-2019-1000012 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2019-1000012?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-1000012, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2019-1000012
Is Your Infrastructure Affected by CVE-2019-1000012?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.