CVE-2018-18998 json
LCDS Laquis SCADA prior to version 4.1.0.4150 uses hard coded credentials, which may allow an attacker unauthorized access to the system wi…
published 7y ago modified 4mo ago also EUVD-2018-10702
- cvss
- 9.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.4%
- EPSS 2.4% chance of exploitation in 30 days, percentile 83%
- public exploits
- 0
- none known
Summary
LCDS Laquis SCADA prior to version 4.1.0.4150 uses hard coded credentials, which may allow an attacker unauthorized access to the system with high privileges.
Patch / fix
- lcds laquis_scada 4.1.0.4150
Is CVE-2018-18998 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-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.3870affected: 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.38% chance of exploitation in the next 30 days, higher than 83% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 9.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/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
- ICS-CERT LCDS Laquis SCADA
Classification
- Weakness
-
- CWE-798 Use of Hard-coded Credentials
References
-
ics-cert.us-cert.gov
/advisories/ICSA-19-015-01
third-party-advisory, us-government-resource
-
securityfocus.com
/bid/106634
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2018-18998
- NVD CVE-2018-18998
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.