CVE-2022-27480 json
A vulnerability has been identified in SICAM A8000 CP-8031 (All versions < V4.80), SICAM A8000 CP-8050 (All versions < V4.80).
published 2022-04-12 4 y ago modified 2026-06-17 4 mo ago also EUVD-2022-31981
- cvss
- 7.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.5%
- EPSS 2.5% chance of exploitation in 30 days, percentile 84%
- public exploits
- 0
- none known
Summary
A vulnerability has been identified in SICAM A8000 CP-8031 (All versions < V4.80), SICAM A8000 CP-8050 (All versions < V4.80). Affected devices do not require an user to be authenticated to access certain files. This could allow unauthenticated attackers to download these files.
Patch / fix
- siemens sicam_a8000_cp-8031_firmware 4.80
- siemens sicam_a8000_cp-8050_firmware 4.80
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
cisa ICSA-22-104-10 updated cvss 5.3
Siemens SICAM A8000
-
Siemens SICAM A8000 CP-8031 <V4.80 Siemens SICAM A8000 CP-8050 <V4.80affected: fixed in V4.80 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
2.48% chance of exploitation in the next 30 days, higher than 84% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
Affected products
- Siemens SICAM A8000 CP-8031
- Siemens SICAM A8000 CP-8050
Classification
References
-
cert-portal.siemens.com
/productcert/pdf/ssa-316850.pdf
patch, vendor-advisory
-
seclists.org
/fulldisclosure/2022/Apr/20
mailing-list, third-party-advisory
-
packetstormsecurity.com
/files/166743/Siemens-A8000-CP-8050-CP-8031-SICAM-WEB-Missing-File-Download-Missing-Authentication.html
third-party-advisory, vdb-entry
Sources
- CVE List CVE-2022-27480
- NVD CVE-2022-27480
Fencer Vulns 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.