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

> Remote authenticated operators can prevent kick or de-op actions via a race condition, bypassing administrative controls in the IRC server.

- **Severity:** Medium 6.0 (`AV:N/AC:M/Au:S/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Aug 2007
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2007-4410, GHSA-686m-wx69-7h93

## What is CVE-2007-4410?

CVE-2007-4410 is a medium-severity vulnerability in n/a, published on 18 Aug 2007. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

ircu 2.10.12.05 and earlier does not properly synchronize a kick action in certain cross scenarios, which allows remote authenticated operators to prevent later kick or de-op actions from non-local ops.

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

It affects 1 product.


Products: Universal Ircd Ircu.

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

Upgrade to a fixed version.

## Is CVE-2007-4410 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-4404](https://insights.sbomify.com/CVE-2007-4404/): Denial of service in n/a (high 7.8)
- [CVE-2007-4405](https://insights.sbomify.com/CVE-2007-4405/): Denial of service in n/a (high 7.8)
- [CVE-2007-4406](https://insights.sbomify.com/CVE-2007-4406/): Privilege escalation in n/a (high 7.5)
- [CVE-2007-4407](https://insights.sbomify.com/CVE-2007-4407/): Privilege escalation in n/a (medium 6.4)
- [CVE-2007-4409](https://insights.sbomify.com/CVE-2007-4409/): Race condition in n/a (medium 5.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-4410 is a medium-severity vulnerability in n/a, published on 18 Aug 2007. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2007-4410 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-4410/ (Markdown: https://insights.sbomify.com/CVE-2007-4410/index.md)
```

## Sources

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

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