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

> Local attackers can cause a denial of service in the MCS translation daemon by submitting large sensitivity label ranges.

- **Severity:** Low 1.9 (`AV:L/AC:M/Au:N/C:N/I:N/A:P`)
- **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:** Yes
- **Published:** 10 Nov 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-gf2x-9g2r-6hp6, RHSA-2007:0542

## What is CVE-2007-4570?

CVE-2007-4570 is a low-severity denial of service vulnerability in n/a, published on 10 Nov 2007. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Algorithmic complexity vulnerability in the MCS translation daemon in mcstrans 0.2.3 allows local users to cause a denial of service (temporary daemon outage) via a large range of compartments in sensitivity labels.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mcstrans` | Red Hat:enterprise_linux:5::client | All versions | 0:0.2.6-1.el5 |
| `mcstrans-debuginfo` | Red Hat:enterprise_linux:5::client | All versions | 0:0.2.6-1.el5 |
| `mcstrans` | Red Hat:enterprise_linux:5::server | All versions | 0:0.2.6-1.el5 |
| `mcstrans-debuginfo` | Red Hat:enterprise_linux:5::server | All versions | 0:0.2.6-1.el5 |

Products: Redhat Mcstrans.

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

Apply the vendor's patch.

## Is CVE-2007-4570 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2007-4570 is a low-severity denial of service vulnerability in n/a, published on 10 Nov 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-4570 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-4570/ (Markdown: https://insights.sbomify.com/CVE-2007-4570/index.md)
```

## Sources

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

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