# CVE-2009-0343: Security feature bypass in n/a

> Local attackers can bypass Systrace access restrictions on x86_64 Linux by exploiting race conditions in 32-bit syscall monitoring.

- **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:** 29 Jan 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-rvg6-xg72-xc4w

## What is CVE-2009-0343?

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

### Official description

Niels Provos Systrace 1.6f and earlier on the x86_64 Linux platform allows local users to bypass intended access restrictions by making a 32-bit syscall with a syscall number that corresponds to a policy-compliant 64-bit syscall, related to race conditions that occur in monitoring 64-bit processes.

Weakness: CWE-264

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

It affects 1 product.


Products: Niels Provos Systrace.

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

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

## Is CVE-2009-0343 being exploited?

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

Public exploit code:

- Systrace 1.x (Linux Kernel x64) - Aware Local Privilege Escalation (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2009-0343 is a high-severity vulnerability in n/a, published on 29 Jan 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-0343 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-0343/ (Markdown: https://insights.sbomify.com/CVE-2009-0343/index.md)
```

## Sources

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

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