CVE-2018-13816 json
A vulnerability has been identified in TIM 1531 IRC (All version < V2.0).
published 7y ago modified 4mo ago also EUVD-2018-5752
- cvss
- 10.0
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.8%
- EPSS 2.8% chance of exploitation in 30 days, percentile 86%
- public exploits
- 0
- none known
Summary
A vulnerability has been identified in TIM 1531 IRC (All version < V2.0). The devices was missing proper authentication on port 102/tcp, although configured. Successful exploitation requires an attacker to be able to send packets to port 102/tcp of the affected device. No user interaction and no user privileges are required to exploit the vulnerability. At the time of advisory publication no public exploitation of this vulnerability was known.
Patch / fix
- siemens tim_1531_irc_firmware 2.0
Is CVE-2018-13816 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-18-352-05 updated cvss 10.0
Siemens TIM 1531 IRC Modules
-
Siemens TIM 1531 IRC (incl. SIPLUS NET variants) <V2.0affected: fixed in V2.0, mitigation
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.80% chance of exploitation in the next 30 days, higher than 86% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 10.0 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H |
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
Affected products
- Siemens AG TIM 1531 IRC
Classification
References
-
cert-portal.siemens.com
/productcert/pdf/ssa-982399.pdf
vendor-advisory
-
securityfocus.com
/bid/106194
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2018-13816
- NVD CVE-2018-13816
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.