# CVE-2009-2344: Privilege escalation in n/a

> Authenticated users can escalate privileges by manipulating the admin parameter in the web management interface of Sourcefire Defense Center.

- **Severity:** Critical 9.0 (`AV:N/AC:L/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:** 7 Jul 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-7pjx-r98g-p4qj

## What is CVE-2009-2344?

CVE-2009-2344 is a critical vulnerability in n/a, published on 7 Jul 2009. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The web-based management interfaces in Sourcefire Defense Center (DC) and 3D Sensor before 4.8.2 allow remote authenticated users to gain privileges via a $admin value for the admin parameter in an edit action to admin/user/user.cgi and unspecified other components.

Weakness: CWE-264

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

It affects 2 products.


Products: Sourcefire 3d Sensor, Sourcefire Defense Center.

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

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

## Is CVE-2009-2344 being exploited?

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

Public exploit code:

- Sourcefire 3D Sensor & Defense Center 4.8.x - Privilege Escalation (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2009-2344 is a critical vulnerability in n/a, published on 7 Jul 2009. Any signed-in user can exploit it 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-2009-2344 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-2344/ (Markdown: https://insights.sbomify.com/CVE-2009-2344/index.md)
```

## Sources

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

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