CVE-2021-23280
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 · uneditedEaton Intelligent Power Manager (IPM) prior to 1.69 is vulnerable to authenticated arbitrary file upload vulnerability. IPM’s maps_srv.js allows an attacker to upload a malicious NodeJS file using uploadBackgroud action. An attacker can upload a malicious code or execute any command using a specially crafted packet to exploit the vulnerability.
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 confidenceEaton Intelligent Power Manager (IPM) prior to version 1.69 contains an authenticated arbitrary file upload vulnerability in the maps_srv.js component. The uploadBackgroud action allows authenticated attackers to upload malicious NodeJS files, enabling remote command execution via specially crafted requests.
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< 1.69< 1.69< 1.68CVSS 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
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Check installed IPM versionLocate the Eaton Intelligent Power Manager installation and identify the version number. On Windows, check Add/Remove Programs or the installation directory for version info. On the Virtual Appliance, use 'rpm -q ipm' or check the web interface login page for version display.Affected if The installed version is less than 1.69 for IPM or less than 1.68 for IP Protector.
-
Verify maps_srv.js component existsSearch the web server document root or application installation directory for the file maps_srv.js. Common paths may include /opt/ipm/, /usr/local/ipm/, or the web server's document root. Use 'find' or file explorer to locate this file.Affected if The maps_srv.js file exists, indicating the vulnerable component is present.
-
Confirm web management interface is accessibleAttempt to access the IPM web management interface via browser or curl at the default HTTPS port (typically 4679 or 4680). The vulnerability requires authentication but the endpoint must be reachable.Affected if The web interface is accessible over the network, making the upload endpoint reachable.
-
Check for suspicious uploaded filesExamine web application directories, particularly upload or static content folders, for unexpected .js or .node files. Check /tmp, application data directories, or web root for unfamiliar files with recent modification dates.Affected if Unexpected JavaScript or executable files are found in the application directories that were not intentionally deployed.
A user is affected if their installed version is below 1.69 for IPM or below 1.68 for IP Protector, the maps_srv.js component exists, and the management interface is network-accessible.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.681.69
Upgrade to IPM version 1.69 or later to remediate this vulnerability. Until patched, restrict network access to the IPM management interface to trusted users only and monitor for suspicious upload activity.
Intelligent Power Manager to version 1.69 | Intelligent Power Manager Virtual Appliance to version 1.69 | Intelligent Power Protector to version 1.68
- 1. Back up current Intelligent Power Manager/Protector configuration and data according to Eaton backup procedures
- 2. Download the fixed version (Intelligent Power Manager 1.69 or Intelligent Power Protector 1.68) from official Eaton sources (www.eaton.com)
- 3. Apply the upgrade following the official Eaton upgrade documentation for your specific product
- 4. After upgrade, verify the maps_srv.js component has been updated and the uploadBackgroud action is properly restricted
- 5. Confirm the application functions normally post-upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-23280 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-23280 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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