CVE-2019-14701
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 MicroDigital N-series cameras with firmware through 6400.0.8.5. An attacker can trigger read operations on an arbitrary file via Path Traversal in the TZ parameter, but cannot retrieve the data that is read. This causes a denial of service if the filename is, for example, /dev/random.
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 confidenceMicroDigital N-series cameras with firmware up to 6400.0.8.5 contain a path traversal vulnerability in the TZ (timezone) parameter. An attacker can manipulate this parameter to trigger read operations on arbitrary files in the filesystem. While the attacker cannot exfiltrate the read data, reading special files like /dev/random causes a denial-of-service condition by blocking or hanging the device.
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
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 the camera modelAccess the device web interface or check physical labels to confirm the model is one of: Mdc N4090, Mdc N4090w, or Mdc N2190vAffected if The device is any of these three models.
-
Check the firmware versionIn the device web interface, navigate to the system or status page and locate the firmware version field. Compare it to 6400.0.8.5Affected if The firmware version is 6400.0.8.5 or lower.
-
Verify the web interface is accessibleAttempt to access the device HTTP interface at the IP address on ports 80 or 443. Confirm the /cgi-bin/ endpoint responds.Affected if The web management interface is reachable from a network segment accessible to potential attackers.
-
Confirm TZ parameter exposureLocate the timezone (TZ) setting in the device web interface, typically under system, date/time, or regional settings.Affected if The timezone parameter is present and user-controllable in the web interface.
A user is affected if they have a Microdigital Mdc N4090, N4090w, or N2190v camera running firmware version 6400.0.8.5 or lower, with the web interface accessible on the network.
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 firmware updates from the vendor if available, or implement network segmentation and restrict camera management interfaces to authorized networks to reduce exposure to unauthenticated attackers.
- 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-14701 — 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-14701 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