# CVE-2004-2546: Multiple memory leaks in Samba before 3.0.6 allow attackers to cause a denial of service (memory consumption).


- **Severity:** Medium 6.4 (`AV:N/AC:L/Au:N/C:P/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 21 Nov 2005
- **Updated:** 8 Aug 2024
- **Also known as:** DEBIAN-CVE-2004-2546, GHSA-8v2x-hr7h-j8qx

## What is CVE-2004-2546?

CVE-2004-2546 is a medium-severity vulnerability in Samba Samba, published on 21 Nov 2005. 

### Official description

Multiple memory leaks in Samba before 3.0.6 allow attackers to cause a denial of service (memory consumption).

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

It affects 2 products.


Products: Samba Samba, Trustix Secure Linux.

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

Upgrade to a fixed version.

## Is CVE-2004-2546 being exploited?

There is no known exploitation of CVE-2004-2546 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-2546 and fix it if it is affected.

What it is: CVE-2004-2546 is a medium-severity vulnerability in Samba Samba, published on 21 Nov 2005. 
Exploitation: There is no known exploitation of CVE-2004-2546 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-2546/ (Markdown: https://insights.sbomify.com/CVE-2004-2546/index.md)
```

## Sources

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

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