CVE-2017-14262
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 · uneditedOn Samsung NVR devices, remote attackers can read the MD5 password hash of the 'admin' account via certain szUserName JSON data to cgi-bin/main-cgi, and login to the device with that hash in the szUserPasswd parameter.
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 confidenceSamsung NVR devices contain an information disclosure vulnerability in the cgi-bin/main-cgi endpoint. Remote unauthenticated attackers can send specially crafted szUserName JSON data to receive the MD5 password hash of the admin account. The system then accepts this hash directly in the szUserPasswd parameter for authentication, effectively allowing attackers to authenticate as admin using the exposed hash.
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 dataall versionsall versionsall versionsall versionsCVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:H/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 NVR device modelAccess the device web interface or check the physical device label to determine if the model is Samsung Srn 1670d, Srn 1000, Srn 472s, or Srn 470dAffected if The device model is one of the four listed Samsung NVR models (Srn 1670d, Srn 1000, Srn 472s, or Srn 470d)
-
Check firmware versionLog into the device web interface and navigate to the System or About section to view the firmware versionAffected if The device is running any firmware version on the affected models (all versions are affected per the CVE)
-
Verify web interface accessibilityAttempt to access the device web interface via HTTP/HTTPS on the local network by navigating to the device IP addressAffected if The web interface is reachable from a network where unauthenticated attackers could send requests
-
Check cgi-bin/main-cgi endpoint exposureSend an HTTP GET request to http://[device-ip]/cgi-bin/main-cgi and observe if the endpoint respondsAffected if The cgi-bin/main-cgi endpoint is accessible and responds to requests without authentication
If the device is a Samsung Srn 1670d, Srn 1000, Srn 472s, or Srn 470d NVR with an accessible web interface and cgi-bin/main-cgi endpoint, the environment is likely affected by this vulnerability.
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 dataRestrict network access to the NVR devices, apply any available Samsung firmware updates, and consider network segmentation or firewall rules to limit exposure to the cgi-bin/main-cgi endpoint.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.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,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-14262 — 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-2017-14262 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