# CVE-2015-8764: Memory corruption in n/a

> An off-by-one error in FreeRADIUS EAP-PWD module allows buffer overflow, potentially leading to code execution or service disruption.

- **Severity:** High 8.1 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Mar 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-3rpp-wj27-m2p9

## What is CVE-2015-8764?

CVE-2015-8764 is a high-severity memory corruption vulnerability in n/a, published on 27 Mar 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Off-by-one error in the EAP-PWD module in FreeRADIUS 3.0 through 3.0.8, which triggers a buffer overflow.

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

## Which versions are affected by CVE-2015-8764?

It affects 1 product.


Products: Freeradius Freeradius.

## How do I fix CVE-2015-8764?

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

## Is CVE-2015-8764 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-10979](https://insights.sbomify.com/CVE-2017-10979/): Memory corruption in n/a (critical 9.8)
- [CVE-2017-10984](https://insights.sbomify.com/CVE-2017-10984/): Memory corruption in n/a (critical 9.8)
- [CVE-2017-9148](https://insights.sbomify.com/CVE-2017-9148/): Auth bypass in n/a (critical 9.8)
- [CVE-2015-8763](https://insights.sbomify.com/CVE-2015-8763/): Memory corruption in n/a (high 8.1)
- [CVE-2005-4746](https://insights.sbomify.com/CVE-2005-4746/): Memory corruption in n/a (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-8764 and fix it if it is affected.

What it is: CVE-2015-8764 is a high-severity memory corruption vulnerability in n/a, published on 27 Mar 2017. 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-2015-8764 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-2015-8764/ (Markdown: https://insights.sbomify.com/CVE-2015-8764/index.md)
```

## Sources

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

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