# CVE-2007-4445: Denial of service in n/a

> Remote attackers can crash the rFactor daemon or block UDP ports by sending malformed network packets, causing service disruption.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Aug 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-v689-7vgf-r3r8

## What is CVE-2007-4445?

CVE-2007-4445 is a high-severity denial of service vulnerability in n/a, published on 21 Aug 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Image Space rFactor 1.250 and earlier allows remote attackers to cause a denial of service (daemon crash) via (1) an ID 0x30 packet, (2) an ID 0x38 packet, and an invalid 13-bit integer in (3) an ID 0x60 packet and (4) an ID 0x68 packet; and a denial of service (UDP port block) via (5) an ID 0x20 packet and (6) an ID 0x28 packet.

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

It affects 1 product.


Products: Rfactor Rfactor.

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

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

## Is CVE-2007-4445 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-4444](https://insights.sbomify.com/CVE-2007-4444/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-4445 is a high-severity denial of service vulnerability in n/a, published on 21 Aug 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2007-4445 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-4445/ (Markdown: https://insights.sbomify.com/CVE-2007-4445/index.md)
```

## Sources

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

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