CVE-2013-0692
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 kernel in ENEA OSE on the Emerson Process Management ROC800 RTU with software 3.50 and earlier, DL8000 RTU with software 2.30 and earlier, and ROC800L RTU with software 1.20 and earlier allows remote attackers to execute arbitrary code by connecting to the debug service.
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 ENEA OSE kernel on Emerson Process Management ROC800, DL8000, and ROC800L RTU devices contains a vulnerability in the debug service that allows remote attackers to execute arbitrary code by connecting to this exposed service. This is a critical RCE vulnerability affecting specific software versions of the affected RTUs.
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.20<= 3.50<= 2.30all versionsall versionsall versionsCVSS 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
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/Au:N/C:C/I:C/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 the RTU device modelCheck the device nameplate, firmware banner, or management interface for the exact model number (ROC800, ROC800L, or DL8000)Affected if The device is an Emerson ROC800, ROC800L, or DL8000 Remote Terminal Unit
-
Check if the debug service is listeningUse a network scanner or netstat command to identify open ports on the device, particularly the debug service port (commonly TCP port 20100 but may vary)Affected if The debug service port is open and responding to connections
-
Attempt unauthenticated debug connectionUse a tool like telnet or netcat to attempt a connection to the debug service port without credentialsAffected if A connection is successfully established to the debug service without authentication
-
Verify ENA OSE kernel version if accessibleIf system access is available, check the kernel version through the device's OS information or boot messagesAffected if The ENA OSE kernel version is 1.20 or lower, 2.30 or lower, or 3.50 or lower
-
Confirm network exposure of debug serviceReview firewall rules, ACLs, or network segmentation to determine if the debug service port is accessible from untrusted networksAffected if The debug service is accessible from network segments outside the trusted control system network
A user is affected if their Emerson ROC800, ROC800L, or DL8000 device has an accessible debug service, regardless of ENA OSE version (all versions are affected).
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 dataDisable or restrict access to the debug service on affected RTU devices, implement network segmentation to limit exposure, and upgrade to patched software versions if available from Emerson Process Management.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-0692 — 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-0692 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