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

> Local attackers can exploit race conditions in CerbNG to bypass system call interposition, potentially gaining privileges or evading auditing on FreeBSD.

- **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-gwmh-6579-2hjm

## What is CVE-2007-4303?

CVE-2007-4303 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 (1) certain rules and (2) argument copying during VM protection, in CerbNG for FreeBSD 4.8 allow local users to defeat system call interposition and possibly gain privileges or bypass auditing, as demonstrated by modifying command lines in log-exec.cb.

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

It affects 1 product.


Products: Cerb Cerbng.

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

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

## Is CVE-2007-4303 being exploited?

There is no known exploitation of CVE-2007-4303 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2007-4304](https://insights.sbomify.com/CVE-2007-4304/): Race condition in n/a (medium 6.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-4303 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: There is no known exploitation of CVE-2007-4303 in the wild and no public exploit code.

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-4303/ (Markdown: https://insights.sbomify.com/CVE-2007-4303/index.md)
```

## Sources

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

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