CVE-2014-4501 json
Multiple stack-based buffer overflows in sgminer before 4.2.2, cgminer before 4.3.5, and BFGMiner before 3.3.0 allow remote pool servers to…
published 2014-07-23 12 y ago modified 2026-06-17 4 mo ago also EUVD-2014-4428
- cvss
- 10.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.9%
- EPSS 2.9% chance of exploitation in 30 days, percentile 87%
- public exploits
- 0
- none known
Summary
Multiple stack-based buffer overflows in sgminer before 4.2.2, cgminer before 4.3.5, and BFGMiner before 3.3.0 allow remote pool servers to have unspecified impact via a long URL in a client.reconnect stratum message to the (1) extract_sockaddr or (2) parse_reconnect functions in util.c.
Patch / fix
Exploit prediction
2.91% chance of exploitation in the next 30 days, higher than 87% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- github.com https://github.com/sgminer-dev/sgminer/commit/78cc408369bdbbd440196c93574098d1482efbce referenced PoC, tagged "exploit" by a source, unverified
- github.com https://github.com/ckolivas/cgminer/commit/e1c5050734123973b99d181c45e74b2cbb00272e referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 10.0 | AV:N/AC:L/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
References
-
github.com
/luke-jr/bfgminer/commit/c80ad8548251eb0e15329fc240c89070640c9d79
patch
-
github.com
/sgminer-dev/sgminer/commit/78cc408369bdbbd440196c93574098d1482efbce
exploit, patch
-
github.com
/ckolivas/cgminer/commit/e1c5050734123973b99d181c45e74b2cbb00272e
exploit, patch
-
github.com
/sgminer-dev/sgminer/commit/b65574bef233474e915fdf18614aa211e31cc6c2
patch
-
seclists.org
/fulldisclosure/2014/Jul/118
mailing-list
Sources
- CVE List CVE-2014-4501
- NVD CVE-2014-4501
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.