CVE-2019-14707
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. The firmware update process is insecure, leading to remote code execution. The attacker can provide arbitrary firmware in a .dat file via a webparam?system&action=set&upgrade URI.
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 have an insecure firmware update mechanism. The webparam?system&action=set&upgrade endpoint lacks proper authentication and validation, allowing attackers to upload arbitrary .dat firmware files and achieve remote code execution.
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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:H/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 the camera modelAccess the camera web interface or use the device's API to retrieve the model number. Check if the device is a Microdigital Mdc N4090, N4090w, or N2190v model.Affected if The device model is one of: Mdc N4090, Mdc N4090w, or Mdc N2190v.
-
Check the firmware versionAccess the camera's admin panel or use the device's API to retrieve the firmware version. Look for a version field in the system information or status page.Affected if The installed firmware version is 6400.0.8.5 or lower.
-
Test unauthenticated access to the update endpointAttempt to access the URL path /webparam?system&action=set&upgrade directly without providing any login credentials. Observe if the endpoint responds or accepts requests.Affected if The endpoint responds without requiring authentication.
-
Verify if HTTP is used for managementCheck if the camera web interface is accessible over HTTP (port 80) rather than only HTTPS. Attempt to connect to the device using HTTP.Affected if The management interface is accessible over unencrypted HTTP.
The device is affected if it is a Microdigital N4090, N4090w, or N2190v model running firmware version 6400.0.8.5 or lower, and the /webparam?system&action=set&upgrade endpoint is accessible without authentication.
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 dataImplement authentication requirements for the firmware update endpoint and add cryptographic signature verification to ensure only legitimate, signed firmware can be installed. Consider also enforcing HTTPS for all management interfaces.
- Consultation6.0 h
- Implementation20.0 h
- Testing10.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 $11,232.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-14707 — 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-14707 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