# CVE-2014-8518: Hardcoded credentials in n/a

> Local attackers can brute-force passwords due to a hard-coded salt in McAfee File and Removable Media Protection, compromising encrypted data.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Oct 2014
- **Updated:** 6 Aug 2024
- **Also known as:** CVE-2014-8565, GHSA-j89r-327h-pvjm

## What is CVE-2014-8518?

CVE-2014-8518 is a low-severity vulnerability in n/a, published on 29 Oct 2014. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The (1) Removable Media and (2) CD and DVD encryption offsite access options (formerly Endpoint Encryption for Removable Media or EERM) in McAfee File and Removable Media Protection (FRP) 4.3.0.x, and Endpoint Encryption for Files and Folders (EEFF) 3.2.x through 4.2.x, uses a hard-coded salt, which makes it easier for local users to obtain passwords via a brute force attack.

Weakness: CWE-255

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

It affects 2 products.


Products: Mcafee Endpoint Encryption for Files and Folders, Mcafee File and Removable Media Protection.

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

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

## Is CVE-2014-8518 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2014-8518 is a low-severity vulnerability in n/a, published on 29 Oct 2014. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-8518 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-8518/ (Markdown: https://insights.sbomify.com/CVE-2014-8518/index.md)
```

## Sources

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

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