# CVE-2004-0686: Memory corruption in n/a

> Buffer overflow in Samba when hash mangling is enabled allows attackers to potentially execute code or cause denial of service.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not stated
- **Fix available:** Yes
- **Published:** 23 Jul 2004
- **Updated:** 8 Aug 2024
- **Also known as:** DEBIAN-CVE-2004-0686, GHSA-7c6c-h82r-p2cf

## What is CVE-2004-0686?

CVE-2004-0686 is a medium-severity memory corruption vulnerability in Samba Samba, published on 23 Jul 2004. It can be exploited over the network.

### Official description

Buffer overflow in Samba 2.2.x to 2.2.9, and 3.0.0 to 3.0.4, when the "mangling method = hash" option is enabled in smb.conf, has unknown impact and attack vectors.

## Which versions are affected by CVE-2004-0686?

It affects 2 products.


Products: Samba Samba, Trustix Secure Linux.

## How do I fix CVE-2004-0686?

Upgrade to a fixed version.

## Is CVE-2004-0686 being exploited?

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

## Other vulnerabilities in Samba Samba

- [CVE-2012-1182](https://insights.sbomify.com/CVE-2012-1182/): Integer overflow in n/a (critical 10.0)
- [CVE-2007-2446](https://insights.sbomify.com/CVE-2007-2446/): Memory corruption in n/a (critical 10.0)
- [CVE-2004-0600](https://insights.sbomify.com/CVE-2004-0600/): Memory corruption in n/a (critical 10.0)
- [CVE-1999-0810](https://insights.sbomify.com/CVE-1999-0810/): Denial of service in n/a (critical 10.0)
- [CVE-1999-0182](https://insights.sbomify.com/CVE-1999-0182/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-0686 and fix it if it is affected.

What it is: CVE-2004-0686 is a medium-severity memory corruption vulnerability in Samba Samba, published on 23 Jul 2004. It can be exploited over the network.
Exploitation: There is no known exploitation of CVE-2004-0686 in the wild and no public exploit code.

Affected product: Samba Samba. 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-2004-0686/ (Markdown: https://insights.sbomify.com/CVE-2004-0686/index.md)
```

## Sources

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

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