dbcve.org
Mdc N4090 FirmwareOperating system · Microdigital

CVE-2019-14698

CRITICAL · 9.8 CVSS v3.0 Published 2019-08-06
Fix available
A fix is available. Upgrade to after 6400.0.8.5 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
An issue was discovered on MicroDigital N-series cameras with firmware through 6400.0.8.5. In a CGI program running under the HTTPD web server, a buffer overflow in the param 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 · moderate confidence

Buffer overflow vulnerability in the param parameter of a CGI program running under the HTTPD web server on MicroDigital N-series IP cameras (firmware through 6400.0.8.5). The overflow allows remote attackers to execute arbitrary code in the context of the low-privilege 'nobody' account.

MitigationUpdate camera firmware to a version beyond 6400.0.8.5 if available; otherwise, restrict network access to the camera's web interface via firewall rules or network segmentation to prevent unauthenticated attackers from reaching the CGI endpoint.

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
Mdc N4090 FirmwareOperating system
Affected:<= 6400.0.8.5
Mdc N4090w FirmwareOperating system
Affected:<= 6400.0.8.5
Mdc N2190v FirmwareOperating system
Affected:<= 6400.0.8.5

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify camera model
    Access the camera's web interface or check the device label/serial to confirm the exact model number (Mdc N4090, N4090w, or N2190v).
    Affected if The model is one of: Mdc N4090, Mdc N4090w, or Mdc N2190v.
  2. Check firmware version
    Log into the camera's web admin interface and navigate to the System or Firmware settings page to view the installed firmware version. Alternatively, use the CGI endpoint or check via the device's API if available.
    Affected if The firmware version is 6400.0.8.5 or earlier.
  3. Verify web server is enabled
    Attempt to access the camera's web interface over HTTP/HTTPS (port 80 or 443) from a network client to confirm the HTTPD service is running.
    Affected if The web interface is accessible and responds to requests.
  4. Confirm CGI functionality
    Check if the CGI program (/cgi-bin/ or similar) is accessible by attempting a request to a known CGI endpoint on the camera. The vulnerability exists in a CGI program that handles the 'param' parameter.
    Affected if CGI programs are enabled and accessible on the web server.

The camera is affected if it is an Mdc N4090, N4090w, or N2190v model running firmware version 6400.0.8.5 or earlier with the web interface and CGI functionality enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 6400.0.8.5
Interim mitigation

Update camera firmware to a version beyond 6400.0.8.5 if available; otherwise, restrict network access to the camera's web interface via firewall rules or network segmentation to prevent unauthenticated attackers from reaching the CGI endpoint.

Recommended fix Moderate confidence

Firmware version greater than 6400.0.8.5 (check MicroDigital support for latest available version)

  1. 1. Identify the exact model number of the MicroDigital camera (N4090, N4090w, or N2190v)
  2. 2. Visit the official MicroDigital support website (www.microdigital.co.kr or www.microdigital.ru) to check for firmware updates
  3. 3. Download the latest firmware version available for your specific camera model
  4. 4. Review the firmware release notes to confirm the version addresses CVE-2019-14698
  5. 5. Follow the manufacturer's documented firmware upgrade procedure, typically involving uploading the firmware file through the web interface
  6. 6. After upgrading, verify the new firmware version is greater than 6400.0.8.5
  7. 7. Confirm the CGI program vulnerability is no longer exploitable
Caveat Firmware upgrades on embedded devices can sometimes reset configuration to defaults; backup current configuration before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Mdc N4090 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-14698 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-14698 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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