# CVE-2008-1925: Memory corruption in n/a

> Remote attackers can crash the InspIRCd daemon via buffer overflow in specific modules, requiring those modules to be enabled.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 Apr 2008
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2008-1925, GHSA-qcpx-4xgf-735p

## What is CVE-2008-1925?

CVE-2008-1925 is a medium-severity memory corruption vulnerability in n/a, published on 23 Apr 2008. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Buffer overflow in InspIRCd before 1.1.18, when using the namesx and uhnames modules, allows remote attackers to cause a denial of service (daemon crash) via a large number of channel users with crafted nicknames, idents, and long hostnames.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2008-1925?

It affects 1 product.


Products: Inspircd Inspircd.

## How do I fix CVE-2008-1925?

Upgrade to a fixed version.

## Is CVE-2008-1925 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2012-6696](https://insights.sbomify.com/CVE-2012-6696/): Integer overflow in n/a (critical 9.8)
- [CVE-2012-1836](https://insights.sbomify.com/CVE-2012-1836/): Memory corruption in n/a (high 7.5)
- [CVE-2019-20918](https://insights.sbomify.com/CVE-2019-20918/): Use after free in n/a (medium 6.5)
- [CVE-2021-33586](https://insights.sbomify.com/CVE-2021-33586/): Use after free in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-1925 and fix it if it is affected.

What it is: CVE-2008-1925 is a medium-severity memory corruption vulnerability in n/a, published on 23 Apr 2008. 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-2008-1925 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-2008-1925/ (Markdown: https://insights.sbomify.com/CVE-2008-1925/index.md)
```

## Sources

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

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