CVE-2013-0689
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 TFTP server 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 upload files and consequently execute arbitrary code via unspecified vectors.
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 confidenceUnauthenticated TFTP server on Emerson ROC800, DL8000, and ROC800L RTU devices allows remote attackers to upload arbitrary files, leading to remote code execution. This is a critical vulnerability in industrial control equipment where TFTP (a protocol without built-in authentication) can be exploited to write malicious files to the device filesystem.
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 device model and firmware versionAccess the device management interface or console and retrieve the device model name and current firmware version. For Emerson devices, this is typically available via the device web interface, serial console, or SNMP. For Enea Ose, check the system information or use 'uname -a' or equivalent system commands.Affected if The device is an Emerson ROC800, ROC800L, or DL8000 (all versions are affected), or Enea Ose version 1.20 or lower, 2.30 or lower, or 3.50 or lower.
-
Verify TFTP service statusCheck whether the TFTP service is running or enabled on the device. On Emerson RTU devices, this is typically configurable through the device configuration software (such as ROC Explorer) or via the device web interface under services or network settings. Look for TFTP server settings.Affected if The TFTP server service is enabled or running on the device.
-
Confirm TFTP port is listeningPerform a UDP port scan against the device targeting port 69 (the standard TFTP port). Use a command such as 'nmap -sU -p 69 <device_ip>' or verify with 'netstat' or similar tool directly on the device if accessible.Affected if UDP port 69 is open and responding on the device.
-
Assess network exposure of TFTP serviceReview network segmentation and firewall rules to determine whether the device with TFTP enabled is accessible from untrusted networks, DMZs, or the internet. Check ACLs, router rules, and perimeter firewall configurations.Affected if The device with TFTP enabled is reachable from any network segment that contains untrusted or external systems.
You are affected if your device is an Emerson ROC800, ROC800L, or DL8000 (any firmware version) or Enea Ose <= 1.20/2.30/3.50, AND the TFTP service is enabled and accessible from a network segment you do not fully control.
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 · scopedApply vendor firmware updates (ROC800 v3.60+, DL8000 v2.40+, ROC800L v1.30+). If updates are not feasible, disable the TFTP service and restrict network access to these devices via firewall rules or network segmentation.
ROC800: software version 3.51+; DL8000: software version 2.31+; ROC800L: software version 1.21+ (obtain latest from Emerson)
- Contact Emerson Process Management to obtain the latest firmware/software versions for your ROC800, DL8000, or ROC800L RTU devices
- Request version 3.51 or higher for ROC800, version 2.31 or higher for DL8000, and version 1.21 or higher for ROC800L
- Apply the firmware update following Emerson's official update procedures
- After upgrade, verify that the TFTP server functionality is working correctly
- If the TFTP service is not required in your operational environment, consider disabling it to reduce attack surface
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-0689 — 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-0689 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