Security readout for executives and security teams
Plain-English summary
KingSCADA before 3.7.0.0.1 has a memory corruption flaw in its alarm service. A specially crafted network packet can trigger a stack-based buffer overflow in AEserver.exe on TCP port 12401. The sources do not show active exploitation, but public proof-of-concept material exists.
Executive priority
Prioritize if KingSCADA supports production, safety, or industrial operations. The main urgency is reducing network reachability and confirming upgrade status, not responding to confirmed active exploitation.
Technical view
CVE-2018-20410 affects WellinTech KingSCADA versions before 3.7.0.0.1. The vulnerable component is AlarmServer, AEserver.exe, listening on TCP 12401. The record describes a stack-based buffer overflow triggered by crafted traffic. No CVSS, CWE, CPE, or vendor remediation details are provided in the bundle.
Likely exposure
Exposure is likely limited to environments running KingSCADA before 3.7.0.0.1, especially where AEserver.exe is reachable on TCP 12401. Internet-facing or broadly reachable SCADA networks would carry higher business risk.
Exploitation context
The CVE is not listed as CISA KEV in the provided bundle. Public GitHub references include proof-of-concept and debugging material, but the bundle does not prove real-world active exploitation.
Researcher notes
The public record is sparse: no CVSS vector, CPE, CWE, or vendor advisory is included. Analysis should remain bounded to KingSCADA before 3.7.0.0.1 and AlarmServer AEserver.exe on TCP 12401.
Mitigation direction
- Inventory KingSCADA installations and identify versions before 3.7.0.0.1.
- Check WellinTech guidance for upgrade or remediation details.
- Restrict TCP 12401 to trusted SCADA network segments only.
- Remove any internet exposure for AEserver.exe.
- Monitor AEserver.exe crashes or unexpected restarts.
Validation and detection
- Confirm whether KingSCADA is deployed in the environment.
- Verify product version on each KingSCADA host.
- Check whether AEserver.exe is running and listening on TCP 12401.
- Review firewall rules and asset exposure for TCP 12401.
- Look for historical crashes or anomalous alarm service behavior.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2018-20410 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/flypuma/vul/blob/master/kingview/copy_argumengt_overflow/poc.pyCVE reference · x_refsource_MISC
- https://github.com/flypuma/vul/blob/master/kingview/copy_argumengt_overflow/Debugging.mdCVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.