CVE-2019-14699
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 exploit OS Command Injection in the filename parameter for remote code execution as root. This occurs in the Mainproc executable file, which can be run from the HTTPD web server.
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 confidenceOS Command Injection vulnerability in MicroDigital N-series IP cameras firmware (through 6400.0.8.5) allows remote attackers to execute arbitrary commands as root via the filename parameter in the Mainproc executable running on the HTTPD web server.
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 modelAccess the camera's web interface or check the device label/metadata to confirm the exact model number is one of: Mdc N4090, Mdc N4090w, or Mdc N2190vAffected if The model is any of these three variants
-
Check firmware versionLog into the camera's web interface and navigate to System > Firmware/Version, or use the camera's API to query the firmware version. Compare against the affected version 6400.0.8.5Affected if Firmware version is 6400.0.8.5 or lower
-
Verify HTTPD web server is enabledAttempt to access the camera's web interface via HTTP (port 80/8080) or check the camera's network configuration to confirm the web server is runningAffected if The web server is accessible on the network
-
Confirm Mainproc endpoint accessibilitySend an HTTP request to the Mainproc endpoint with a test parameter (e.g., /cgi-bin/Mainproc?filename=test) to verify the vulnerable parameter is exposedAffected if The Mainproc CGI endpoint responds to requests with the filename parameter
The device is affected if it is an Mdc N4090, N4090w, or N2190v model running firmware version 6400.0.8.5 or lower with the HTTPD web server enabled and Mainproc endpoint 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 dataUpgrade firmware to a patched version beyond 6400.0.8.5; if unavailable, restrict network access to the camera web interface and disable remote administration until a patch is released.
- Consultation3.0 h
- Implementation6.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-14699 — 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-14699 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