CVE-2018-17899 json
LAquis SCADA Versions 4.1.0.3870 and prior has a path traversal vulnerability, which may allow remote code execution.
published 2018-10-17 8 y ago modified 2026-06-17 4 mo ago also EUVD-2018-9640
- cvss
- 8.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 8.1%
- EPSS 8.1% chance of exploitation in 30 days, percentile 94%
- public exploits
- 0
- none known
Summary
LAquis SCADA Versions 4.1.0.3870 and prior has a path traversal vulnerability, which may allow remote code execution.
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
cisa ICSA-18-289-01 updated cvss 6.3
LCDS - Leão Consultoria e Desenvolvimento de Sistemas Ltda ME LAquis SCADA
-
LCDS - Leão Consultoria e Desenvolvimento de Sistemas LTDA ME Smart Security Manager <= 4.1.0.3870affected: mitigation “LCDS recommends that users update to Version 4.1.0.4114, which can be found at the following location:”
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
8.06% chance of exploitation in the next 30 days, higher than 94% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 8.8 | CVSS:3.0/AV:N/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
- LCDS - Leão Consultoria e Desenvolvimento de Sistemas LTDA ME LAquis SCADA
Classification
- Weakness
-
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory
References
-
laquisscada.com
/instale1.php
product, vendor-advisory
-
securityfocus.com
/bid/105719
vdb-entry, third-party-advisory
-
ics-cert.us-cert.gov
/advisories/ICSA-18-289-01
third-party-advisory, us-government-resource
-
exchange.xforce.ibmcloud.com
/vulnerabilities/151420
third-party-advisory
Sources
- CVE List CVE-2018-17899
- NVD CVE-2018-17899
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.