CVE-2022-29962
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) controllers and IO cards through 2022-04-29 misuse passwords. FTP has hardcoded credentials (but may often be disabled in production). This affects S-series, P-series, and CIOC/EIOC nodes. NOTE: this is different from CVE-2014-2350.
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 DCS controllers and IO cards (S-series, P-series, CIOC/EIOC nodes) contain hardcoded credentials in the FTP service. These credentials are embedded in the firmware and cannot be changed by administrators. While FTP may often be disabled in production environments, if enabled, it allows authenticated access using these static credentials.
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-29<= 2022-04-29<= 2022-04-29<= 2022-04-29<= 2022-04-29<= 2022-04-29<= 2022-04-29<= 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
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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.
-
Inventory DeltaV controllers and IO cardsIdentify all Emerson DeltaV controllers (Sq, Sx series) and IO cards (Se4xxx series) deployed in the network. Consult asset inventory or use network discovery to locate these devices.Affected if Any DeltaV controller or IO card is present in the environment.
-
Confirm device model matches affected product listVerify the exact model number of each DeltaV device against the affected products: Sq Controller, Sx Controller, Se4002s1t2b6, Se4003s2b4, Se4003s2b524, Se4017p0, Se4017p1, Se4019p0.Affected if Device model is one of the eight listed affected product models.
-
Check if FTP service is enabledAccess the DeltaV device management interface or controller configuration and verify whether the FTP service is enabled. This is typically found in network services or protocol configuration settings.Affected if FTP service is enabled on the device - this is the key condition for exploitation. If FTP is disabled, the hardcoded credentials cannot be leveraged regardless of firmware version.
-
Determine firmware versionRetrieve the firmware version from the DeltaV controller or IO card. This is usually available through the device's web interface, console, or management software under system information or firmware details.Affected if Firmware version is dated on or before 2022-04-29. Compare your installed firmware date against this cutoff.
-
Verify network accessibility of FTP portPerform a port scan or check firewall rules to determine if TCP port 21 (FTP) is accessible from any network segment that could contain attackers. Check both external and internal network perspectives.Affected if FTP port 21 is exposed and reachable from untrusted network segments.
A user is affected if they have a DeltaV controller or IO card from the affected product list, with FTP service enabled, running firmware dated 2022-04-29 or earlier, and where the FTP port is network-accessible.
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 · scopedDisable the FTP service on DeltaV controllers and IO cards if not required for operations. If FTP is necessary, implement strict network segmentation to limit exposure and apply compensating controls such as IP whitelisting and monitoring for unauthorized access attempts.
Emerson DeltaV firmware released after 2022-04-29 (specific version numbers not provided in available sources)
- 1. Identify all affected DeltaV controllers and I/O cards in the manufacturing plant network
- 2. Check current firmware versions of each affected device
- 3. Obtain updated firmware from Emerson that was released after 2022-04-29
- 4. Schedule a maintenance window to apply firmware updates
- 5. Before updating, verify that FTP is disabled as a compensating control if immediate patching is not feasible
- 6. After firmware update, verify the hardcoded FTP credentials have been removed
- 7. Conduct security testing to confirm the vulnerability is resolved
Generated from the published advisory — verify against the referenced sources before acting.
- 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-2022-29962 — 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-29962 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