CVE-2015-5626 Memory corruption in B/M9000 VP

Critical 9.8 Published Updated

Remote attackers can cause a denial of service in Yokogawa industrial control systems via a crafted packet exploiting a stack-based buffer overflow.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
None listed

What is CVE-2015-5626?

CVE-2015-5626 is a critical memory corruption vulnerability in Yokogawa B/M9000 VP, published on 5 Feb 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official description

Stack-based buffer overflow in Yokogawa CENTUM CS 1000 R3.08.70 and earlier, CENTUM CS 3000 R3.09.50 and earlier, CENTUM CS 3000 Entry R3.09.50 and earlier, CENTUM VP R5.04.20 and earlier, CENTUM VP Entry R5.04.20 and earlier, ProSafe-RS R3.02.10 and earlier, Exaopc R3.72.00 and earlier, Exaquantum R2.85.00 and earlier, Exaquantum/Batch R2.50.30 and earlier, Exapilot R3.96.10 and earlier, Exaplog R3.40.00 and earlier, Exasmoc R4.03.20 and earlier, Exarqe R4.03.20 and earlier, Field Wireless Device OPC Server R2.01.02 and earlier, PRM R3.12.00 and earlier, STARDOM VDS R7.30.01 and earlier, STARDOM OPC Server for Windows R3.40 and earlier, FAST/TOOLS R10.01 and earlier, B/M9000CS R5.05.01 and earlier, B/M9000 VP R7.03.04 and earlier, and FieldMate R1.01 or R1.02 allows remote attackers to cause a denial of service (network-communications outage) via a crafted packet.

Weakness: CWE-787

Which versions are affected by CVE-2015-5626?

It affects 21 products.

Products include Yokogawa B\/M9000 Vp Firmware, Yokogawa B\/M9000cs Firmware, Yokogawa Centum Cs 1000 Firmware, Yokogawa Centum Cs 3000 Entry Firmware, Yokogawa Centum Cs 3000 Firmware, Yokogawa Centum Vp Entry Firmware and 15 more.

How do I fix CVE-2015-5626?

No fix has been published for CVE-2015-5626 yet. Limit exposure of the affected software until one is available.

Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.

Is CVE-2015-5626 being exploited?

There is no known exploitation of CVE-2015-5626 in the wild and no public exploit code.

Sources

Also known as GHSA-gmf6-3628-28f2.

Is CVE-2015-5626 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free