# CVE-2010-2448: Null dereference in n/a

> Authenticated users can crash the ZNC IRC bouncer by requesting traffic statistics while an unauthenticated connection is active.

- **Severity:** Low 3.5 (`AV:N/AC:M/Au:S/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Jul 2010
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-9fjx-4w4f-2p9x

## What is CVE-2010-2448?

CVE-2010-2448 is a low-severity vulnerability in n/a, published on 12 Jul 2010. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

znc.cpp in ZNC before 0.092 allows remote authenticated users to cause a denial of service (crash) by requesting traffic statistics when there is an active unauthenticated connection, which triggers a NULL pointer dereference, as demonstrated using (1) a traffic link in the web administration pages or (2) the traffic command in the /znc shell.

## Which versions are affected by CVE-2010-2448?

It affects 1 product.


Products: Znc Znc.

## How do I fix CVE-2010-2448?

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

## Is CVE-2010-2448 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-12816](https://insights.sbomify.com/CVE-2019-12816/): Privilege escalation in n/a (high 8.8)
- [CVE-2010-2488](https://insights.sbomify.com/CVE-2010-2488/): Null dereference in znc (high 7.5)
- [CVE-2009-2658](https://insights.sbomify.com/CVE-2009-2658/): Path traversal in n/a (high 7.5)
- [CVE-2009-0759](https://insights.sbomify.com/CVE-2009-0759/): Code injection in n/a (medium 6.5)
- [CVE-2010-2812](https://insights.sbomify.com/CVE-2010-2812/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-2448 and fix it if it is affected.

What it is: CVE-2010-2448 is a low-severity vulnerability in n/a, published on 12 Jul 2010. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2010-2448 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-2010-2448/ (Markdown: https://insights.sbomify.com/CVE-2010-2448/index.md)
```

## Sources

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

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