CVE-2013-0675
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 · uneditedBuffer overflow in CCEServer (aka the central communications component) in Siemens WinCC before 7.2, as used in SIMATIC PCS7 before 8.0 SP1 and other products, allows remote attackers to cause a denial of service via a crafted packet.
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 · high confidenceBuffer overflow vulnerability in Siemens WinCC's CCEServer (central communications component) allows remote attackers to cause denial of service via crafted packets. The vulnerability affects WinCC versions before 7.2 and SIMATIC PCS7 versions before 8.0 SP1.
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<= 8.0= 7.1<= 7.1= 5.0= 6.0= 7.0CVSS 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
- Adjacent
- Complexity
- Low
- Authentication
- None
- Confidentiality
- None
- Integrity
- None
- Availability
- Complete
AV:A/AC:L/Au:N/C:N/I:N/A:C
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.
-
Identify if Siemens WinCC is installedCheck for WinCC installation directories (typically C:\Program Files\Siemens\WinCC) or look for WinCC entries in Windows Add/Remove ProgramsAffected if WinCC is installed and the version is 5.0, 6.0, 7.0, or any version up to and including 7.1
-
Identify if SIMATIC PCS7 is installedCheck for PCS7 installation directories or look for SIMATIC PCS7 entries in Windows Add/Remove ProgramsAffected if SIMATIC PCS7 is installed and the version is 7.1 or any version up to and including 8.0
-
Determine the exact version of WinCCLocate the WinCC version information in the installation directory, registry (HKLM\SOFTWARE\Siemens\WinCC\Version), or via the 'ccinstallinfo' utility if availableAffected if The installed version is before 7.2 (versions 5.0, 6.0, 7.0, 7.1 are affected)
-
Determine the exact version of SIMATIC PCS7Locate the PCS7 version information in the installation directory or registry (HKLM\SOFTWARE\Siemens\PCS7\Version)Affected if The installed version is before 8.0 SP1 (versions 7.1 through 8.0 are affected)
-
Verify if CCEServer component is present and enabledCheck for the CCEServer service or executable within the WinCC/PCS7 installation directory (typically named CCEServer.exe or similar), and check if the service is registered and running via Windows Services consoleAffected if The CCEServer component exists and is running (this is the vulnerable component that must be exposed for exploitation)
Your environment is affected if WinCC versions 5.0, 6.0, 7.0, or 7.1 are installed, or if SIMATIC PCS7 versions 7.1 through 8.0 are installed, and the CCEServer component is present and enabled.
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 Siemens WinCC to version 7.2 or later, and SIMATIC PCS7 to version 8.0 SP1 or later. If immediate patching is not possible, consider network segmentation to limit exposure of the CCEServer component.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-0675 — 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-2013-0675 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