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

> Remote attackers can cause a denial of service by sending crafted packets to specific ports on Emerson DeltaV controllers.

- **Severity:** Medium 6.1 (`AV:A/AC:L/Au:N/C:N/I:N/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:** 11 Mar 2013
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-9w3v-5m26-9mh6

## What is CVE-2012-4703?

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

### Official description

The Emerson DeltaV SE3006 through 11.3.1, DeltaV VE3005 through 10.3.1 and 11.x through 11.3.1, and DeltaV VE3006 through 10.3.1 and 11.x through 11.3.1 allow remote attackers to cause a denial of service (device restart) via a crafted packet on (1) TCP port 23, (2) UDP port 161, or (3) TCP port 513.

Weakness: CWE-399

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

It affects 3 products.


Products: Emerson Deltav Se3006 Sd Plus Controller, Emerson Deltav Ve3005 Controller Md, Emerson Deltav Ve3006 Controller Md Plus.

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

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

## Is CVE-2012-4703 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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