Skip to content
Fencer Intel
high 8.0

CVE-2021-23279 in the critical feed json

Arbitrary File delete

published 5y ago modified 4mo ago also EUVD-2021-10374

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

Summary

Eaton Intelligent Power Manager (IPM) prior to 1.69 is vulnerable to unauthenticated arbitrary file delete vulnerability induced due to improper input validation in meta_driver_srv.js class with saveDriverData action using invalidated driverID. An attacker can send specially crafted packets to delete the files on the system where IPM software is installed.

Patch / fix

  • Eaton Intelligent Power manager (IPM) 1.69

Is CVE-2021-23279 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

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

cisa ICSA-21-110-06 updated cvss 8.0

Eaton Intelligent Power Manager

  • Eaton Intelligent Power Manager (IPM) < 1.69 Eaton Intelligent Power Manager Virtual Appliance (IPM VA) < 1.69 Eaton Intelligent Power Protector (IPP) < 1.68
    affected: mitigation “Eaton IPM v1.69: Download | IPM | Eaton” eaton.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

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

CVSS scores

assigned by version score vector
CNA 3.1 8.0 CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:H
NVD 3.1 10.0 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:H
NVD 2.0 6.4 AV:N/AC:L/Au:N/C:N/I:P/A:P

Affected products

  • Eaton Intelligent Power manager (IPM)

Classification

Weakness
  • CWE-20 Improper Input Validation

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.