# CVE-2013-2341: Other in n/a

> Remote authenticated users can execute arbitrary code or obtain sensitive information on HP ProCurve, 3COM, and H3C network devices.

- **Severity:** High 7.1 (`AV:N/AC:H/Au:S/C:C/I:C/A:C`)
- **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:** 6 Jul 2013
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-39rq-5648-q49j

## What is CVE-2013-2341?

CVE-2013-2341 is a high-severity vulnerability in n/a, published on 6 Jul 2013. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Unspecified vulnerability on the HP ProCurve JC###A, JC###B, JD###A, JD###B, JE###A, JF###A, JF###B, JF###C, JG###A, 658250-B21, and 658247-B21; HP 3COM routers and switches; and HP H3C routers and switches allows remote authenticated users to execute arbitrary code or obtain sensitive information via unknown vectors.

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

It affects 15 products.


Products: Hp 3com Baseline Plus Switch, Hp 3com Router, Hp 3com Switch, Hp 3com Switch Taa Compliant, Hp 3com Taa Switch, Hp H3c Ethernet Switch, Hp H3c High Performance Main Processing Unit, Hp H3c Processing Module, Hp H3c Processor Module, Hp H3c Router, Hp H3c Routing Switch, Hp H3c Switch, Hp Procurve Router, Hp Procurve Switch, Hp Vpn Firewall Appliance.

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

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

## Is CVE-2013-2341 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-2340](https://insights.sbomify.com/CVE-2013-2340/): Other in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

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

## Sources

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

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