# CVE-2014-4501: Memory corruption in n/a

> Remote pool servers can trigger stack-based buffer overflows in mining software via long URLs, potentially leading to code execution or crashes.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Jul 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-wm22-f5pr-qxv3

## What is CVE-2014-4501?

CVE-2014-4501 is a critical memory corruption vulnerability in n/a, published on 23 Jul 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2014-4501?

It affects 3 products.


Products: Bfgminer Bfgminer, Cgminer Project Cgminer, Sgminer Project Sgminer.

## How do I fix CVE-2014-4501?

No fix has been published for CVE-2014-4501 yet. Limit exposure of the affected software until one is available.

## Is CVE-2014-4501 being exploited?

There is no known exploitation of CVE-2014-4501 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2014-4502](https://insights.sbomify.com/CVE-2014-4502/): Memory corruption in n/a (critical 10.0)
- [CVE-2018-10058](https://insights.sbomify.com/CVE-2018-10058/): Memory corruption in n/a (high 8.8)
- [CVE-2018-10057](https://insights.sbomify.com/CVE-2018-10057/): Path traversal in n/a (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-4501 and fix it if it is affected.

What it is: CVE-2014-4501 is a critical memory corruption vulnerability in n/a, published on 23 Jul 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-4501 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2014-4501/ (Markdown: https://insights.sbomify.com/CVE-2014-4501/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2014-4501
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2014-4501
- OSV: https://osv.dev/vulnerability/CVE-2014-4501

---
From sbomify Insights: https://insights.sbomify.com/CVE-2014-4501/
Summaries are generated and may contain mistakes; the official description above is the record.