CVE-2019-7673
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 · uneditedAn issue was discovered on MOBOTIX S14 MX-V4.2.1.61 devices. Administrator Credentials are stored in the 13-character DES hash format.
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 confidenceMOBOTIX S14 MX-V4.2.1.61 devices store administrator credentials using weak 13-character DES hashing, which is cryptographically outdated and vulnerable to offline brute-force cracking attacks. The 13-character DES format uses only 2 characters of salt making it susceptible to rainbow table attacks and modern GPU-based cracking.
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= mx-v4.2.1.61CVSS 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.
-
Identify the device modelAccess the MOBOTIX S14 web interface or check the device label/documentation to confirm the device model is S14Affected if The device is not a MOBOTIX S14 model, then this specific CVE does not apply
-
Check the firmware versionLog into the MOBOTIX S14 web interface and navigate to Admin > Overview or System > Software to view the installed firmware version. Alternatively, access the device via SSH and run: cat /etc/version or look for mx-v4.2.1.61 in the system informationAffected if The firmware version is exactly mx-v4.2.1.61 - only this specific version is listed as affected
-
Verify password storage mechanismAccess the device configuration files or password database. On the web interface, navigate to Admin > Users or examine the /etc/passwd or /etc/shadow file via SSH to inspect the password hash format. Look for 13-character DES hashes (typically starting with 2-character salt followed by 11 characters of encrypted password)Affected if Administrator password hashes appear as 13-character DES-based strings (format: 2 salt chars + 11 hash chars), indicating the weak hashing is in use
A MOBOTIX S14 device running firmware version mx-v4.2.1.61 with 13-character DES password hashes is affected by this vulnerability.
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 dataUpdate to a patched firmware version using modern password hashing (bcrypt, scrypt, or Argon2). If no patch available, implement compensating controls including network segmentation, strict ACLs, MFA, and monitor for unauthorized access attempts.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-7673 — 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-7673 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