CVE-2020-15785 json
A vulnerability has been identified in Siveillance Video Client (All versions).
published 6y ago modified 4mo ago also EUVD-2020-7768
- cvss
- 5.3
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 50%
- public exploits
- 0
- none known
Summary
A 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.
Is CVE-2020-15785 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
cisa ICSA-20-252-05 updated cvss 5.3
Siemens Siveillance Video Client
-
Siemens Siveillance Video Clientaffected: vendor fix, mitigation support.industry.siemens.com
Facts from CISA's republication of the vendor's own advisory (CSAF); the linked advisory is the authoritative source. CISA notification · csaf
Exploit prediction
0.62% chance of exploitation in the next 30 days, higher than 50% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:P/I:N/A:N |
Affected products
- Siemens AG Siveillance Video Client
Classification
- Weakness
-
- CWE-319 Cleartext Transmission of Sensitive Information
References
-
cert-portal.siemens.com
/productcert/pdf/ssa-770698.pdf
vendor-advisory
-
us-cert.cisa.gov
/ics/advisories/icsa-20-252-05
third-party-advisory, us-government-resource
Sources
- CVE List CVE-2020-15785
- NVD CVE-2020-15785
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.