CVE-2019-10990
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedRed 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceRed Lion Controls Crimson software uses a hard-coded password to encrypt protected configuration files both in transit and at rest. Since this password is static and discoverable, any attacker who obtains the password can decrypt and access sensitive configuration data, potentially revealing credentials, network settings, or system logic.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 3.0>= 3.1, < 3112.00CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm Crimson software is installedCheck the system for Red Lion Crimson installation by looking in standard program directories (Program Files, Program Files x86) or the Windows registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for an entry named 'Crimson' or similar.Affected if Crimson software is present on the system
-
Identify the installed Crimson versionOpen the Crimson application and navigate to Help > About, or right-click the crimson.exe file in the installation directory and select Properties > Details to view the File Version.Affected if The version displayed cannot be determined or shows a version number
-
Compare version against affected rangesIf the version is identified, compare it against the vulnerable ranges: any version 3.0 or lower, or any version 3.1.x where x is less than 112 (3112.00 is the fixed release).Affected if The installed version is 3.0 or lower, OR the installed version starts with 3.1 but is below 3112.00 (for example, 3.1.0.0 through 3.1.1.1 would be affected)
-
Verify if protected configuration files existLocate any .crd or other configuration files created by Crimson that may contain encrypted sensitive data. These are typically stored in the Crimson project directory or user documents folder.Affected if Encrypted configuration files exist that were created by a vulnerable version
The system is affected if Crimson software is installed and the version is 3.0 or any release of 3.1 prior to version 3112.00, as these versions contain the hardcoded password used to encrypt configuration files.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data3112.00
Update Crimson to version 3.1 release 3112.00 or later, which presumably removes the hardcoded password. Review all systems where the software was deployed and consider rotating any credentials that may have been exposed through decrypted configuration files.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10990 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-10990 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data