# CVE-2014-1697: Code injection in n/a

> Remote attackers can execute arbitrary code on Siemens SIMATIC WinCC OA by sending crafted packets to the integrated web server.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/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:** 7 Feb 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-pjpr-3jp2-8fm3

## What is CVE-2014-1697?

CVE-2014-1697 is a high-severity code injection vulnerability in n/a, published on 7 Feb 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The integrated web server in Siemens SIMATIC WinCC OA before 3.12 P002 January allows remote attackers to execute arbitrary code via crafted packets to TCP port 4999.

## Which versions are affected by CVE-2014-1697?

It affects 1 product.


Products: Siemens Simatic Wincc Open Architecture.

## How do I fix CVE-2014-1697?

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

## Is CVE-2014-1697 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-3991](https://insights.sbomify.com/CVE-2018-3991/): Memory corruption in n/a (critical 10.0)
- [CVE-2018-13799](https://insights.sbomify.com/CVE-2018-13799/): Privilege escalation in SIMATIC WinCC OA V3.14 and prior (critical 9.1)
- [CVE-2014-1696](https://insights.sbomify.com/CVE-2014-1696/): Weak cryptography in n/a (medium 5.0)
- [CVE-2014-1698](https://insights.sbomify.com/CVE-2014-1698/): Path traversal in n/a (medium 5.0)
- [CVE-2014-1699](https://insights.sbomify.com/CVE-2014-1699/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-1697 and fix it if it is affected.

What it is: CVE-2014-1697 is a high-severity code injection vulnerability in n/a, published on 7 Feb 2014. 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-2014-1697 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-2014-1697/ (Markdown: https://insights.sbomify.com/CVE-2014-1697/index.md)
```

## Sources

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

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