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

> Attackers can trigger a stack-based buffer overflow in FreeRADIUS via long password hashes, potentially causing crashes or executing arbitrary code.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 2 Nov 2014
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2014-2015, GHSA-4w6w-6xrm-w35q, MGASA-2014-0088, RHSA-2015:1287

## What is CVE-2014-2015?

CVE-2014-2015 is a high-severity memory corruption vulnerability in n/a, published on 2 Nov 2014. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Stack-based buffer overflow in the normify function in the rlm_pap module (modules/rlm_pap/rlm_pap.c) in FreeRADIUS 2.x, possibly 2.2.3 and earlier, and 3.x, possibly 3.0.1 and earlier, might allow attackers to cause a denial of service (crash) and possibly execute arbitrary code via a long password hash, as demonstrated by an SSHA hash.

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

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `freeradius` | Red Hat:enterprise_linux:6::server | All versions | 0:2.2.6-4.el6 |
| `freeradius-debuginfo` | Red Hat:enterprise_linux:6::server | All versions | 0:2.2.6-4.el6 |
| `freeradius-krb5` | Red Hat:enterprise_linux:6::server | All versions | 0:2.2.6-4.el6 |
| `freeradius-ldap` | Red Hat:enterprise_linux:6::server | All versions | 0:2.2.6-4.el6 |
| `freeradius-mysql` | Red Hat:enterprise_linux:6::server | All versions | 0:2.2.6-4.el6 |
| `freeradius-perl` | Red Hat:enterprise_linux:6::server | All versions | 0:2.2.6-4.el6 |
| `freeradius-postgresql` | Red Hat:enterprise_linux:6::server | All versions | 0:2.2.6-4.el6 |
| `freeradius-python` | Red Hat:enterprise_linux:6::server | All versions | 0:2.2.6-4.el6 |
| `freeradius-unixODBC` | Red Hat:enterprise_linux:6::server | All versions | 0:2.2.6-4.el6 |
| `freeradius-utils` | Red Hat:enterprise_linux:6::server | All versions | 0:2.2.6-4.el6 |
| `freeradius` | Red Hat:enterprise_linux:6::workstation | All versions | 0:2.2.6-4.el6 |
| `freeradius-debuginfo` | Red Hat:enterprise_linux:6::workstation | All versions | 0:2.2.6-4.el6 |
| `freeradius-krb5` | Red Hat:enterprise_linux:6::workstation | All versions | 0:2.2.6-4.el6 |
| `freeradius-ldap` | Red Hat:enterprise_linux:6::workstation | All versions | 0:2.2.6-4.el6 |
| `freeradius-mysql` | Red Hat:enterprise_linux:6::workstation | All versions | 0:2.2.6-4.el6 |
| `freeradius-perl` | Red Hat:enterprise_linux:6::workstation | All versions | 0:2.2.6-4.el6 |
| `freeradius-postgresql` | Red Hat:enterprise_linux:6::workstation | All versions | 0:2.2.6-4.el6 |
| `freeradius-python` | Red Hat:enterprise_linux:6::workstation | All versions | 0:2.2.6-4.el6 |
| `freeradius-unixODBC` | Red Hat:enterprise_linux:6::workstation | All versions | 0:2.2.6-4.el6 |
| `freeradius-utils` | Red Hat:enterprise_linux:6::workstation | All versions | 0:2.2.6-4.el6 |

Products: Freeradius Freeradius.

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

Apply the vendor's patch.

## Is CVE-2014-2015 being exploited?

There is no known exploitation of CVE-2014-2015 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-2015-8764](https://insights.sbomify.com/CVE-2015-8764/): Memory corruption in n/a (high 8.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-2015 is a high-severity memory corruption vulnerability in n/a, published on 2 Nov 2014. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-2015 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-2015/ (Markdown: https://insights.sbomify.com/CVE-2014-2015/index.md)
```

## Sources

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

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