CVE-2022-29957
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 Emerson DeltaV Distributed Control System (DCS) through 2022-04-29 mishandles authentication. It utilizes several proprietary protocols for a wide variety of functionality. These protocols include Firmware upgrade (18508/TCP, 18518/TCP); Plug-and-Play (18510/UDP); Hawk services (18507/UDP); Management (18519/TCP); Cold restart (18512/UDP); SIS communications (12345/TCP); and Wireless Gateway Protocol (18515/UDP). None of these protocols have any authentication features, allowing any attacker capable of communicating with the ports in question to invoke (a subset of) desired functionality.
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 Emerson DeltaV DCS uses multiple proprietary protocols (18508/TCP, 18518/TCP, 18510/UDP, 18507/UDP, 18519/TCP, 18512/UDP, 12345/TCP, 18515/UDP) for critical functions including firmware upgrades, plug-and-play, management, and SIS communications. None of these protocols implement any authentication, allowing any network-adjacent attacker to invoke arbitrary functionality on the DCS.
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<= 2022-04-29CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 DCS installationReview system inventory, installed software list, or look for DeltaV-related processes/services on the target systemAffected if The system runs Emerson DeltaV DCS software
-
Scan for open affected portsPerform a port scan (e.g., nmap -p 18508,18518,18510,18507,18519,18512,12345,18515 -sT/-sU) against the DeltaV controller or engineering workstationAffected if Any of the ports 18508/TCP, 18518/TCP, 18510/UDP, 18507/UDP, 18519/TCP, 18512/UDP, 12345/TCP, or 18515/UDP are open and accessible on the network
-
Check DeltaV versionQuery the DeltaV system information, check the About section in DeltaV Explorer, review installation logs, or check the version metadata of DeltaV executablesAffected if The installed DeltaV version was released on or before April 29, 2022 (verify against Emerson release dates)
-
Verify protocol accessibilityConfirm network accessibility to the DeltaV system from untrusted network segments by reviewing firewall rules and network segmentationAffected if The DeltaV protocols on the affected ports are reachable from network segments that contain untrusted or non-ICS devices
A user is affected if their DeltaV DCS system has any of the specified ports accessible from the network and runs a version released on or before April 29, 2022.
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 dataImplement network segmentation to isolate the DCS from untrusted networks, and engage Emerson for vendor-supplied authentication mechanisms or protocol upgrades to secure these interfaces.
- Consultation8.0 h
- Implementation24.0 h
- Testing24.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 $17,536.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-29957 — 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-2022-29957 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