CVE-2018-4836 json
A vulnerability has been identified in TeleControl Server Basic < V3.1.
published 2018-01-25 8 y ago modified 2026-06-17 4 mo ago also EUVD-2018-16622
- cvss
- 8.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.8%
- EPSS 1.8% chance of exploitation in 30 days, percentile 78%
- public exploits
- 0
- none known
Summary
A vulnerability has been identified in TeleControl Server Basic < V3.1. An authenticated attacker with a low-privileged account to the TeleControl Server Basic's port 8000/tcp could escalate his privileges and perform administrative operations.
Patch / fix
- siemens telecontrol_server_basic 3.1
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
cisa ICSA-18-030-02 updated cvss 8.8
Siemens TeleControl Server Basic
-
Siemens TeleControl Server Basic < 3.1affected: vendor fix, mitigation “If TeleControl Server Basic is operated in standalone mode, then users can close Port 8000/TCP on the Windows firewall to mitigate vulnerabilities CVE-2018-4835 and CVE-2018-4836.” support.industry.siemens.com
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
1.80% chance of exploitation in the next 30 days, higher than 78% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 8.8 | CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 6.5 | AV:N/AC:L/Au:S/C:P/I:P/A:P |
Affected products
- Siemens AG TeleControl Server Basic
Classification
- Weakness
-
- CWE-287 Improper Authentication
References
-
siemens.com
/cert/pool/cert/siemens_security_advisory_ssa-651454.pdf
patch, vendor-advisory
-
securityfocus.com
/bid/102904
vdb-entry, third-party-advisory
-
securityfocus.com
/bid/102897
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2018-4836
- NVD CVE-2018-4836
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.