Security readout for executives and security teams
Plain-English summary
Red Lion Controls Crimson used a hard-coded password to protect configuration files. If an attacker can obtain or intercept those protected files, confidentiality of configuration data may be lost. The sources rate this as medium severity, with high confidentiality impact but no stated integrity or availability impact.
Executive priority
Prioritize remediation where Crimson configuration files contain sensitive industrial configuration data or move across shared networks. This is not KEV-listed in the provided sources, but loss of configuration confidentiality can still support follow-on targeting.
Technical view
CVE-2019-10990 affects Red Lion Controls Crimson 3.0 and prior, and 3.1 before release 3112.00. It is a CWE-321 hard-coded cryptographic password issue for protected files in transit and at rest. CVSS 3.1 is 6.5: network attack vector, low complexity, no privileges, user interaction required, confidentiality high.
Likely exposure
Exposure is likely limited to organizations using Red Lion Controls Crimson Windows configuration software, especially where protected configuration files are exchanged, stored, or accessible to untrusted users or networks.
Exploitation context
The provided bundle does not show CISA KEV listing or confirmed active exploitation. It does not provide exploit maturity details. Treat risk as confidentiality-focused exposure of configuration files, not as confirmed remote system takeover.
Researcher notes
Evidence supports a hard-coded password weakness affecting file protection, with confidentiality impact only in the CVSS vector. The bundle does not include exploit details, proof of active exploitation, or a detailed vendor workaround beyond the affected version boundary.
Mitigation direction
- Inventory Red Lion Controls Crimson installations and versions.
- Upgrade affected Crimson versions to a vendor-supported non-affected release.
- Treat protected configuration files as sensitive and restrict access.
- Review CISA and Red Lion guidance before deployment changes.
- Limit file transfer paths to trusted systems and users.
Validation and detection
- Confirm whether Crimson 3.0 or 3.1 before 3112.00 is installed.
- Identify where protected Crimson configuration files are stored or transferred.
- Check whether untrusted users can access those files.
- Verify upgrade status against vendor and CISA guidance.
- Review monitoring for unusual access to configuration files.
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.
CWE-321: 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.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2019-10990 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
- Medium
- CVSS
- 6.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
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.
SSVC decision data
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N2.83.6CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
6.5MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://www.us-cert.gov/ics/advisories/icsa-19-248-01CVE reference, icscert · 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.
Use of Hard-coded Cryptographic Key
Use of Hard-coded Cryptographic Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.