CVE-2019-10980 json
A type confusion vulnerability may be exploited when LAquis SCADA 4.3.1.71 processes a specially crafted project file.
published 7y ago modified 4mo ago also EUVD-2019-2694
- cvss
- 7.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.0%
- EPSS 1.0% chance of exploitation in 30 days, percentile 63%
- public exploits
- 0
- none known
Summary
A type confusion vulnerability may be exploited when LAquis SCADA 4.3.1.71 processes a specially crafted project file. This may allow an attacker to execute remote code. The attacker must have local access to the system. A CVSS v3 base score of 7.8 has been calculated; the CVSS vector string is (AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H).
Is CVE-2019-10980 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-19-213-06 updated cvss 7.8
LCDS LAquis SCADA LQS File Parsing
-
LCDS Leão Consultoria e Desenvolvimento de Sistemas LTDA ME SCADA 4.3.1.71affected: mitigation “LCDS recommends users update to Version 4.3.1.323” laquisscada.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.00% chance of exploitation in the next 30 days, higher than 63% of all scored CVEs (FIRST EPSS, 2026-11-09).
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
- n/a LCDS LAquis SCADA
Classification
- Weakness
-
- CWE-843 Access of Resource Using Incompatible Type
References
-
us-cert.gov
/ics/advisories/icsa-19-213-06
third-party-advisory, us-government-resource
Sources
- CVE List CVE-2019-10980
- NVD CVE-2019-10980
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.