# CVE-2014-2519: Misconfiguration in n/a

> Remote attackers can access sensitive port information or cause denial of service due to a missing firewall in the default configuration.

- **Severity:** Medium 5.8 (`AV:N/AC:M/Au:N/C:P/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Jul 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-m924-ggx6-jfpw

## What is CVE-2014-2519?

CVE-2014-2519 is a medium-severity vulnerability in n/a, published on 19 Jul 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The default configuration of EMC RecoverPoint Appliance (RPA) 4.1 before 4.1.0.1 does not enable a firewall, which allows remote attackers to obtain potentially sensitive information about open ports, or cause a denial of service, by sending packets to many ports.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Emc Recoverpoint Appliance.

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

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

## Is CVE-2014-2519 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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