CVE-2012-1816
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 · uneditedPORTSERV.exe in Emerson DeltaV and DeltaV Workstations 9.3.1, 10.3.1, 11.3, and 11.3.1 and DeltaV ProEssentials Scientific Graph 5.0.0.6 allows remote attackers to cause a denial of service (daemon crash) via a crafted (1) TCP or (2) UDP packet to port 111.
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 confidencePORTSERV.exe daemon in Emerson DeltaV versions 9.3.1, 10.3.1, 11.3, and 11.3.1 crashes when receiving malformed TCP or UDP packets on port 111, allowing remote attackers to cause denial of service.
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= 9.3.1= 10.3.1= 11.3= 11.3.1= 5.0.0.6= 9.3.1= 10.3.1= 11.3= 11.3.1CVSS 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
- None
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/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 if Emerson DeltaV is installedCheck Windows installed programs or look for DeltaV installation directory (typically under C:\DeltaV or similar)Affected if Emerson DeltaV version 9.3.1, 10.3.1, 11.3, or 11.3.1 is found, or Processessentials Scientific Graph version 5.0.0.6, or DeltaV Workstation matching those versions
-
Check PORTSERV.exe processOpen Task Manager or use command: tasklist | findstr PORTSERV.exeAffected if PORTSERV.exe process is running on the system
-
Verify port 111 is listeningRun command: netstat -an | findstr :111 or use PortQry.exe to query port 111 statusAffected if Port 111 is open and accepting TCP or UDP connections
-
Confirm DeltaV versionCheck installed version via Windows Programs and Features, DeltaV About dialog, or check version info of PORTSERV.exe fileAffected if Installed version exactly matches 9.3.1, 10.3.1, 11.3, or 11.3.1 for DeltaV/Workstation, or 5.0.0.6 for Processessentials Scientific Graph
System is affected if Emerson DeltaV (or Workstation) version 9.3.1, 10.3.1, 11.3, or 11.3.1 is installed, PORTSERV.exe is running, and port 111 is exposed on 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 dataApply vendor patches for affected DeltaV versions or restrict network access to port 111 using firewall rules to block untrusted sources.
- Consultation8.0 h
- Implementation4.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 $6,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-1816 — 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-2012-1816 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