CVE-2016-9345
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 · uneditedAn issue was discovered in Emerson DeltaV Easy Security Management DeltaV V12.3, DeltaV V12.3.1, and DeltaV V13.3. Critical vulnerabilities may allow a local attacker to elevate privileges within the DeltaV control system.
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 confidenceEmerson DeltaV Easy Security Management contains critical privilege escalation vulnerabilities in versions V12.3, V12.3.1, and V13.3. A local attacker could exploit these flaws to elevate their privileges within the DeltaV control system, potentially gaining administrative or higher-level access to industrial process controls.
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= 12.3= 12.3.1= 13.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
- Adjacent
- Complexity
- High
- Privileges
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- Low
- Availability
- Low
CVSS:3.0/AV:A/AC:H/PR:H/UI:N/S:C/C:H/I:L/A:L
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 installation and versionLocate the Emerson DeltaV installation directory or check the system's installed programs list for DeltaV version information. Look for version metadata in the DeltaV application folders or Windows registry entries related to DeltaV.Affected if The installed DeltaV version matches 12.3, 12.3.1, or 13.3 exactly.
-
Confirm Easy Security Management componentCheck for the presence of the Easy Security Management module within the DeltaV installation. This may appear as a separate component, service, or administrative tool within the DeltaV environment.Affected if The Easy Security Management component is installed and present on the system.
-
Review local user accounts and privilegesExamine user accounts configured within the DeltaV Easy Security Management system. Check for standard user accounts that could potentially be elevated to administrative or higher-level access roles.Affected if Multiple local user accounts exist with varying privilege levels, particularly any accounts that could be exploited for privilege escalation.
-
Verify physical and logical access controlsAssess whether the DeltaV system has adequate access controls. Determine if the system is accessible to untrusted personnel or network segments that could allow local attacker access.Affected if The system lacks proper access restrictions, allowing unauthorized local access to the DeltaV workstation or server.
You are affected if DeltaV version 12.3, 12.3.1, or 13.3 is installed with the Easy Security Management component and the system has insufficient access controls preventing local attackers from reaching the vulnerable privilege escalation vector.
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-supplied patches or updates to DeltaV V12.3.1 and V13.3 as they become available. Until patches are applied, restrict physical and logical access to the DeltaV system to trusted personnel only and monitor for unauthorized access attempts.
- 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-2016-9345 — 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-2016-9345 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