CVE-2023-34433
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 · uneditedPiiGAB M-Bus stores passwords using a weak hash 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 confidenceThe PiiGAB M-Bus product stores user passwords using a cryptographically weak hashing algorithm, making them vulnerable to efficient offline cracking attacks. An attacker who obtains the password database could potentially recover plaintext passwords and gain unauthorized access to the system.
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 dataall versionsCVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Confirm the device is a Piigab M-Bus 900sIdentify the hardware model or firmware running on the system. Check device documentation, web interface, or system information to verify the exact product name and model number.Affected if The device is a Piigab M Bus 900s with firmware installed.
-
Check the firmware versionAccess the device management interface or system files to retrieve the installed firmware version. Compare it against the affected range (all versions of Piigab M Bus 900s Firmware).Affected if Any firmware version is installed on a Piigab M Bus 900s device.
-
Locate the password storage mechanismExamine the system for password-related configuration files, databases, or user storage. Look for files that contain user credentials, password hashes, or authentication data.Affected if A password database or configuration file exists on the system.
-
Analyze the hash algorithm usedInspect the stored password hashes to determine the algorithm. Weak algorithms include unsalted MD5, SHA1, or similar fast hash functions without proper salting or iteration.Affected if Passwords are stored using a weak hashing algorithm such as unsalted MD5, SHA1, or another cryptographically fast hash function without salt or iteration.
-
Verify password file accessibilityCheck file permissions on the password database to determine if an attacker with local or backup access could obtain the file for offline cracking.Affected if The password storage file has weak permissions or is accessible to unauthorized users.
If the system is a Piigab M Bus 900s and stores passwords using a weak hashing algorithm (unsalted MD5, SHA1, or similar), it is affected by CVE-2023-34433.
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 dataReplace the weak hash algorithm with a modern, computationally expensive algorithm such as bcrypt, scrypt, or Argon2, and force password resets for all existing users.
- Consultation8.0 h
- Implementation16.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 $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-34433 — 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-34433 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