# CVE-2014-8530: Information disclosure in n/a

> Remote attackers can obtain sensitive information or cause denial of service in McAfee Network Data Loss Prevention via simultaneous logins.

- **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:** No
- **Published:** 29 Oct 2014
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-6w66-6h83-cmc9

## What is CVE-2014-8530?

CVE-2014-8530 is a high-severity vulnerability in n/a, published on 29 Oct 2014. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Unspecified vulnerability in McAfee Network Data Loss Prevention (NDLP) before 9.3 allows remote attackers to obtain sensitive information, affect integrity, or cause a denial of service via unknown vectors, related to simultaneous logins.

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

It affects 1 product.


Products: Mcafee Network Data Loss Prevention.

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

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

## Is CVE-2014-8530 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-4014](https://insights.sbomify.com/CVE-2017-4014/): Auth bypass in Network Data Loss Prevention (NDLP) (high 8.0)
- [CVE-2017-3968](https://insights.sbomify.com/CVE-2017-3968/): Auth bypass in Network Data Loss Prevention (NDLP) (high 7.5)
- [CVE-2017-3935](https://insights.sbomify.com/CVE-2017-3935/): Information disclosure in Network Data Loss Prevention (high 7.5)
- [CVE-2014-8522](https://insights.sbomify.com/CVE-2014-8522/): Auth bypass in n/a (high 7.5)
- [CVE-2014-8533](https://insights.sbomify.com/CVE-2014-8533/): Other in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-8530 is a high-severity vulnerability in n/a, published on 29 Oct 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-8530 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-8530/ (Markdown: https://insights.sbomify.com/CVE-2014-8530/index.md)
```

## Sources

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

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