CVE-2016-6535
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 · uneditedAVer Information EH6108H+ devices with firmware X9.03.24.00.07l have hardcoded accounts, which allows remote attackers to obtain root access by leveraging knowledge of the credentials and establishing a TELNET session.
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 confidenceThe AVer Information EH6108H+ video encoder device ships with firmware X9.03.24.00.07l containing hardcoded credentials embedded in the system. Attackers who discover these credentials can authenticate via the TELNET service to gain immediate root-level access to the device.
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= x9.03.24.00.07lCVSS 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 the device modelLocate the video encoder device and confirm it is an AVer Information EH6108H+ model. This can be done via device documentation, web interface, or physical label inspection.Affected if The device is an AVer EH6108H+ video encoder
-
Check the firmware versionAccess the device web interface or use SNMP to retrieve the installed firmware version. Compare it to the affected version X9.03.24.00.07l.Affected if The firmware version is exactly X9.03.24.00.07l
-
Verify if TELNET service is enabledScan the device network ports or check the device configuration to determine if TELNET (port 23) is enabled and accessible.Affected if TELNET service is enabled and reachable on the device
-
Check for hardcoded credentialsInspect the device firmware image or configuration files for embedded credentials. If TELNET is accessible, attempt authentication using any discovered default or hardcoded credentials.Affected if Hardcoded credentials exist in the firmware and grant root access via TELNET
-
Assess network exposure of TELNETDetermine if the device TELNET port is exposed to untrusted networks or the internet by reviewing firewall rules and network access controls.Affected if TELNET port is accessible from untrusted networks
The environment is affected if the device is an AVer EH6108H+ running firmware X9.03.24.00.07l with TELNET enabled and hardcoded credentials present.
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 dataImmediately disable the TELNET service if not business-critical, change any default credentials, apply available firmware updates, and restrict network access to the device using firewall rules or network segmentation.
- 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-2016-6535 — 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-2016-6535 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