dbcve.org
Ac500 Cpu FirmwareOperating system · Abb

CVE-2022-3192

MEDIUM · 5.3 CVSS v3.1 Published 2023-03-31
Fix available
A fix is available. Upgrade to 2.8.6 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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
Improper Input Validation vulnerability in ABB AC500 V2 PM5xx allows Client-Server Protocol Manipulation.This issue affects AC500 V2: from 2.0.0 before 2.8.6.

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

Improper input validation vulnerability in ABB AC500 V2 PM5xx PLC firmware allows client-server protocol manipulation. This affects firmware versions 2.0.0 through 2.8.5, enabling attackers to potentially manipulate the protocol communication between client and the PLC.

MitigationUpgrade the AC500 V2 PM5xx firmware to version 2.8.6 or later to remediate the improper input validation vulnerability.

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
Ac500 Cpu FirmwareOperating system
Affected:>= 2.0.0, < 2.8.6

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 checks

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

  1. Identify AC500 V2 PM5xx PLC firmware version
    Access the PLC through ABB Automation Builder engineering software or check the PLC web interface (if enabled). Navigate to the CPU firmware information section to retrieve the installed firmware version number.
    Affected if The installed firmware version falls within the range 2.0.0 to 2.8.5 inclusive.
  2. Confirm client-server protocol is in use
    Review the PLC project configuration in Automation Builder to identify if client-server protocol communication (such as Modbus TCP or ABB proprietary protocols) is configured and enabled for communication with external clients.
    Affected if Client-server protocol communication is enabled and the firmware version is 2.0.0 to 2.8.5.
  3. Verify external network exposure
    Examine the PLC network configuration to determine if the protocol communication interfaces are exposed to external networks or accessible from untrusted segments.
    Affected if The PLC management interface or protocol ports are accessible from untrusted networks and the firmware version is vulnerable.
  4. Check for unusual protocol traffic patterns
    Monitor network traffic on protocol ports (typically port 102 or 502 for Modbus) for signs of malformed packets or unexpected protocol manipulation attempts.
    Affected if Abnormal or malformed protocol packets are detected and the firmware version is within the affected range.

A user is affected if the AC500 V2 PM5xx PLC runs firmware version 2.0.0 through 2.8.5 and has client-server protocol communication enabled.

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.

dbcve · scoped
Upgrade available Upgrade to 2.8.6 or later
Fixed in 2.8.6
Interim mitigation

Upgrade the AC500 V2 PM5xx firmware to version 2.8.6 or later to remediate the improper input validation vulnerability.

Recommended fix Moderate confidence

AC500 V2 PM5xx firmware version 2.8.6

  1. 1. Identify all ABB AC500 V2 PM5xx PLC devices in the environment running firmware versions 2.0.0 through 2.8.5.
  2. 2. Backup current PLC configurations and programs before performing any firmware update.
  3. 3. Obtain the AC500 V2 firmware version 2.8.6 or later from ABB's official support portal at search.abb.com.
  4. 4. Follow ABB's standard firmware update procedure for AC500 V2 PM5xx CPUs, typically via PLC's web server or Automation Builder software.
  5. 5. After upgrade, verify the firmware version displays 2.8.6 or higher.
  6. 6. Test critical PLC programs and communications to ensure normal operation.
  7. 7. Update change management documentation to reflect the firmware upgrade.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ac500 Cpu Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation4.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,840
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-3192 — 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-3192 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