CVE-2019-10990
No exploitation reported by the sources we read.
- Published2019-09-23
- Fixed in3112.00
- WeaknessCWE-321 · CWE-798
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
Red Lion Controls Crimson, version 3.0 and prior and version 3.1 prior to 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.
Timeline
dates in UTC- 2019-09-2316:15CVE publishedNVD
Observed activity
isMalicious corpus · updated 2026-10-23 21:37 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2019-10990?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2019-10990?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 3112.0 | ≥ 3.1, < 3112.00 | 3112.00 | NVD |
| 3.0 | ≤ 3.0 | no fix published | NVD |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Distribution builds and vendor advisories
Packages from OSV.dev and products from the vendors' CSAF advisories.
version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.
Vendor advisories
Red Lion Controls Crimson
Crimson: Versions 3.0 and prior · Crimson: Versions 3.1 prior to release 3112.00
Fix
- Update Redlion crimson to 3112.00
- Vendor fix CISA ICSA-19-248-01 · 2 productsRed Lion Controls recommends users migrate to Crimson 3.1 release 3112.00 or later where the model choice allows. Updated software can be found at the following link:
- Vendor fix CISA ICSA-19-248-01 · 2 productsThe use of a hardcoded key vulnerability (CVE-2019-10990) can be mitigated in two ways: 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 secur…
- Mitigation from the vendor CISA ICSA-19-248-01 · 2 productsThe use of a hardcoded key vulnerability (CVE-2019-10990) can be mitigated in two ways: In a later release, targeted for September 2019, Red Lion Controls will modify the existing database protection scheme to include an option for a second file access password designed to encrypt the file.
- Mitigation from the vendor CISA ICSA-19-248-01 · 2 productsFor more information, Red Lion Controls has released a security bulletin that can be found at the following link:
Advisories and patches
- www.us-cert.govMitigation
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- none listed PoC-in-GitHub
Sources
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
- Published
- 2019-09-23
- Last Modified
- 2026-06-17
- NVD status
- Modified
Frequently asked questions
What is CVE-2019-10990?
Is CVE-2019-10990 actively exploited?
What is the CVSS score for CVE-2019-10990?
Running Red Lion Controls Crimson? Hear about its next vulnerability
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.