# CVE-2013-2367: Code injection in n/a

> Remote attackers can execute arbitrary code on HP SiteScope servers when SOAP is enabled, requiring immediate patching.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Jul 2013
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-x8p9-cjx3-wx24

## What is CVE-2013-2367?

CVE-2013-2367 is a critical code injection vulnerability in n/a, published on 31 Jul 2013. It can be exploited over the network, with no action from the victim.

### Official description

Multiple unspecified vulnerabilities in HP SiteScope 11.20 and 11.21, when SOAP is used, allow remote attackers to execute arbitrary code via unknown vectors, aka ZDI-CAN-1678.

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

It affects 1 product.


Products: Hp Sitescope.

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

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

## Is CVE-2013-2367 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2013-2367 exists.

Public exploit code:

- HP SiteScope Remote Code Execution (metasploit)
- HP SiteScope (Windows) - Remote Code Execution (Metasploit) (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2012-3259](https://insights.sbomify.com/CVE-2012-3259/): Code injection in n/a (critical 10.0)
- [CVE-2012-3260](https://insights.sbomify.com/CVE-2012-3260/): Code injection in n/a (critical 10.0)
- [CVE-2012-3261](https://insights.sbomify.com/CVE-2012-3261/): Code injection in n/a (critical 10.0)
- [CVE-2012-3262](https://insights.sbomify.com/CVE-2012-3262/): Code injection in n/a (critical 10.0)
- [CVE-2012-3263](https://insights.sbomify.com/CVE-2012-3263/): Code injection in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2013-2367 is a critical code injection vulnerability in n/a, published on 31 Jul 2013. It can be exploited over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2013-2367 exists.

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-2367/ (Markdown: https://insights.sbomify.com/CVE-2013-2367/index.md)
```

## Sources

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

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