# CVE-2010-0359: Memory corruption in n/a

> Remote attackers can cause denial of service or execute arbitrary code via a buffer overflow in SSLv2 support.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Jan 2010
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-h436-qgjj-x35v

## What is CVE-2010-0359?

CVE-2010-0359 is a critical memory corruption vulnerability in n/a, published on 20 Jan 2010. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Buffer overflow in the SSLv2 support in Zeus Web Server before 4.3r5 allows remote attackers to cause a denial of service (daemon crash) or possibly execute arbitrary code via a long string in an invalid Client Hello message.

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

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

It affects 1 product.


Products: Zeus Zeus Web Server.

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

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

## Is CVE-2010-0359 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2010-0359 exists.

Public exploit code:

- Zeus Web Server 4.x - 'SSL2_CLIENT_HELLO' Remote Buffer Overflow (PoC) (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2010-0362](https://insights.sbomify.com/CVE-2010-0362/): Other in n/a (medium 5.0)
- [CVE-2010-0363](https://insights.sbomify.com/CVE-2010-0363/): Cross-site scripting in n/a (low 2.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2010-0359 is a critical memory corruption vulnerability in n/a, published on 20 Jan 2010. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2010-0359 exists.

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-0359/ (Markdown: https://insights.sbomify.com/CVE-2010-0359/index.md)
```

## Sources

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

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