CVE-2020-15785
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 · uneditedA vulnerability has been identified in Siveillance Video Client (All versions). In environments where Windows NTLM authentication is enabled the affected client application transmits usernames to the server in cleartext. This could allow an attacker in a privileged network position to obtain valid adminstrator login names and use this information to launch further attacks.
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 confidenceThe Siveillance Video Client transmits usernames in cleartext to the server when Windows NTLM authentication is enabled. This information disclosure occurs during the authentication handshake, allowing an attacker with network-level access to capture valid administrator usernames via packet sniffing or man-in-the-middle techniques.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
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.
-
Confirm Siveillance Video Client installationLocate the Siveillance Video Client application on the system, typically found in the program files directory or listed in installed programs. Verify the software is present and operational.Affected if The software is installed and running on the system.
-
Check if NTLM authentication is enabledExamine the client configuration settings or server settings for the Siveillance Video deployment. Look for authentication method configuration, specifically whether Windows NTLM authentication is selected or enabled.Affected if NTLM authentication is enabled as the authentication mechanism between client and server.
-
Verify TLS encryption statusInspect the client-server communication configuration to determine whether TLS or SSL encryption is enforced for all connections. Check if encrypted communication channels are configured for the Video Client.Affected if TLS encryption is not enforced and NTLM authentication is being used without encrypted transport.
-
Inspect network traffic for cleartext usernamesCapture network packets during the authentication handshake between the Siveillance Video Client and server. Look for username strings transmitted in cleartext during the NTLM authentication exchange.Affected if Network capture reveals usernames transmitted in cleartext during client-server authentication.
A user is affected if Siveillance Video Client is installed with NTLM authentication enabled and without TLS encryption protecting the authentication handshake, allowing username disclosure via network sniffing.
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 dataDisable NTLM authentication in favor of Kerberos or implement TLS encryption for all client-server communications. Network segmentation and monitoring can also help detect attempts to exploit this vulnerability.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.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 $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-15785 — 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-2020-15785 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