CVE-2016-5848 json
Siemens SICAM PAS before 8.07 does not properly restrict password data in the database, which makes it easier for local users to calculate…
published 2016-07-04 10 y ago modified 2026-06-17 4 mo ago also EUVD-2016-6783
- cvss
- 6.7
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 24%
- public exploits
- 0
- none known
Summary
Siemens SICAM PAS before 8.07 does not properly restrict password data in the database, which makes it easier for local users to calculate passwords by leveraging unspecified database privileges.
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
cisa ICSA-16-182-02B updated cvss 2.3
Siemens SICAM PAS Information Disclosure Vulnerabilities (Update B)
-
Siemens SICAM PAS <8.08affected: mitigation “For more information on this vulnerability and detailed instructions, please see Siemens Security Advisory SSA-444217 at the following location: (http://www.siemens.com/cert/advisories)”
From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf
Exploit prediction
0.31% chance of exploitation in the next 30 days, higher than 24% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 6.7 | CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 1.7 | AV:L/AC:L/Au:S/C:P/I:N/A:N |
Classification
References
-
siemens.com
/cert/pool/cert/siemens_security_advisory_ssa-444217.pdf
vendor-advisory
-
ics-cert.us-cert.gov
/advisories/ICSA-16-182-02
third-party-advisory, us-government-resource
-
securityfocus.com
/bid/91525
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2016-5848
- NVD CVE-2016-5848
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.