CVE-2014-1699
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedSiemens SIMATIC WinCC OA before 3.12 P002 January allows remote attackers to cause a denial of service (monitoring-service outage) via malformed HTTP requests to port 4999.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceSiemens SIMATIC WinCC OA versions prior to 3.12 P002 January contain a denial-of-service vulnerability in the monitoring service component. Remote attackers can send malformed HTTP requests to port 4999, causing the monitoring service to fail and resulting in an outage.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 3.12CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- None
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/A:P
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm Siemens SIMATIC WinCC OA installationCheck for WinCC OA installation on the system - look for installation directories (commonly C:\Program Files\Siemens\WinCC_OA or /opt/siemens/wincc_oa on Linux) or verify via system program listingsAffected if If WinCC OA is not present, this CVE does not apply to the system
-
Determine installed WinCC OA versionLocate the version information in the WinCC OA installation - check the product version through Windows Programs and Features, or look for version files in the installation directory such as version.txt or in the Manager configurationAffected if If version is prior to 3.12 P002 January (any version 3.12 or earlier without the P002 patch), the system is vulnerable
-
Verify monitoring service is runningCheck if the WinCC OA monitoring service component is enabled and running - look for the monitoring manager process (commonly named wccoaMonitor or similar) in running processes, or check the WinCC OA manager status via the SCADA management consoleAffected if If the monitoring service is not running or not installed, the specific DoS vector may not be exploitable
-
Check network exposure of port 4999Verify if port 4999 (the monitoring service HTTP port) is listening and accessible - use netstat, firewall rules, or port scanning tools to determine if port 4999 is bound to a network interface accessible from other hostsAffected if If port 4999 is exposed to untrusted network segments, remote attackers can send malformed HTTP requests to trigger the denial of service
System is affected if WinCC OA version is prior to 3.12 P002 January AND the monitoring service is enabled with port 4999 network-accessible, allowing remote attackers to cause a denial of service.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade to Siemens SIMATIC WinCC OA version 3.12 P002 January or later to remediate this vulnerability. If immediate patching is not possible, consider network segmentation to restrict unauthorized access to port 4999.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-1699 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2014-1699 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data