CVE-2020-6652
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 · uneditedIncorrect Privilege Assignment vulnerability in Eaton's Intelligent Power Manager (IPM) v1.67 & prior allow non-admin users to upload the system configuration files by sending specially crafted requests. This can result in non-admin users manipulating the system configurations via uploading the configurations with incorrect parameters.
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) versions 1.67 and prior contains an incorrect privilege assignment vulnerability where non-admin users can upload system configuration files by sending specially crafted requests. This allows unauthorized users to manipulate system configurations by uploading configuration files with incorrect or malicious parameters, bypassing the intended admin-only restriction on configuration management.
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.67CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/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.
-
Verify Eaton IPM installationCheck for Eaton Intelligent Power Manager installation by looking for the application in system directories, running services, or the web interface (typically on port 4679 or 4680).Affected if Eaton IPM software is installed on the system
-
Determine installed versionCheck the installed version of Eaton IPM through the application UI (Help > About), installation directory metadata, or Windows Programs and Features.Affected if Installed version is 1.67 or lower (any version up to and including 1.67)
-
Confirm web service is accessibleVerify the IPM web interface is running and reachable by accessing the server on the expected port.Affected if Web interface is accessible and the application is running
-
Identify non-admin user accountsReview user accounts configured in IPM through the user management interface or configuration files to determine if non-admin users exist.Affected if Non-admin user accounts are configured in the system
-
Check configuration upload permissionsInspect the user role permissions in IPM to determine which roles can access system configuration upload functionality.Affected if Non-admin roles have permission to upload configuration files or if no role-based access control is enforced on configuration uploads
The environment is affected if Eaton Intelligent Power Manager version 1.67 or prior is installed and non-admin users have access to the configuration upload functionality.
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.
From vendor dataImplement proper authorization checks to ensure only authenticated admin users can upload system configuration files. Validate user privileges server-side before accepting any configuration uploads.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-6652 — 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-2020-6652 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