dbcve.org
CrimsonApplication · Redlion

CVE-2019-10984

HIGH · 7.8 CVSS v3.1 Published 2019-09-23
Fix available
A fix is available. Upgrade to 3112.00 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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 · unedited
Red 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 causes the program to mishandle pointers.

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 confidence

Red Lion Controls Crimson software versions 3.0 and prior, and 3.1 prior to build 3112.00, contains a pointer mishandling vulnerability triggered when a user opens a specially crafted malicious input file. The vulnerability allows memory corruption which could potentially lead to arbitrary code execution or denial of service.

MitigationUpgrade Crimson to version 3.1 build 3112.00 or later. Avoid opening untrusted or suspicious input files, and implement file type validation before processing.

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
CrimsonApplication
Affected:<= 3.0>= 3.1, < 3112.00

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Crimson version
    Open Crimson software and navigate to Help > About, or check the installed program version through Windows Control Panel > Programs and Features
    Affected if Version displayed is 3.0 or earlier, or version shows 3.1 but build number is below 3112.00
  2. Confirm build number for version 3.1
    In the About dialog or version details, locate the build number (often shown as build #### or similar). For version 3.1, verify if the build is 3112.00 or higher
    Affected if Running Crimson 3.1 with build number less than 3112.00
  3. Compare against affected version range
    Cross-reference your identified version and build number with the affected ranges: version 3.0 and any 3.1 version prior to build 3112.00
    Affected if Installed version is 3.0 (any build) or 3.1 with build lower than 3112.00

You are affected if running Crimson version 3.0 or earlier, or version 3.1 with a build number lower than 3112.00.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to 3112.00 or later
Fixed in 3112.00
Interim mitigation

Upgrade Crimson to version 3.1 build 3112.00 or later. Avoid opening untrusted or suspicious input files, and implement file type validation before processing.

Fix this in Crimson Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-10984 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-10984 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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