# CVE-2007-6123: Other in n/a

> Unspecified vulnerability in IRC Services allows attackers to potentially compromise the service, though specific impact and vectors are unknown.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 26 Nov 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-4mfp-5fwm-2mc7

## What is CVE-2007-6123?

CVE-2007-6123 is a critical vulnerability in n/a, published on 26 Nov 2007. 

### Official description

Unspecified vulnerability in IRC Services 5.1.8 has unknown impact and attack vectors.

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

It affects 1 product.


Products: Irc Services Irc Services.

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

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

## Is CVE-2007-6123 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-6122](https://insights.sbomify.com/CVE-2007-6122/): Denial of service in n/a (medium 5.0)
- [CVE-2007-3245](https://insights.sbomify.com/CVE-2007-3245/): Business logic in n/a (medium 5.0)
- [CVE-2007-3246](https://insights.sbomify.com/CVE-2007-3246/): Auth bypass in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-6123 is a critical vulnerability in n/a, published on 26 Nov 2007. 
Exploitation: There is no known exploitation of CVE-2007-6123 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-6123/ (Markdown: https://insights.sbomify.com/CVE-2007-6123/index.md)
```

## Sources

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

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