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

> Remote attackers can cause denial of service in Koyo ECOM Ethernet modules via unspecified vectors, impacting industrial network availability.

- **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:** 13 Apr 2012
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-f89q-4x47-3fph

## What is CVE-2012-1809?

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

### Official description

The web server in the ECOM Ethernet module in Koyo H0-ECOM, H0-ECOM100, H2-ECOM, H2-ECOM-F, H2-ECOM100, H4-ECOM, H4-ECOM-F, and H4-ECOM100 allows remote attackers to cause a denial of service (resource consumption) via unspecified vectors.

Weakness: CWE-399

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

It affects 8 products.


Products: Koyo H0-Ecom, Koyo H0-Ecom100, Koyo H2-Ecom, Koyo H2-Ecom-F, Koyo H2-Ecom100, Koyo H4-Ecom, Koyo H4-Ecom-F, Koyo H4-Ecom100.

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

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

## Is CVE-2012-1809 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2012-1805](https://insights.sbomify.com/CVE-2012-1805/): Memory corruption in n/a (critical 10.0)
- [CVE-2012-1808](https://insights.sbomify.com/CVE-2012-1808/): Missing authorization in n/a (critical 10.0)
- [CVE-2012-1806](https://insights.sbomify.com/CVE-2012-1806/): Weak cryptography in n/a (high 7.5)
- [CVE-2012-1807](https://insights.sbomify.com/CVE-2012-1807/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

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

## Sources

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

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