CVE-2019-10996
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, 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.
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 · high confidenceRed Lion Controls Crimson software versions 3.0 and prior, and 3.1 prior to build 3112.00, contains a use-after-free vulnerability triggered when a valid user opens a specially crafted malicious input file. The crafted file can reference memory after it has been freed, leading to potential code execution or system compromise.
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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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.
-
Locate Red Lion Crimson installationSearch for Crimson software on the system: check Program Files directories, look for 'Crimson' in installed programs list, or search for crimson.exe. On Windows, also check Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for Crimson entries.Affected if Crimson software is found installed on the system
-
Identify installed version and build numberRight-click on the Crimson executable (typically crimson.exe) and select Properties, then view the Details tab for version information. Alternatively, launch Crimson and check Help > About to display the exact build version (format: x.xx.xxxx.xx where the last four digits represent the build).Affected if Version displayed is 3.0 or lower, or version shows 3.1 with build number less than 3112.00
-
Compare against vulnerable version rangeThe vulnerable range is: any version <= 3.0, or version 3.1 with build < 3112.00. If version is 3.1 build 3112.00 or later, the vulnerability is patched. Document the exact version string found in the previous step.Affected if Installed version falls within <= 3.0 or 3.1 < build 3112.00, indicating the vulnerability is present
-
Assess file handling exposureDetermine if users of this system open input files (.cd3, .cd3x, or other Crimson project/data files) from external or untrusted sources. The vulnerability triggers specifically when processing a specially crafted malicious input file.Affected if Users routinely open Crimson input files from untrusted or external sources, making the attack vector viable
System is affected if Red Lion Crimson version is 3.0 or prior, or 3.1 with build lower than 3112.00, and users open input files from potentially untrusted sources.
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
Apply vendor patch by updating Crimson software to version 3.1 build 3112.00 or later, and exercise caution when opening input files from untrusted sources.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10996 — 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-10996 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