CVE-2013-0693
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 performs network-beacon broadcasts, which allows remote attackers to obtain potentially sensitive information about device presence by listening for broadcast traffic.
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 confidenceThe ENEA OSE kernel on Emerson ROC800, DL8000, and ROC800L RTU devices performs network-beacon broadcasts that expose device presence information to any attacker listening on the same network segment. This allows remote unauthenticated attackers to discover vulnerable devices by passively monitoring broadcast traffic.
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<= 2.30<= 3.50all 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 modelInventory the physical or managed devices on your network to determine if any are Emerson ROC800, ROC800L, or DL8000 Remote Terminal UnitsAffected if The device is one of these three models (all versions affected)
-
Check the ENEA OSE kernel versionIf accessible via console or management interface, run 'uname -a' or check system information to identify the ENEA OSE kernel versionAffected if Version is 1.20 or lower, 2.30 or lower, or 3.50 or lower
-
Determine network exposureMap the network segment where the RTU devices are deployed. Check if they are on the same segment as untrusted networks, guest networks, or internet-facing systemsAffected if The RTU devices share a network segment with untrusted systems or are directly accessible from less-trusted networks
-
Verify broadcast traffic visibilityFrom a test system on the same network segment, use a packet capture tool (such as tcpdump or Wireshark) to monitor for periodic beacon broadcasts originating from the RTU devicesAffected if Beacon broadcast packets are observable by systems on the same network segment, indicating device presence information is exposed
-
Check firewall rules for broadcast trafficReview firewall configurations on network perimeter devices to determine if broadcast or multicast traffic from the RTU network segment is permitted to cross into untrusted segmentsAffected if No firewall rules block broadcast traffic from reaching hostile network segments
You are affected if you have Emerson ROC800, ROC800L, or DL8000 RTU devices, or any system running ENEA OSE kernel version 1.20/2.30/3.50 or lower, and these devices are on network segments where an attacker could passively observe their beacon broadcasts.
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.
dbcve · scopedImplement network segmentation to isolate RTU devices from untrusted networks and deploy firewall rules to block broadcast traffic from reaching hostile network segments. Contact Emerson for patched firmware versions beyond the affected software releases.
- Implement network segmentation to isolate the affected RTUs from untrusted networks
- Place the affected devices on a dedicated VLAN or air-gapped network segment
- Configure firewalls to block broadcast traffic between network zones
- Monitor network traffic for unexpected broadcast packets
- Contact Emerson Process Management for firmware updates that address the beacon broadcast issue
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-0693 — 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-0693 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