CVE-2017-7912
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 · uneditedHanwha Techwin SRN-4000, SRN-4000 firmware versions prior to SRN4000_v2.16_170401, A specially crafted http request and response could allow an attacker to gain access to the device management page with admin privileges without proper authentication.
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 confidenceThe Hanwha Techwin SRN-4000 NVR contains an authentication bypass vulnerability where a specially crafted HTTP request and response allows an attacker to gain admin access to the device management page without providing valid credentials. This is a pre-authentication compromise affecting firmware versions prior to SRN4000_v2.16_170401.
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< 2.16_170401CVSS 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.
-
Check SRN-4000 firmware version via web interfaceLog into the device web management interface and navigate to System or About section, typically found under Settings > System Information or a System Info/About page. Locate the firmware version field.Affected if The displayed firmware version is lower than 2.16_170401 (for example, 2.15_161230 or any version prior to 2.16_170401)
-
Verify the exact firmware version numberConfirm the full version string shown in the system information page matches the vulnerable range. Note that some interfaces display only partial version numbers.Affected if The version string does not contain 2.16_170401 or a later date code
-
Check if remote HTTP management is accessibleAttempt to access the device login page over HTTP/HTTPS from a network perspective to confirm the management interface is exposed.Affected if The web management interface is reachable from network segments where untrusted users could send HTTP requests
The device is affected if it is running any SRN-4000 firmware version prior to 2.16_170401 and has the web management interface accessible on the network.
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.
dbcve · scoped2.16_170401
Update the SRN-4000 firmware to version SRN4000_v2.16_170401 or later. If patching is not immediately possible, restrict network access to the device management interface using firewall rules or VLAN segmentation.
SRN4000_v2.16_170401 or later
- 1. Download the firmware version SRN4000_v2.16_170401 or later from the Hanwha Techwin official support website
- 2. Access the SRN-4000 device management interface
- 3. Navigate to the firmware upgrade section (typically under System > Maintenance or Settings > Firmware Upgrade)
- 4. Upload the downloaded firmware file
- 5. Wait for the firmware update process to complete and the device to reboot
- 6. Verify the firmware version has been updated successfully by checking the device status page
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-7912 — 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-7912 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