CVE-2019-10855
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 · uneditedComputrols CBAS 18.0.0 mishandles password hashes. The approach is MD5 with a pw prefix, e.g., if the password is admin, it will calculate the MD5 hash of pwadmin and store it in a MySQL database.
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 confidenceComputrols CBAS 18.0.0 uses a weak password hashing mechanism combining MD5 with a static 'pw' prefix (e.g., password 'admin' becomes MD5('pwadmin')). MD5 is cryptographically broken and vulnerable to rainbow table attacks and collision attacks, allowing attackers to recover plaintext passwords if the database is compromised.
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<= 19.0.0CVSS 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
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/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.
-
Determine installed CBAS versionLocate the CBAS installation directory and check the version information, typically found in the software's About section, installation logs, or version file within the program directory.Affected if Version is 19.0.0 or lower (e.g., 18.0.0, 17.x, etc.)
-
Inspect database password storageAccess the application's database (likely Microsoft SQL Server or similar) and query the user or account table to examine how passwords are stored. Look for hexadecimal hash strings that may be 32 characters long (MD5 length).Affected if Passwords are stored as 32-character hexadecimal strings consistent with MD5 format, particularly if prefixed or transformed in a predictable manner.
-
Check for static salt or prefix in password hashingReview any available application configuration files, authentication modules, or source code (if accessible) to identify the password hashing implementation. Look for any string concatenation like 'pw' + password before hashing.Affected if The code or configuration shows a static prefix such as 'pw' concatenated to passwords before MD5 hashing.
-
Verify MD5 usage in authentication moduleExamine the authentication or security module files within the CBAS installation for MD5 function calls used for password hashing. Search for 'MD5' in relevant source or configuration files.Affected if MD5 is actively used for password hashing in the authentication process.
A user is affected if their installed CBAS version is 19.0.0 or lower and the application stores passwords using MD5 hashing combined with a static 'pw' prefix, making them vulnerable to rainbow table attacks if the database is compromised.
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 MD5 with a modern password hashing algorithm like bcrypt, scrypt, or Argon2 with per-password salting. Migrate existing password hashes by requiring users to reset passwords or re-hashing with the new algorithm upon successful login.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10855 — 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-2019-10855 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