# CVE-2000-1183: Memory corruption in n/a

> Attackers can execute arbitrary commands on Linux systems running a vulnerable SOCKS5 server by sending a long connection request.

- **Severity:** High 7.2 (`AV:L/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:** 19 Dec 2000
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-j648-847p-926p

## What is CVE-2000-1183?

CVE-2000-1183 is a high-severity memory corruption vulnerability in n/a, published on 19 Dec 2000. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Buffer overflow in socks5 server on Linux allows attackers to execute arbitrary commands via a long connection request.

## Which versions are affected by CVE-2000-1183?

It affects 1 product.


Products: Nec Socks 5.

## How do I fix CVE-2000-1183?

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

## Is CVE-2000-1183 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2002-2368](https://insights.sbomify.com/CVE-2002-2368/): Memory corruption in n/a (critical 10.0)
- [CVE-1999-1435](https://insights.sbomify.com/CVE-1999-1435/): Memory corruption in n/a (high 7.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2000-1183 and fix it if it is affected.

What it is: CVE-2000-1183 is a high-severity memory corruption vulnerability in n/a, published on 19 Dec 2000. 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-2000-1183 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-2000-1183/ (Markdown: https://insights.sbomify.com/CVE-2000-1183/index.md)
```

## Sources

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

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