CVE-2019-10990 is a hard-coded key in Red Lion Crimson, the Windows software used to program Red Lion HMIs and gateways. Crimson's file protection encrypts project files with a password built into the software, so anyone holding a protected file can decrypt it, including stored user passwords. NVD scores it 6.5. Crimson 3.0 and earlier and 3.1 before release 3112.00 are affected; Red Lion's answer in 3112.00 is mainly a manual warning.
Vulnerability summary
CVSS base score
6.5
Medium severity
EPSS score (FIRST)
1.3%
Probability of exploitation in the wild in the next 30 days
CISA KEV catalog
No
Not listed
Published
Vulnerability ID: CVE-2019-10990 · Source: NVD
Affected components
| Component | CPE | Version range |
|---|---|---|
| Red Lion Crimson (Windows configuration software) | cpe:2.3:a:redlion:crimson:*:*:*:*:*:*:*:* | Crimson 3.0 and earlier, and Crimson 3.1 before release 3112.00 (CISA ICSA-19-248-01; NVD CPE: up to and including 3.0, and from 3.1 up to but excluding 3112.00); mitigation: Crimson 3.1 release 3112.00 or later, whose manual states that database protection is not cryptographically secure |
What does this mean for affected devices?
NVD carries the CISA-assigned description: Crimson 3.0 and earlier and Crimson 3.1 before release 3112.00 "uses a hard-coded password to encrypt protected files in transit and at rest, which may allow an attacker to access configuration files." The ICS-CERT CNA classes it CWE-321 (use of hard-coded cryptographic key); NVD's own analysis says CWE-798 (use of hard-coded credentials). The record was published on 2019-09-23 (NVD, CVE record).
How severe is it, and who scored it?
NVD's Primary score is CVSS v3.1 6.5 (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N), with a CVSS v2 score of 4.3. CISA's ICSA-19-248-01 CSAF file gives the same 6.5 vector as CVSS v3.0, and CISA's ADP entry on NVD repeats it. The impact is confidentiality only: anyone who obtains a protected Crimson file can read what the protection was meant to hide.
What is the hard-coded key?
Crimson offers a database protection mechanism for its files. Trend Micro's Zero Day Initiative reported to Red Lion on 2019-02-28 that this protection rests on a secret built into the software. ZDI-19-785 says the flaw "exists within the CTextStreamMemory class", which "contains hard-coded secrets in clear text", and that an attacker "can leverage this to decrypt user passwords". Because every Crimson installation shares the secret, a protected file copied from a workstation, a file share, a USB stick or the network gives up its contents and its stored passwords to anyone who extracts the secret once. ZDI rates the issue 6.5 and says authentication is not required.
Which products are affected, and is there a fix?
| Product | Affected | Fix |
|---|---|---|
| Red Lion Crimson 3.0 | 3.0 and earlier | Migrate to Crimson 3.1 release 3112.00 or later where the device model allows |
| Red Lion Crimson 3.1 | Before release 3112.00 | Crimson 3.1 release 3112.00 or later |
For this CVE the fix is partly documentation. CISA's advisory gives two mitigations. First, the user manual for Crimson 3.1 release 3112.00 "now includes a paragraph describing the intended use of the database protection mechanism, noting the software is not designed to provide a cryptographically secure method of database protection." Second, Red Lion said it would modify the database protection scheme in a later release, targeted for September 2019, to add an option for a second file access password designed to encrypt the file. CISA's advisory does not name the release that carries that option, so check the release notes of the Crimson version you run before relying on it.
How do you mitigate it?
Treat Crimson project files as sensitive data whatever protection is set on them. Keep them in an access-controlled repository, do not send them by email or leave them on shared drives, and assume that any password stored in a file that has left your control is known. Change device and user passwords that were stored in project files exposed before the update. Install Crimson 3.1 release 3112.00 or later, which also fixes the three file-parsing flaws in the same advisory. CISA reported no known public exploits specifically targeting these vulnerabilities.
ICSA-19-248-01 also covers CVE-2019-10996, CVE-2019-10978 and CVE-2019-10984, all triggered by a malicious file. Our Red Lion Sixnet, N-Tron and Crimson guide lists the other Crimson credential issues, and the hard-coded credentials fix guide covers the class. Related advisories: CVE-2020-27285 (Crimson 3.1 database readable without authentication), CVE-2023-5719 (Crimson 3.2 password truncation) and CVE-2016-9335 (hard-coded keys in Sixnet-Managed switches).
CVE-2019-10990 is not in the CISA KEV catalog as of 2026-11-22 (catalog version 2026.11.20, 1,790 entries). FIRST EPSS gives it 0.01336, the 71.9th percentile, in the 2026-11-21 dataset (CISA KEV, FIRST EPSS).
Evidence
- NVD (read 2026-11-22): status Modified, published 2019-09-23, last modified 2026-06-17; NVD Primary CVSS v3.1 6.5 AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N and CVSS v2 4.3; CISA ADP Secondary CVSS v3.1 6.5; NVD Primary CWE-798, ICS-CERT Secondary CWE-321; vulnerable CPE redlion crimson up to and including 3.0, and from 3.1 up to but excluding 3112.00. — NVD
- CVE record (checked 2026-11-22): state PUBLISHED, CNA icscert, published 2019-09-23; CWE-321; product Red Lion Controls Crimson (Windows configuration software), version 3.0 and prior, version 3.1 prior to release 3112.00; no CNA CVSS score. — CVE.org
- CISA CSAF ICSA-19-248-01 Red Lion Controls Crimson (2019-09-05), read 2026-11-22: reported by Michael DePlante, Anthony Fuller and Todd Manning of Trend Micro's Zero Day Initiative; known affected Crimson <= 3.0 and Crimson 3.1 before release 3112.00; fix: migrate to Crimson 3.1 release 3112.00 or later where the model choice allows; Red Lion security bulletin support.redlion.net article 360033077531; no known public exploits specifically target these vulnerabilities; CISA advises users to avoid social engineering (do not open untrusted attachments). CVE-2019-10990: CWE-321, CVSS v3.0 6.5; mitigations: the Crimson 3.1 release 3112.00 user manual describes the intended use of the database protection mechanism and notes it is not designed to provide cryptographically secure database protection; in a later release, targeted for September 2019, Red Lion will modify the database protection scheme to include an option for a second file access password designed to encrypt the file. — CISA CSAF ICSA-19-248-01
- ZDI-19-785 (2019-09-05, updated 2021-06-29, read 2026-11-22): CVE-2019-10990, CVSS 6.5 AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N; flaw within the CTextStreamMemory class, which contains hard-coded secrets in clear text; an attacker can leverage this to decrypt user passwords; authentication not required; reported to vendor 2019-02-28. — Zero Day Initiative
- Not in the CISA KEV catalog, version 2026.11.20 (1,790 entries), checked 2026-11-22. — CISA KEV
- EPSS 0.01336, percentile 0.71936, dataset 2026-11-21, read 2026-11-22. — FIRST EPSS

Related advisories
Sources
Frequently asked questions
Does Crimson 3.1 release 3112.00 fix CVE-2019-10990?
Only partly. CISA says the 3112.00 manual now explains that Crimson's database protection is not designed to be cryptographically secure. Red Lion also said a later release, targeted for September 2019, would add an optional second file access password that encrypts the file; check your version's release notes for it.
What can an attacker get from a protected Crimson file?
CISA says configuration files can be accessed, and ZDI-19-785 says the hard-coded secret in the CTextStreamMemory class lets an attacker decrypt user passwords. Treat any password stored in an exposed project file as known and change it.
How should Crimson project files be handled?
As sensitive data. Keep them in an access-controlled repository, avoid email and open file shares, and limit who can copy them to removable media. The file protection setting alone does not keep the contents confidential.
Is CVE-2019-10990 exploited in the wild?
It is not in the CISA KEV catalog as of 2026-11-22 (catalog version 2026.11.20, 1,790 entries), and CISA reported no known public exploits specifically targeting it. FIRST EPSS gives it 0.01336 (71.9th percentile) in the 2026-11-21 dataset.
Questions about this page?