CVE-2019-10924 json
A vulnerability has been identified in LOGO!
published 2019-05-14 7 y ago modified 2026-06-17 4 mo ago also EUVD-2019-2638
- cvss
- 7.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.3%
- EPSS 1.3% chance of exploitation in 30 days, percentile 70%
- public exploits
- 0
- none known
Summary
A vulnerability has been identified in LOGO! Soft Comfort (All versions < V8.3). The vulnerability could allow an attacker to execute arbitrary code if the attacker tricks a legitimate user to open a manipulated project. In order to exploit the vulnerability, a valid user must open a manipulated project file. No further privileges are required on the target system. The vulnerability could compromise the confidentiality, integrity and availability of the engineering station. At the time of advisory publication no public exploitation of this security vulnerability was known.
Patch / fix
- siemens logo!_soft_comfort 8.3
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
cisa ICSA-19-134-03 updated cvss 7.8
Siemens LOGO! Soft Comfort (Update A)
-
Siemens LOGO! Soft Comfort <V8.3affected: vendor fix, 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
1.27% chance of exploitation in the next 30 days, higher than 70% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
Affected products
- Siemens LOGO! Soft Comfort
Classification
- Weakness
-
- CWE-502 Deserialization of Untrusted Data
References
-
cert-portal.siemens.com
/productcert/pdf/ssa-102144.pdf
vendor-advisory
-
securityfocus.com
/bid/108368
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2019-10924
- NVD CVE-2019-10924
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.