CVE-2019-14705
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 Incorrect Access Control issue was discovered on MicroDigital N-series cameras with firmware through 6400.0.8.5 because any valid cookie can be used to make requests as an admin.
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 confidenceMicroDigital N-series IP cameras with firmware through 6400.0.8.5 contain an incorrect access control vulnerability where any valid authentication cookie (regardless of user privilege level) can be used to perform administrative actions. The system fails to properly validate that the cookie belongs to an admin user before granting elevated privileges.
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 camera modelLog into the camera web interface or check device documentation to confirm the exact model number is one of: Mdc N4090, Mdc N4090w, or Mdc N2190vAffected if Camera model is not one of the listed affected models - you are likely not affected
-
Check firmware versionAccess the camera web interface, typically under Settings > System > Firmware or About page, to find the installed firmware version numberAffected if Firmware version is 6400.0.8.5 or lower - you may be affected
-
Verify admin privilege validationLog in with a non-administrator user account and attempt to access or execute an administrative function (such as modifying system settings, user management, or firmware update). Observe whether the action is denied or allowedAffected if A non-admin user can successfully perform admin-level actions using only a valid cookie - you are affected by this vulnerability
-
Test cookie reuse behaviorCapture an authentication cookie from a standard user session, then use that cookie to make a direct HTTP request to an administrative endpoint (e.g., /admin/settings or similar). Check if the request succeeds without additional privilege verificationAffected if A valid cookie from a low-privilege user can be reused to execute administrative operations - the access control flaw is present
If the camera model matches one of the affected Mdc N4090/N4090w/N2190v units and runs firmware version 6400.0.8.5 or lower, AND a non-admin user can perform admin actions, then the environment is affected by CVE-2019-14705.
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 dataUpdate camera firmware to a patched version if available. If no patch exists, restrict network access to cameras via firewall rules or network segmentation to limit exposure to untrusted users.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-14705 — 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-14705 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