CVE-2021-33003
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 · uneditedDelta Electronics DIAEnergie Version 1.7.5 and prior may allow an attacker to retrieve passwords in cleartext due to a weak hashing algorithm.
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 · moderate confidenceDelta Electronics DIAEnergie Version 1.7.5 and prior stores user passwords using a weak hashing algorithm that allows attackers to retrieve credentials in cleartext, likely through database access or an authentication bypass.
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.7.5CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:L/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.
-
Identify DIAEnergie installed versionCheck the application's About page, Windows Registry under HKEY_LOCAL_MACHINE\SOFTWARE\DeltaDIAEnergie, or the version.dll/version.txt file in the installation directoryAffected if The installed version is 1.7.5 or any version number lower than 1.7.5
-
Locate the user database fileFind the SQL Server or SQLite database file used by DIAEnergie, typically in the application data folder or SQL Server instance it connects toAffected if Database access is available and contains user credential tables
-
Inspect password storage formatQuery the user table (commonly named Users, tbl_Users, or similar) and examine the password column valuesAffected if Passwords appear as short fixed-length strings (32, 40, or 64 characters) typical of MD5, SHA1, or SHA256 without proper salting, indicating weak hashing
-
Verify if password hashes are saltedCompare multiple password hash values - if they share the same hash for the same password or follow a predictable pattern, salting is not implementedAffected if Identical passwords produce identical hash values, indicating unsalted weak hashing algorithm is in use
-
Check authentication mechanism configurationExamine web.config or app.config files for authentication settings and password hash algorithm configurationAffected if Configuration shows use of MD5, SHA1, or basic SHA256 without key stretching or salt parameters
A user is affected if DIAEnergie version is 1.7.5 or lower AND password storage uses unsalted MD5/SHA1/SHA256 hashes that can be reversed or cracked.
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 dataUpgrade to a version that implements strong password hashing (e.g., bcrypt, Argon2, scrypt) and migrate existing password hashes using a secure key derivation function.
- Consultation6.0 h
- Implementation20.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,288.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-33003 — 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-33003 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