CVE-2019-10996: 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 can reference memory after it has been freed.
Security readout for executives and security teams
Plain-English summary
This issue affects Red Lion Controls Crimson, a Windows configuration tool used around industrial systems. A legitimate user opening a malicious input file can trigger memory misuse that may compromise the workstation. Business risk is highest where engineers exchange Crimson files with vendors, integrators, or untrusted sources.
Executive priority
Prioritize remediation for engineering workstations that manage industrial configurations or receive files from outside parties. This is high severity because successful exploitation can affect confidentiality, integrity, and availability, but urgency is moderated by the need for user interaction and lack of sourced active-exploitation evidence.
Technical view
CVE-2019-10996 is a CWE-416 use-after-free flaw in Crimson 3.0 and prior, and 3.1 before release 3112.00. CVSS 3.1 is 7.8: local attack vector, low complexity, no privileges, user interaction required, and high confidentiality, integrity, and availability impact.
Likely exposure
Exposure is limited to organizations running affected Crimson Windows configuration software and opening project or input files. Internet exposure is not indicated by the CVSS vector; the realistic path is a malicious file delivered to an authorized user.
Exploitation context
The provided bundle does not show CISA KEV listing or active exploitation evidence. Exploitation requires user interaction: a valid user must open a specially crafted malicious file. Treat this as a workstation and engineering-operations risk, not a remotely reachable service flaw.
Researcher notes
The key exposure condition is file parsing in affected Crimson releases, not network reachability. Validate version boundaries carefully: 3.0 and prior are affected, and 3.1 is affected before release 3112.00. The bundle gives no safe exploit proof, exploit prevalence, or detailed vendor fix procedure beyond the version boundary.
Mitigation direction
Identify all installations of Crimson and record exact release versions.
Upgrade away from Crimson 3.0 and 3.1 releases before 3112.00 per vendor guidance.
Restrict opening Crimson files from unknown, unsolicited, or untrusted sources.
Use endpoint controls on engineering workstations that handle industrial configuration files.
Check the CISA advisory and vendor guidance for any additional mitigations.
Validation and detection
Inventory engineering workstations for installed Crimson versions.
Confirm no systems run Crimson 3.0 or 3.1 before release 3112.00.
Review recent file-handling events for unexpected Crimson project or input files.
Verify users handling Crimson files received guidance on trusted-file handling.
Document compensating controls where upgrades are delayed.
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-416: 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.
1CVSS vectors
3Timeline events
2ADP providers
2Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
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-416 · source CWE mapping
Use After Free
Use After Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.