# CVE-2005-3269: Memory corruption in n/a

> Remote attackers can crash the admin server, while local users can gain root privileges via a stack-based buffer overflow in the HTTP interface.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Oct 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-wcrv-7ccm-jh9r

## What is CVE-2005-3269?

CVE-2005-3269 is a high-severity memory corruption vulnerability in n/a, published on 20 Oct 2005. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Stack-based buffer overflow in help.cgi in the HTTP administrative interface for (1) Sun Java System Directory Server 5.2 2003Q4, 2004Q2, and 2005Q1, (2) Red Hat Directory Server and (3) Certificate Server before 7.1 SP1, (4) Sun ONE Directory Server 5.1 SP4 and earlier, and (5) Sun ONE Administration Server 5.2 allows remote attackers to cause a denial of service (admin server crash), or local users to gain root privileges.

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

## Which versions are affected by CVE-2005-3269?

It affects 4 products.


Products: Sun Java System Directory Proxy Server, Sun Java System Directory Server, Sun One Administration Server, Sun One Directory Server.

## How do I fix CVE-2005-3269?

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

## Is CVE-2005-3269 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-3269 and fix it if it is affected.

What it is: CVE-2005-3269 is a high-severity memory corruption vulnerability in n/a, published on 20 Oct 2005. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2005-3269 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-2005-3269/ (Markdown: https://insights.sbomify.com/CVE-2005-3269/index.md)
```

## Sources

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

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