CVE-2019-14709
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 · uneditedA cleartext password storage issue was discovered on MicroDigital N-series cameras with firmware through 6400.0.8.5. The file in question is /usr/local/ipsca/mipsca.db. If a camera is compromised, the attacker can gain access to passwords and abuse them to compromise further systems.
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 confidenceMicroDigital N-series cameras with firmware through 6400.0.8.5 store user credentials in cleartext within the database file /usr/local/ipsca/mipsca.db. An attacker who compromises the device can directly read this file to obtain plaintext passwords, enabling lateral movement to other systems using those credentials.
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<= 6400.0.8.5<= 6400.0.8.5<= 6400.0.8.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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/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.
-
Identify camera modelLog into the camera web interface or check the device label to confirm the exact model (Mdc N4090, Mdc N4090w, or Mdc N2190v)Affected if Model is Mdc N4090, Mdc N4090w, or Mdc N2190v
-
Check firmware versionAccess the camera's web interface under System > Info or use the ONVIF/SNMP interface to retrieve the firmware version numberAffected if Firmware version is 6400.0.8.5 or lower
-
Locate the database fileAccess the device via SSH or UART and attempt to read /usr/local/ipsca/mipsca.db (requires root or limited shell access)Affected if The file /usr/local/ipsca/mipsca.db exists on the device
-
Verify cleartext credentialsOpen the mipsca.db file using sqlite3 or a hex editor and search for user account entries to confirm passwords are stored in plaintext rather than hashedAffected if User credentials in the database appear as plaintext passwords
A user is affected if they have a MicroDigital Mdc N4090, N4090w, or N2190v camera running firmware version 6400.0.8.5 or lower, and the /usr/local/ipsca/mipsca.db file contains plaintext passwords.
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 dataApply vendor firmware patch when available; if patch is unavailable, implement network segmentation to isolate cameras, rotate all compromised credentials, and monitor for unauthorized access using the exposed credentials.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-14709 — 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-14709 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