CVE-2018-13802 json
A vulnerability has been identified in ROX II (All versions < V2.12.1).
published 2018-10-10 8 y ago modified 2026-06-17 4 mo ago also EUVD-2018-5738
- cvss
- 7.2
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.6%
- EPSS 3.6% chance of exploitation in 30 days, percentile 89%
- public exploits
- 0
- none known
Summary
A vulnerability has been identified in ROX II (All versions < V2.12.1). An authenticated attacker with a high-privileged user account access via SSH could circumvent restrictions in place and execute arbitrary operating system commands. Successful exploitation requires that the attacker has network access to the SSH interface in on port 22/tcp. The attacker must be authenticated to exploit the vulnerability. The vulnerability could allow an attacker to execute arbitrary code on the device.
Patch / fix
- siemens rox_ii_firmware 2.12.1
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
cisa ICSA-18-282-03 updated cvss 7.2
ICSA-18-282-03 Siemens ROX II
-
Siemens ROX II <V2.12.1affected: fixed in V2.12.1, 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
3.57% chance of exploitation in the next 30 days, higher than 89% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 7.2 | CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 9.0 | AV:N/AC:L/Au:S/C:C/I:C/A:C |
Affected products
- Siemens AG ROX II
Classification
References
-
cert-portal.siemens.com
/productcert/pdf/ssa-493830.pdf
vendor-advisory
-
ics-cert.us-cert.gov
/advisories/ICSA-18-282-03
third-party-advisory, us-government-resource
-
securityfocus.com
/bid/105545
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2018-13802
- NVD CVE-2018-13802
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.