# CVE-2013-4840: Denial of service in n/a

> Remote attackers can cause a denial of service in HP and H3C VPN Firewall Module products via unspecified vectors.

- **Severity:** High 7.8 (`AV:N/AC:L/Au:N/C:N/I:N/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Jul 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-xrgv-hpqj-2pcx

## What is CVE-2013-4840?

CVE-2013-4840 is a high-severity denial of service vulnerability in n/a, published on 28 Jul 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Unspecified vulnerability in HP and H3C VPN Firewall Module products SECPATH1000FE before 5.20.R3177 and SECBLADEFW before 5.20.R3177 allows remote attackers to cause a denial of service via unknown vectors.

## Which versions are affected by CVE-2013-4840?

It affects 17 products.


Products: H3c F1000-E Vpn Firewall, H3c S5820 Secblade Vpn Firewall Module, H3c S7500e Secblade Vpn Firewall Module, H3c S9500e Secblade Vpn Firewall Module, H3c Secbladefw, H3c Secpath1000fe, H3c Sr66 Gigabit Firewall Module, H3c Sr88 Firewall Processing Module, Hp 10500\/7500 Advanced Vpn Firewall Module, Hp 12500 Vpn Firewall Module, Hp 5820 Vpn Firewall Module, Hp 6600 Firewall Processing Rtr Module, Hp 8800 Firewall Processing Module, Hp 9500 Vpn Firewall Module, Hp S1000-E Vpn Firewall Appliance, Hp Secbladefw, Hp Secpath1000fe.

## How do I fix CVE-2013-4840?

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

## Is CVE-2013-4840 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-4840 and fix it if it is affected.

What it is: CVE-2013-4840 is a high-severity denial of service vulnerability in n/a, published on 28 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-2013-4840 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-2013-4840/ (Markdown: https://insights.sbomify.com/CVE-2013-4840/index.md)
```

## Sources

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

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