CVE-2017-10835
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 · unedited"Dokodemo eye Smart HD" SCR02HD Firmware 1.0.3.1000 and earlier allows authenticated attackers to conduct code injection attacks 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 confidenceAuthenticated code injection vulnerability in Dokodemo eye Smart HD SCR02HD IP camera firmware 1.0.3.1000 and earlier allows remote attackers to inject arbitrary code via unspecified vectors. The attacker requires valid authentication credentials to exploit this flaw.
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<= 1.0.3.1000CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/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.
-
Check the device firmware versionAccess the IP camera's web administration interface (typically via HTTP/HTTPS on the device's IP address). Navigate to the System or Settings section and locate the firmware version information. The version is usually displayed on a status, info, or about page.Affected if The displayed firmware version is 1.0.3.1000 or earlier.
-
Verify the exact model identificationIn the same web interface, confirm the device model is either "Scr02hd", "SCR02HD", or "Dokodemo eye Smart HD" as the affected product. This ensures you are checking the correct vulnerable device.Affected if The model matches Scr02hd/SCR02HD and the firmware is at or below 1.0.3.1000.
-
Determine if remote web access is enabledCheck the network settings in the camera's administration interface for remote access, web server, or DDNS configuration options. Verify if the HTTP/HTTPS ports are listening on external interfaces or if port forwarding is configured on the network.Affected if Remote web administration is enabled and the camera interface is accessible from outside the local network.
-
Check for unauthenticated network exposureFrom an external network location, attempt to reach the camera's IP address and web port. Use a network scanner to determine if the device's web interface is exposed to the internet or an untrusted network.Affected if The camera's web interface is directly accessible from an untrusted network without VPN or firewall protection.
You are affected if your Scr02hd/SCR02HD camera runs firmware version 1.0.3.1000 or earlier and has its web interface accessible to network attackers who could obtain valid 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.
From vendor dataUpgrade firmware to version greater than 1.0.3.1000. Additionally, restrict network access to the device, enforce strong authentication credentials, and monitor for unauthorized access attempts.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-10835 — 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-10835 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