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

> Local attackers can escalate privileges to kernel level by sending crafted IOCTL requests to the Online Armor firewall driver.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Jul 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-66r2-9m7r-3cvc

## What is CVE-2009-2450?

CVE-2009-2450 is a high-severity vulnerability in n/a, published on 13 Jul 2009. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The OAmon.sys kernel driver 3.1.0.0 and earlier in Tall Emu Online Armor Personal Firewall AV+ before 3.5.0.12, and Personal Firewall 3.5 before 3.5.0.14, allows local users to gain privileges via crafted METHOD_NEITHER IOCTL requests to \Device\OAmon containing arbitrary kernel addresses, as demonstrated using the 0x830020C3 IOCTL.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 2 products.


Products: Tallemu Online Armor Personal Firewall Av\+, Tallemu Personal Firewall.

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

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

## Is CVE-2009-2450 being exploited?

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

Public exploit code:

- Online Armor < 3.5.0.12 - 'OAmon.sys' Local Privilege Escalation (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2009-2450 is a high-severity vulnerability in n/a, published on 13 Jul 2009. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-2450 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-2450/ (Markdown: https://insights.sbomify.com/CVE-2009-2450/index.md)
```

## Sources

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

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