CVE-2019-14708
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. A buffer overflow in the action parameter leads to remote code execution in the context of the nobody 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 confidenceA buffer overflow vulnerability in the 'action' parameter of MicroDigital N-series IP cameras (firmware up to 6400.0.8.5) allows unauthenticated remote attackers to execute arbitrary code. The exploit executes in the context of the low-privilege 'nobody' account, which may limit immediate system impact but could enable further privilege escalation.
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 MicroDigital N-series camera modelAccess the camera web interface and look for the model name (N4090, N4090w, N2190v) in the device info page, or query the device via SNMP/OID for system descriptionAffected if Device model is not one of the listed N-series models (N4090, N4090w, N2190v)
-
Retrieve firmware versionIn the camera web interface, navigate to System or Device Info section to view firmware version, or use SNMP query to check firmware/revision OIDsAffected if Unable to retrieve firmware version or device does not have a web interface
-
Compare installed firmware to affected versionCompare the retrieved firmware version against the vulnerable range: versions <= 6400.0.8.5Affected if Firmware version is 6400.0.8.5 or lower
-
Verify network exposure of web interfaceCheck if the camera HTTP/HTTPS ports (typically 80/443) are accessible from untrusted networks, or perform a port scan to confirm open HTTP serviceAffected if Camera web interface is exposed to untrusted networks without firewall protection
You are affected if you have a MicroDigital N4090, N4090w, or N2190v camera running firmware version 6400.0.8.5 or lower, and the web interface is network-accessible.
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 dataIdentify all affected MicroDigital N-series cameras on the network, verify firmware versions, and apply any available vendor firmware updates. If no patch exists, isolate cameras behind a firewall or VLAN to limit attack surface.
- Consultation6.0 h
- Implementation12.0 h
- Testing4.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-14708 — 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-14708 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