# CVE-2009-3843: File upload in n/a

> Remote attackers can execute arbitrary code via unrestricted file upload using a hidden Tomcat manager account in HP Operations Manager.

- **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 needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Nov 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-vcf2-959x-5ggc

## What is CVE-2009-3843?

CVE-2009-3843 is a critical vulnerability in n/a, published on 24 Nov 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

HP Operations Manager 8.10 on Windows contains a "hidden account" in the XML file that specifies Tomcat users, which allows remote attackers to conduct unrestricted file upload attacks, and thereby execute arbitrary code, by using the org.apache.catalina.manager.HTMLManagerServlet class to make requests to manager/html/upload.

Weakness: CWE-264

## Which versions are affected by CVE-2009-3843?

It affects 1 product.


Products: Hp Operations Manager.

## How do I fix CVE-2009-3843?

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

## Is CVE-2009-3843 being exploited?

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

Public exploit code:

- Apache Tomcat Manager Application Deployer Authenticated Code Execution (metasploit)
- Apache Tomcat Manager Authenticated Upload Code Execution (metasploit)
- Apache Tomcat Manager - Application Deployer (Authenticated) Code Execution (Metasploit) (exploitdb)
- Tomcat Application Manager Login Utility (metasploit)

## Other vulnerabilities in n/a

- [CVE-2016-1985](https://insights.sbomify.com/CVE-2016-1985/): Deserialization in n/a (critical 10.0)
- [CVE-2014-2648](https://insights.sbomify.com/CVE-2014-2648/): Other in n/a (critical 10.0)
- [CVE-2009-4189](https://insights.sbomify.com/CVE-2009-4189/): Hardcoded credentials in n/a (critical 10.0)
- [CVE-2009-3099](https://insights.sbomify.com/CVE-2009-3099/): Other in n/a (critical 10.0)
- [CVE-2016-4373](https://insights.sbomify.com/CVE-2016-4373/): Deserialization in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-3843 and fix it if it is affected.

What it is: CVE-2009-3843 is a critical vulnerability in n/a, published on 24 Nov 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-3843 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-2009-3843/ (Markdown: https://insights.sbomify.com/CVE-2009-3843/index.md)
```

## Sources

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

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