# CVE-2008-3746: Null dereference in n/a

> Remote servers can crash the neon HTTP client library via a NULL pointer dereference in Digest authentication parsing, causing denial of service.

- **Severity:** Medium 4.3 (`AV:N/AC:M/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:** 27 Aug 2008
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2008-3746, GHSA-7mww-385g-p2jf

## What is CVE-2008-3746?

CVE-2008-3746 is a medium-severity vulnerability in n/a, published on 27 Aug 2008. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

neon 0.28.0 through 0.28.2 allows remote servers to cause a denial of service (NULL pointer dereference and crash) via vectors related to Digest authentication, Digest domain parameter support, and the parse_domain function.

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

It affects 1 product.


Products: Webdav Neon.

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

Upgrade to a fixed version.

## Is CVE-2008-3746 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2009-2473](https://insights.sbomify.com/CVE-2009-2473/): Denial of service in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

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

## Sources

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

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