CVE-2019-10710
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 · uneditedInsecure permissions in the Web management portal on all IP cameras based on Hisilicon Hi3510 firmware allow authenticated attackers to receive a network's cleartext WiFi credentials via a specific HTTP request. This affects certain devices labeled as HI3510, HI3518, LOOSAFE, LEVCOECAM, Sywstoda, BESDER, WUSONGLUSAN, GADINAN, Unitoptek, ESCAM, etc.
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 confidenceInsecure permission controls in the Web management portal of Hisilicon Hi3510-based IP camera firmware allow any authenticated user to retrieve cleartext WiFi network credentials via a specific HTTP request. The vulnerability stems from the application failing to enforce proper authorization checks on the endpoint that returns WiFi configuration data.
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 dataall versionsCVSS 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.
-
Identify Hisilicon Hi3510-based IP cameras in your environmentInventory network devices and check product documentation, device labels, or administrative interfaces for 'Hi3510' or 'Hisilicon' branding to confirm the camera modelAffected if Any Hisilicon Hi3510-based IP cameras are present in the environment
-
Confirm the Web management portal is accessibleAttempt to reach the camera's HTTP/HTTPS interface via its IP address from a network segment that has access to the deviceAffected if The Web management portal responds to HTTP/HTTPS requests and accepts authentication
-
Verify you can authenticate to the portalLog into the Web management portal with any valid user accountAffected if Authentication succeeds with any valid user credentials
-
Test for unauthorized WiFi credential accessUsing an authenticated session, submit an HTTP request to the endpoint that returns WiFi configuration data. If the exact endpoint is unknown, inspect network traffic or documentation for WiFi settings pages and attempt to retrieve configuration via direct HTTP requestsAffected if WiFi network credentials are returned in cleartext to any authenticated user, regardless of privilege level
-
Check if authorization is enforced on WiFi data endpointsCompare access attempts from low-privilege vs administrator accounts to the WiFi configuration endpoint. If both can retrieve the same cleartext credentials, proper authorization is not enforcedAffected if Non-administrator accounts can retrieve WiFi credentials that should only be visible to administrators
If you have any Hisilicon Hi3510-based IP camera with an accessible Web management portal, you are affected because all versions of this firmware contain the authorization bypass allowing any authenticated user to retrieve cleartext WiFi 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 dataPrioritize firmware updates from device manufacturers; if unavailable, implement network segmentation to isolate cameras and restrict Web management portal access to authorized administration VLANs only.
- Consultation4.0 h
- Implementation8.0 h
- Testing3.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 $4,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10710 — 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-2019-10710 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