CVE-2019-14702
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. SQL injection vulnerabilities exist in 13 forms that are reachable through HTTPD. An attacker can, for example, create an admin account.
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 confidenceSQL injection vulnerabilities in 13 HTTP-accessible forms on MicroDigital N-series IP cameras (firmware through 6400.0.8.5) allow remote unauthenticated attackers to inject arbitrary SQL commands. This can result in authentication bypass, enabling attackers to create administrative accounts and gain full device control.
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 the camera modelAccess the camera's web interface and look for the model number in the system information or status page, or check the device label/stickerAffected if The model is NOT one of: Mdc N4090, Mdc N4090w, or Mdc N2190v (these are the only affected models)
-
Check the firmware versionIn the camera web interface, navigate to the firmware or system info page to view the installed firmware version numberAffected if The firmware version is 6400.0.8.5 or lower (versions above 6400.0.8.5 are not affected)
-
Confirm HTTP management interface is accessibleAttempt to access the camera's IP address on port 80 (HTTP) or port 443 (HTTPS) from a browserAffected if The HTTP/HTTPS management interface is reachable (this is required for the SQL injection to be exploitable)
-
Verify network exposureDetermine if the camera HTTP port is accessible from untrusted networks by checking firewall rules, NAT configurations, or port forwarding settingsAffected if The camera HTTP interface is exposed directly to the internet or untrusted networks (this indicates higher risk exposure for unauthenticated attacks)
You are affected if you have a MicroDigital Mdc N4090, N4090w, or N2190v camera running firmware version 6400.0.8.5 or lower, with the HTTP management interface accessible to the network where the attacker resides.
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 if available; otherwise isolate cameras behind a firewall or VLAN to restrict HTTP management access to trusted networks only.
- Consultation4.0 h
- Implementation4.0 h
- Testing3.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 $3,728.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-14702 — 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-14702 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