CVE-2023-43777
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 easySoft software is used to program easy controllers and displays for configuring, programming and defining parameters for all the intelligent relays. This software has a password protection functionality to secure the project file from unauthorized access. This password was being stored insecurely and could be retrieved by skilled adversaries.
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 easySoft software stores project file passwords insecurely, allowing skilled adversaries to retrieve the password and gain unauthorized access to protected project files.
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< 8.01CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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 Eaton easySoft versionOpen the software and navigate to Help > About, or check the installed programs list in Windows Control Panel to find the exact version numberAffected if The installed version is below 8.01
-
Locate project filesSearch for project file extensions used by easySoft (typically .ezp or similar) in user directories and project foldersAffected if Password-protected project files exist on the system
-
Inspect password storage in project filesOpen a project file in a hex editor or text viewer and look for stored password strings or encoded credential data within the file structureAffected if Passwords appear as plaintext, base64-encoded, or use weak encryption rather than strong cryptographic hashing
-
Verify password protection feature usageCheck project settings or metadata within easySoft to confirm which projects have password protection enabledAffected if Password protection is enabled on any project file
You are affected if Eaton easySoft version is below 8.01 AND you have project files that use the password protection feature, as passwords are stored insecurely in those files.
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 · scoped8.01
Implement proper password storage using strong cryptographic hashing (e.g., bcrypt, Argon2, or PBKDF2 with unique salts) for project file passwords, and require users to update their passwords after the fix is deployed.
8.01
- 1. Check the currently installed Easysoft version on the system
- 2. Back up all existing project files and configurations
- 3. Download Easysoft version 8.01 or later from the official Eaton website (www.eaton.com)
- 4. Run the installer for the new version
- 5. Follow the installation wizard prompts to complete the upgrade
- 6. Open existing project files to verify they load correctly with the new version
- 7. Confirm that password protection now properly secures project files
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation6.0 h
- Testing3.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-43777 — 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-2023-43777 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