WellinTech KingSCADA up to 3.7.0.0.0 AlarmServer AEserver.exe Crafted Packet memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.1 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in WellinTech KingSCADA up to 3.7.0.0.0. Impacted is an unknown function of the file AEserver.exe of the component AlarmServer. This manipulation as part of Crafted Packet causes memory corruption. This vulnerability appears as CVE-2018-20410. The attack may be initiated remotely. There is no available exploit. It is advisable to upgrade the affected component.
Details
A vulnerability has been found in WellinTech KingSCADA up to 3.7.0.0.0 (SCADA Software) and classified as critical. Affected by this vulnerability is an unknown functionality of the file AEserver.exe of the component AlarmServer. The manipulation as part of a Crafted Packet leads to a memory corruption vulnerability. The CWE definition for the vulnerability is CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
WellinTech KingSCADA before 3.7.0.0.1 contains a stack-based buffer overflow. The vulnerability is triggered when sending a specially crafted packet to the AlarmServer (AEserver.exe) service listening on TCP port 12401.
The bug was discovered 12/19/2018. The weakness was presented 12/24/2018 (Website). The advisory is shared at github.com. This vulnerability is known as CVE-2018-20410 since 12/23/2018. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are known, but no exploit is available.
The vulnerability was handled as a non-public zero-day exploit for at least 4 days. During that time the estimated underground price was around $0-$5k.
Upgrading to version 3.7.0.0.1 eliminates this vulnerability.Proper firewalling of tcp/12401 is able to address this issue. The best possible mitigation is suggested to be upgrading to the latest version.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.4VulDB Meta Temp Score: 7.2
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Memory corruptionCWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: KingSCADA 3.7.0.0.1
Firewalling: 🔍
Timeline
12/19/2018 🔍12/23/2018 🔍
12/23/2018 🔍
12/24/2018 🔍
12/24/2018 🔍
04/23/2020 🔍
Sources
Advisory: github.comStatus: Not defined
CVE: CVE-2018-20410 (🔍)
GCVE (CVE): GCVE-0-2018-20410
GCVE (VulDB): GCVE-100-128353
Entry
Created: 12/24/2018 09:56Updated: 04/23/2020 18:24
Changes: 12/24/2018 09:56 (62), 04/23/2020 18:24 (1)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.