dbcve.org
Versa AnalyticsApplication · Versa Networks

CVE-2019-25030

MEDIUM · 5.5 CVSS v3.1 Published 2021-05-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

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 · unedited
In Versa Director, Versa Analytics and VOS, Passwords are not hashed using an adaptive cryptographic hash function or key derivation function prior to storage. Popular hashing algorithms based on the Merkle-Damgardconstruction (such as MD5 and SHA-1) alone are insufficient in thwarting password cracking. Attackers can generate and use precomputed hashes for all possible password character combinations (commonly referred to as "rainbow tables") relatively quickly. The use of adaptive hashing algorithms such asscryptorbcryptor Key-Derivation Functions (i.e.PBKDF2) to hash passwords make generation of such rainbow tables computationally infeasible.

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 confidence

Versa Director, Versa Analytics, and VOS store user passwords using weak, non-adaptive hashing algorithms (MD5/SHA-1) based on the Merkle-Damgard construction. This vulnerability allows attackers to use precomputed rainbow tables to efficiently crack stored password hashes, enabling unauthorized access to user accounts.

MitigationReplace MD5/SHA-1 password hashing with adaptive key derivation functions such as scrypt, bcrypt, or PBKDF2 with appropriate work factors, and implement a secure password migration strategy for existing stored hashes.

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
Versa AnalyticsApplication
Affected:all versions
Versa DirectorApplication
Affected:all versions
Versa Operating SystemOperating system
Affected:all versions

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Versa product
    Run 'show version' or check system inventory to confirm whether Versa Director, Versa Analytics, or VOS is deployed in your environment
    Affected if Any of these three products are running, as all versions are affected by weak password hashing
  2. Locate user credential storage
    Access the backend database or authentication configuration used by your Versa deployment. This is typically found in the application's database directory or authentication configuration files
    Affected if You can access the user database where password hashes are stored
  3. Examine password hash format
    Query the user table or password storage location and inspect the hash format. MD5 hashes appear as 32-character hexadecimal strings, SHA-1 as 40-character hexadecimal strings
    Affected if Password hashes are stored in MD5 or SHA-1 format without salting or iteration (non-adaptive algorithms)
  4. Verify hashing algorithm in configuration
    Inspect authentication-related configuration files for password hashing settings, looking for references to MD5, SHA-1, or similar legacy hashing methods
    Affected if Configuration specifies MD5 or SHA-1 for password hashing rather than adaptive functions like bcrypt, scrypt, or PBKDF2

If your Versa environment uses any of these three products and password hashes are stored in MD5/SHA-1 format without adaptive key derivation, you are affected by this vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace MD5/SHA-1 password hashing with adaptive key derivation functions such as scrypt, bcrypt, or PBKDF2 with appropriate work factors, and implement a secure password migration strategy for existing stored hashes.

Fix this in Versa Analytics Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-25030 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-25030 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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