CVE-2014-2350
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 · uneditedEmerson DeltaV 10.3.1, 11.3, 11.3.1, and 12.3 uses hardcoded credentials for diagnostic services, which allows remote attackers to bypass intended access restrictions via a TCP session, as demonstrated by a session that uses the telnet program.
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 confidenceEmerson DeltaV distributed control system versions 10.3.1, 11.3, 11.3.1, and 12.3 contain hardcoded credentials embedded in the software for diagnostic services. Remote attackers can exploit this by initiating a TCP session (e.g., via telnet) and using these credentials to bypass authentication and gain unauthorized access to the system.
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= 10.3.1= 11.3= 11.3.1= 12.3CVSS 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
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/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 DeltaV version installedCheck the Emerson DeltaV application or system information panel, typically accessible through the DeltaV Explorer or system administration console, to confirm the exact version numberAffected if The installed version matches 10.3.1, 11.3, 11.3.1, or 12.3 exactly
-
Locate diagnostic service configurationInspect the DeltaV configuration files or service settings for diagnostic or maintenance service entries, commonly found in the DeltaV system directory or control system configuration panelAffected if Diagnostic services such as telnet, remote administration, or maintenance ports are enabled or present in the configuration
-
Review enabled system accountsAccess the DeltaV user account management interface or examine user account configuration files to enumerate all enabled accounts, noting any accounts labeled as diagnostic, service, maintenance, or default system accountsAffected if Unknown, default, or undocumented accounts exist beyond normal operator/administrator accounts, particularly those associated with diagnostic or maintenance functions
-
Verify network exposure of diagnostic portsScan the network or review firewall rules to determine if TCP ports used by diagnostic services (commonly port 23 for telnet or other remote access ports) are accessible from network segments outside the trusted control system networkAffected if Diagnostic service ports are open and reachable from untrusted network segments or the enterprise network
-
Test for authentication bypassAttempt to initiate a TCP connection to the DeltaV system on known diagnostic ports using the suspected hardcoded credentials, observing whether authentication is successful without valid user credentialsAffected if Connection succeeds using the hardcoded diagnostic credentials, confirming the vulnerability is exploitable
The system is affected if it runs DeltaV version 10.3.1, 11.3, 11.3.1, or 12.3 and has exposed diagnostic services with hardcoded credentials accessible from the network.
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 dataRemove or disable accounts associated with hardcoded credentials, change all default passwords to strong unique values, and implement network segmentation to restrict access to diagnostic services from untrusted networks.
- Consultation8.0 h
- Implementation12.0 h
- Testing6.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 $8,608.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-2350 — 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-2014-2350 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