Skip to content
Fencer Intel
high 7.8

CVE-2018-19029 json

LCDS Laquis SCADA prior to version 4.1.0.4150 allows an attacker using a specially crafted project file to supply a pointer for a controlle…

published 7y ago modified 4mo ago also EUVD-2018-10747

cvss
7.8
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.7%
EPSS 2.7% chance of exploitation in 30 days, percentile 85%
public exploits
0
none known

Summary

LCDS Laquis SCADA prior to version 4.1.0.4150 allows an attacker using a specially crafted project file to supply a pointer for a controlled memory address, which may allow remote code execution, data exfiltration, or cause a system crash.

Patch / fix

  • lcds laquis_scada 4.1.0.4150

Is CVE-2018-19029 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 Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

cisa ICSA-19-015-01 updated cvss 7.3

LCDS - Leão Consultoria e Desenvolvimento de Sistemas Ltda ME LAquis SCADA

  • LCDS - Leão Consultoria e Desenvolvimento de Sistemas Ltda ME SCADA 4.1.0.3870
    affected: mitigation “LCDS recommends users update to Version 4.1.0.4150” 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

2.67% chance of exploitation in the next 30 days, higher than 85% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.0 7.8 CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD 2.0 8.3 AV:N/AC:M/Au:N/C:P/I:P/A:C

Affected products

  • LCDS LCDS Laquis SCADA

Classification

Weakness
  • CWE-822 Untrusted Pointer Dereference
  • CWE-476 NULL Pointer Dereference

References

Sources

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.