CVE-2017-3186
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 · uneditedACTi cameras including the D, B, I, and E series using firmware version A1D-500-V6.11.31-AC use non-random default credentials across all devices. A remote attacker can take complete control of a device using default admin credentials.
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 confidenceACTi camera models (D, B, I, E series) running firmware A1D-500-V6.11.31-AC ship with non-random default administrative credentials that are identical across all devices. A remote unauthenticated attacker can leverage these static default credentials to authenticate as administrator and gain full control of the camera.
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= a1d-500-v6.11.31-acCVSS 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.
-
Identify ACTi cameras on the networkScan network for devices with ACTi vendor MAC OUI or look for ACTi web interfaces on ports 80/443. Common camera model identifiers include D-series, B-series, I-series, or E-series in device listings or DHCP logs.Affected if ACTi cameras (D, B, I, or E series) are found on the network
-
Check the firmware versionAccess the camera web interface or use SNMP to query the sysDescr or firmware version OID. Look for firmware version 'a1d-500-v6.11.31-ac'.Affected if Firmware version matches exactly 'a1d-500-v6.11.31-ac'
-
Determine if default administrative credentials are still in useAttempt to authenticate to the camera administrative interface using the known default credentials for this firmware version. Alternatively, check if the administrative password has been changed from the factory default by reviewing saved configurations or password policies.Affected if The default administrative credentials have not been changed and remain at their factory-set values
A user is affected if they have ACTi cameras running firmware A1D-500-V6.11.31-AC that still use the original default administrative credentials.
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 · scopedImmediately change default credentials on all affected cameras. Contact ACTi for updated firmware that implements unique per-device credentials. If firmware update is unavailable, restrict network access to cameras via firewall rules or VLAN segmentation to limit exposure to trusted networks.
- Access the camera's web-based administration interface using the default IP address
- Log in using the default administrator credentials (consult ACTi documentation or common default credentials for this firmware version)
- Navigate to the user management or administrator settings section
- Change the default admin password to a strong, unique password following best practices
- Verify the new credentials work by logging out and logging back in
- Ensure the new password is documented in a secure password manager
- Check ACTi's support website for any firmware updates that may address this vulnerability
- If multiple cameras are deployed, ensure each has unique credentials
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-3186 — 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-3186 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