CVE-2013-0666
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 · uneditedThe configuration utility in MatrikonOPC Security Gateway 1.0 allows remote attackers to cause a denial of service (unhandled exception and application crash) via a TCP RST 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 · moderate confidenceThe configuration utility in MatrikonOPC Security Gateway 1.0 contains a denial of service vulnerability where it fails to properly handle incoming TCP RST packets. When a remote attacker sends a TCP RST packet to the service, it triggers an unhandled exception that causes the application to crash.
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= 1.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
- 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.
-
Identify if MatrikonOPC Security Gateway is installedCheck the Windows registry under HKEY_LOCAL_MACHINE\SOFTWARE\MatrikonOPC\ or look for 'MatrikonOPC Security Gateway' in Add/Remove Programs. Also check for installation directories typically under C:\Program Files\MatrikonOPC\ or C:\Program Files (x86)\MatrikonOPC\Affected if The software is found on the system
-
Verify the installed version numberRight-click the MatrikonOPC Security Gateway executable (often named 'MatrikonOPC.SecGateway.exe' or similar), select Properties, and check the File Version in the Details tab. Alternatively, check the registry key for the version string.Affected if The version is exactly 1.0
-
Confirm the service is runningOpen Windows Services (services.msc), locate the MatrikonOPC Security Gateway service, and check its Status column. It may be named 'MatrikonOPC Security Gateway' or 'Matrikon Gateway'Affected if The service status shows as Running
-
Check network exposureUse netstat -an | findstr LISTENING to identify listening ports. Cross-reference with known MatrikonOPC ports (often 10200, 10201, or configurable). Verify if the service listens on interfaces accessible from untrusted networks by checking the bound IP address.Affected if The service listens on 0.0.0.0 or an externally accessible IP rather than only 127.0.0.1 or internal LAN addresses
If MatrikonOPC Security Gateway version 1.0 is installed with its service running and exposed to the network, the system is affected by this CVE.
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 dataApply vendor patch if available. In the interim, consider network segmentation or firewall rules to limit exposure to untrusted networks, as the attack vector is network-based TCP packets.
- Consultation3.0 h
- Implementation8.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-0666 — 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-0666 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