dbcve.org
Controlwave Pac FirmwareOperating system · Emerson

CVE-2022-30262

HIGH · 7.8 CVSS v3.1 Published 2022-08-17
Fix available
A fix is available. Upgrade to after 2022-05-02 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

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 · unedited
The Emerson ControlWave 'Next Generation' RTUs through 2022-05-02 mishandle firmware integrity. They utilize the BSAP-IP protocol to transmit firmware updates. Firmware updates are supplied as CAB archive files containing a binary firmware image. In all cases, firmware images were found to have no authentication (in the form of firmware signing) and only relied on insecure checksums for regular integrity checks.

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 confidence

The Emerson ControlWave 'Next Generation' RTUs use the BSAP-IP protocol to receive firmware updates delivered as CAB archive files containing binary firmware images. The firmware images lack cryptographic signing and rely solely on insecure checksums for integrity verification, allowing attackers to potentially inject malicious firmware via man-in-the-middle attacks or compromised update distribution channels.

MitigationImplement cryptographic firmware signing using industry-standard methods (e.g., RSA-2048 or ECDSA) and verify signatures in the RTU bootloader before applying any firmware update, replacing the current checksum-based integrity check.

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
Controlwave Pac FirmwareOperating system
Affected:<= 2022-05-02
Controlwave Micro FirmwareOperating system
Affected:<= 2022-05-02

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify ControlWave PAC or Micro RTUs on the network
    Inventory network devices and identify Emerson ControlWave PAC and ControlWave Micro RTUs. These are typically found on industrial networks using BSAP-IP protocol on port 102/tcp. Check device listings, network scans, or DCS/PLC configurations for these specific device types.
    Affected if ControlWave PAC or Micro RTUs are present in the environment
  2. Check installed firmware version
    Access the RTU via its management interface (web UI, console, or Emerson configuration software) and retrieve the firmware version and build date. Compare the version date against the <= 2022-05-02 threshold.
    Affected if Firmware version date is on or before 2022-05-02
  3. Verify BSAP-IP protocol configuration for firmware updates
    Check the RTU configuration for BSAP-IP protocol settings. In the ControlWave Manager or similar Emerson configuration tool, examine the protocol configuration to confirm BSAP-IP is enabled for remote firmware delivery.
    Affected if BSAP-IP protocol is enabled and configured for firmware updates
  4. Confirm integrity verification method
    Inspect the firmware update process and CAB archive handling. Check if the RTU bootloader or update mechanism validates firmware using only checksums (e.g., CRC, MD5) rather than cryptographic signatures. This may be visible in update logs, bootloader configuration, or firmware metadata within the CAB file.
    Affected if Firmware updates rely solely on checksum-based integrity verification without cryptographic signing

The environment is affected if ControlWave PAC or Micro RTUs with firmware dated 2022-05-02 or earlier are configured to receive firmware updates via BSAP-IP protocol using only checksum verification.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 2022-05-02
Interim mitigation

Implement cryptographic firmware signing using industry-standard methods (e.g., RSA-2048 or ECDSA) and verify signatures in the RTU bootloader before applying any firmware update, replacing the current checksum-based integrity check.

Fix this in Controlwave Pac Firmware Scoped from the published advisory
  • Consultation12.0 h
  • Implementation40.0 h
  • Testing20.0 h
  • Review / QA12.0 h
84.0 hours of engineering $14,760
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $23,616.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-30262 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-30262 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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