# CVE-2012-5345: Denial of service in n/a

> Remote attackers can crash the Tiny TCP/IP server via a buffer overflow in the Rcmd.bat command server on port 23.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Oct 2012
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-rhr6-cp3p-vq4r

## What is CVE-2012-5345?

CVE-2012-5345 is a medium-severity denial of service vulnerability in n/a, published on 9 Oct 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Buffer overflow in the Remote command server (Rcmd.bat) in IpTools (aka Tiny TCP/IP server) 0.1.4 allows remote attackers to cause a denial of service (crash) via a long string to TCP port 23.

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

## Which versions are affected by CVE-2012-5345?

It affects 1 product.


Products: Kepler Lam Iptools.

## How do I fix CVE-2012-5345?

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

## Is CVE-2012-5345 being exploited?

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

Public exploit code:

- IPtools 0.1.4 - Remote Buffer Overflow (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2012-5344](https://insights.sbomify.com/CVE-2012-5344/): Path traversal in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-5345 and fix it if it is affected.

What it is: CVE-2012-5345 is a medium-severity denial of service vulnerability in n/a, published on 9 Oct 2012. 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-2012-5345 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-2012-5345/ (Markdown: https://insights.sbomify.com/CVE-2012-5345/index.md)
```

## Sources

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

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