Skip to content
Fencer Intel
high 8.8

CVE-2019-7232 in the critical feed json

The ABB IDAL HTTP server is vulnerable to a buffer overflow when a long Host header is sent in a web request.

published 2019-06-24 7 y ago modified 2026-06-17 4 mo ago also EUVD-2019-16776

cvss
8.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
52.1%
EPSS 52.1% chance of exploitation in 30 days, percentile 98%
public exploits
0
none known

Summary

The ABB IDAL HTTP server is vulnerable to a buffer overflow when a long Host header is sent in a web request. The Host header value overflows a buffer and overwrites a Structured Exception Handler (SEH) address. An unauthenticated attacker can submit a Host header value of 2047 bytes or more to overflow the buffer and overwrite the SEH address, which can then be leveraged to execute attacker-controlled code on the server.

Patch / fix

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

cisa ICSA-19-178-01 updated cvss 8.8

ABB PB610 Panel Builder 600

  • ABB PB610 Panel Builder 600 order code 1SAP500900R0101, 1.91 <= 2.8.0.367
    affected: mitigation “PB610 Panel Builder 600: v2.8.0.424.” library.e.abb.com

From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf

Exploit prediction

52.09% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • seclists.org http://seclists.org/fulldisclosure/2019/Jun/40 referenced PoC, tagged "exploit" by a source, unverified
  • packetstormsecurity.com http://packetstormsecurity.com/files/153403/ABB-IDAL-HTTP-Server-Stack-Based-Buffer-Overflow.html referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 8.8 CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 5.8 AV:A/AC:L/Au:N/C:P/I:P/A:P

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.