dbcve.org
Pcu400Hardware / appliance · Abb

CVE-2008-2474

HIGH · 10.0 CVSS v2.0 Published 2008-09-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
Buffer overflow in x87 before 3.5.5 in ABB Process Communication Unit 400 (PCU400) 4.4 through 4.6 allows remote attackers to execute arbitrary code via a crafted packet using the (1) IEC60870-5-101 or (2) IEC60870-5-104 communication protocol to the X87 web interface.

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

Buffer overflow in x87 component before version 3.5.5 in ABB Process Communication Unit 400 (PCU400) versions 4.4 through 4.6 allows remote attackers to execute arbitrary code via crafted packets using IEC60870-5-101 or IEC60870-5-104 industrial communication protocols targeting the X87 web interface.

MitigationUpdate x87 component to version 3.5.5 or later; additionally implement network segmentation and restrict access to IEC60870-5 protocols to limit attack surface.

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
Pcu400Hardware / appliance
Affected:= 4.4= 4.5= 4.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
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

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 the product
    Query the system for ABB Process Communication Unit 400 (PCU400) identification strings or check device inventory/monitoring systems for PCU400 hardware or software entries
    Affected if The device is not an ABB PCU400 system (not applicable)
  2. Check PCU400 firmware version
    Access the PCU400 management interface or check system information to retrieve the installed version number
    Affected if Version is 4.4, 4.5, or 4.6 (vulnerable if x87 component is also below 3.5.5)
  3. Check x87 component version
    Inspect the x87 component version information through the PCU400 administrative interface, configuration files, or system diagnostics related to the X87 web interface
    Affected if x87 component version is below 3.5.5 (combined with PCU400 versions 4.4-4.6)
  4. Verify IEC60870-5 protocol configuration
    Examine PCU400 network configuration settings to determine if IEC60870-5-101 or IEC60870-5-104 industrial protocols are enabled and listening
    Affected if Either IEC60870-5-101 or IEC60870-5-104 protocol is actively configured (prerequisite for remote exploitation)
  5. Check X87 web interface accessibility
    Probe network connectivity to the X87 web interface port or verify in the PCU400 configuration that the web interface is exposed
    Affected if X87 web interface is network-accessible from potentially untrusted networks

The environment is affected if running PCU400 versions 4.4-4.6 with x87 component below 3.5.5 and IEC60870-5 protocols are enabled with accessible X87 web interface.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update x87 component to version 3.5.5 or later; additionally implement network segmentation and restrict access to IEC60870-5 protocols to limit attack surface.

Recommended fix Moderate confidence

x87 version 3.5.5 or later

  1. Identify the current x87 component version installed on the ABB PCU400 system
  2. Obtain the x87 version 3.5.5 or later from ABB's official support channels
  3. Apply the x87 upgrade following ABB's documented upgrade procedure for the PCU400 system
  4. Verify the x87 component has been upgraded to version 3.5.5 or later
  5. Test IEC60870-5-101 and IEC60870-5-104 protocol communication to confirm normal operation

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

Fix this in Pcu400 Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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