CVE-2025-10285
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 · uneditedThe web interface of the Silicon Labs Simplicity Device Manager is exposed publicly and can be used to extract the NTLMv2 hash which an attacker could use to crack the user's domain password.
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 Silicon Labs Simplicity Device Manager web interface, when exposed publicly without proper access controls, allows unauthenticated attackers to capture NTLMv2 authentication hashes. These hashes can be collected through techniques like HTTP negotiation capture or responder attacks, then cracked offline to recover user domain credentials.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- None
- Authentication
- X
- User interaction
- P
- Scope
- X
CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
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 Simplicity Device Manager installationCheck for the Simplicity Device Manager web interface by accessing its default ports (typically HTTP on 80/8080 or HTTPS on 443/8443) or search for running processes related to Silicon Labs device managementAffected if The web interface is running and accessible on any network interface
-
Verify network exposure of the web interfaceDetermine if the Simplicity Device Manager is bound to 0.0.0.0 or an externally accessible IP address. Use 'netstat -an' or similar network tools to identify listening addresses and check firewall rules for inbound access from untrusted networksAffected if The interface listens on public-facing IP addresses or has firewall rules allowing untrusted network access
-
Check for NTLM authentication configurationInspect the Simplicity Device Manager configuration files or web server settings for NTLM or Windows Authentication enablement. This may be found in configuration files under the installation directory or in the web server settingsAffected if NTLM or Windows Authentication is enabled in the web interface configuration
-
Confirm credential caching or relay exposureReview network logs or conduct a test HTTP request to observe if the server attempts NTLM authentication negotiation. Use a test tool to trigger NTLM handshake and verify if the server responds with NTLM challengeAffected if The server responds to unauthenticated requests with NTLM challenge/response negotiation
You are affected if the Simplicity Device Manager web interface is exposed to untrusted networks with NTLM authentication enabled, allowing attackers to capture authentication hashes via HTTP negotiation.
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 dataRestrict public access to the Simplicity Device Manager web interface using firewall rules, VPN, or network segmentation. If NTLM authentication is required, disable it in favor of stronger authentication mechanisms.
- Consultation2.0 h
- Implementation2.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,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-10285 — 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-2025-10285 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