# CVE-2007-4305: Race condition in n/a

> Local attackers can exploit race conditions in Systrace to bypass system call interposition and access control policies on NetBSD and OpenBSD.

- **Severity:** Medium 6.2 (`AV:L/AC:H/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 Aug 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-3vw3-g8hp-j327

## What is CVE-2007-4305?

CVE-2007-4305 is a medium-severity vulnerability in n/a, published on 13 Aug 2007. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Multiple race conditions in the (1) Sudo monitor mode and (2) Sysjail policies in Systrace on NetBSD and OpenBSD allow local users to defeat system call interposition, and consequently bypass access control policy and auditing.

## Which versions are affected by CVE-2007-4305?

It affects 3 products.


Products: Sysjail Sysjail, Systrace Systrace, Todd Miller Sudo.

## How do I fix CVE-2007-4305?

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

## Is CVE-2007-4305 being exploited?

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

Public exploit code:

- Systrace - Multiple System Call Wrappers Concurrency Vulnerabilities (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-4305 and fix it if it is affected.

What it is: CVE-2007-4305 is a medium-severity vulnerability in n/a, published on 13 Aug 2007. 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-2007-4305 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-2007-4305/ (Markdown: https://insights.sbomify.com/CVE-2007-4305/index.md)
```

## Sources

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

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