Subnet Solutions has an update available to handle improper restriction of XML external entity reference and integer overflow or wraparound vulnerabilities in its PowerSYSTEM Center, according to a report with CISA.

Successful exploitation of these remotely exploitable vulnerabilities, which Subnet Solutions self-reported, could allow an attacker to cause an integer overflow on the affected device.

The following versions of SUBNET PowerSYSTEM Center, an OT device management platform, suffer from the vulnerabilities: PowerSYSTEM Center PSC 2020: v5.22.x and prior.

In one issue, there is an issue in libexpat before 2.6.3. xmlparse.c does not reject a negative length for XML_ParseBuffer.

CVE-2024-45490 is the case number for this vulnerability, which has a CVSS v3.1 base score of 9.8.

Schneider Bold

In addition, there is an issue discovered in libexpat before 2.6.3. dtdCopy in xmlparse.c can have an integer overflow for nDefaultAtts on 32-bit platforms (where UINT_MAX equals SIZE_MAX).

CVE-2024-45491 is the case number for this vulnerability, which has a CVSS v3.1 base score of 9.8.

Also, there was an issue in libexpat before 2.6.3. nextScaffoldPart in xmlparse.c can have an integer overflow for m_groupSize on 32-bit platforms (where UINT_MAX equals SIZE_MAX).

CVE-2024-45492 is the case number for this vulnerability, which has a CVSS v3.1 base score of 9.8.

The product sees use in the critical manufacturing and energy sectors, and on a global basis.

No exploit targets these vulnerabilities. However, an attacker could leverage these vulnerabilities.

Canada-based Subnet Solutions reports dependencies ended up updated and vulnerabilities will end up fixed in PowerSYSTEM Center 2020 Update 23 release.

Subnet Solutions recommends users update to the latest version. If this is not possible, the following are identified mitigations:

  • Apply application allow-listing to prevent unauthorized executables from running.
  • Ensure Data Execution Prevention (DEP) and Address Space Layout Randomization (ASLR) are enabled within the operating system. Memory protection controls can be enabled via Windows Security. Click here for more information on the release. 
ISSSource

Pin It on Pinterest

Share This