CVE-2019-10978: Red Lion Controls Crimson, version 3.0 and prior and version 3.1 prior to release 3112.00, allow multiple v...
Red Lion Controls Crimson, version 3.0 and prior and version 3.1 prior to release 3112.00, allow multiple vulnerabilities to be exploited when a valid user opens a specially crafted, malicious input file that operates outside of the designated memory area.
Security readout for executives and security teams
Plain-English summary
This affects Red Lion Controls Crimson Windows configuration software. A user must open a maliciously crafted file, after which the software may read outside intended memory. Business urgency is low unless staff routinely handle Crimson files from outside trusted engineering workflows.
Executive priority
Treat as a low-priority hygiene item unless Crimson files are exchanged with external parties. The main business risk is compromise of engineering workstations through malicious file handling, not direct remote compromise of field devices.
Technical view
CWE-119 memory-boundary vulnerabilities affect Crimson 3.0 and earlier, and Crimson 3.1 before release 3112.00. The CVSS 3.1 score is 3.3: local attack vector, low complexity, user interaction required, and low confidentiality impact only.
Likely exposure
Exposure is limited to organizations with Red Lion Controls Crimson installed, especially engineering or OT support workstations that open project or configuration files from email, vendors, contractors, or removable media.
Exploitation context
The provided sources do not report active exploitation, and the CVE is not listed as KEV. Exploitation requires a valid user to open a specially crafted malicious input file locally.
Researcher notes
Evidence is limited to the CVE data and CISA ICS advisory reference. The vulnerability class is memory access outside the designated area during malicious file parsing. Sources do not provide exploit details, active exploitation evidence, or broad operational impact claims.
Mitigation direction
Update Crimson 3.1 to release 3112.00 or later where vendor guidance confirms applicability.
Retire or upgrade Crimson 3.0 and earlier installations.
Restrict Crimson file intake to trusted engineering channels.
Warn users not to open unexpected Crimson project or configuration files.
Check the CISA advisory and vendor guidance for current remediation details.
Validation and detection
Inventory endpoints for installed Red Lion Controls Crimson versions.
Confirm whether any installation is 3.0 or earlier, or 3.1 before 3112.00.
Review OT engineering workflows for externally supplied Crimson files.
Verify users handling Crimson files have file-source validation procedures.
Document exceptions where upgrade is not immediately possible.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
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.
cwe · low confidence lookup
CWE-119: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
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.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-119 · source CWE mapping
Improper Restriction of Operations within the Bounds of a Memory Buffer
Improper Restriction of Operations within the Bounds of a Memory Buffer represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.