CVE-2017-13774
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 · uneditedHikvision iVMS-4200 devices before v2.6.2.7 allow local users to generate password-recovery codes via unspecified vectors.
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 confidenceHikvision iVMS-4200 video management software versions before v2.6.2.7 contains a vulnerability allowing local authenticated users to generate password-recovery codes through unspecified vectors. This could enable privilege escalation or unauthorized account access.
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.6.2.6CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:L/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.
-
Locate iVMS-4200 installation directoryCheck common installation paths such as C:\Program Files\Hikvision\iVMS-4200 or C:\Program Files (x86)\Hikvision\iVMS-4200, or search for the iVMS-4200 executable file on the systemAffected if The software is found installed on the system
-
Determine installed versionRight-click the iVMS-4200 executable (typically named iVMS-4200.exe or similar) and select Properties, then navigate to the Details tab to view the File Version or Product VersionAffected if The displayed version number is 2.6.2.6 or lower
-
Compare version to affected rangeReview the version number identified in the previous step against the affected range: any version less than 2.6.2.7 (including 2.6.2.6, 2.6.2.5, 2.6.2.4, etc.) is vulnerableAffected if The installed version is less than 2.6.2.7 (e.g., 2.6.2.6 or earlier)
-
Verify local user accessConfirm that local user accounts exist on the system where iVMS-4200 is installed, as the vulnerability specifically affects local authenticated usersAffected if Local Windows user accounts are present on the system running the vulnerable software version
If iVMS-4200 version 2.6.2.6 or earlier is installed and local user authentication is available, the environment is 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 dataUpgrade iVMS-4200 to version 2.6.2.7 or later. Until patched, restrict local access to trusted personnel only and monitor for unauthorized password recovery attempts.
- Consultation2.0 h
- Implementation1.0 h
- Testing1.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,456.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-13774 — 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-13774 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