dbcve.org
CrimsonApplication · Redlion

CVE-2020-27285

CRITICAL · 9.1 CVSS v3.1 Published 2021-01-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
The default configuration of Crimson 3.1 (Build versions prior to 3119.001) allows a user to be able to read and modify the database without authentication.

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 confidence

Crimson 3.1 HMI software versions prior to build 3119.001 have a default configuration that allows unauthenticated users to read and modify the database, enabling potential unauthorized control changes or sensitive data exfiltration.

MitigationUpgrade Crimson 3.1 to build 3119.001 or later, or reconfigure the default settings to require authentication for database access.

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.1

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 checks

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

  1. Identify installed Crimson version and build number
    Open Crimson software, go to Help > About, or check the installed program's version properties. Note both the version (3.1) and the specific build number.
    Affected if Version is 3.1 with build lower than 3119.001 (e.g., 3118.xxx or earlier)
  2. Locate database configuration settings
    In Crimson 3.1, navigate to the database or security settings panel. Look for options controlling database access authentication, typically found under Database > Settings or Security > Authentication.
    Affected if Authentication for database access is set to Disabled, None, or Default (unauthenticated access enabled)
  3. Verify database access control configuration
    Check if the database module allows connections without requiring username/password credentials. This is often indicated by a 'Require Authentication' checkbox that is unchecked in the default state.
    Affected if The database access control is configured to allow unauthenticated connections (authentication is not required)
  4. Confirm default configuration is in use
    Review whether the software was installed with default settings and has not had security configurations explicitly modified. Default installations of Crimson 3.1 prior to build 3119.001 ship with database authentication disabled.
    Affected if Using default configuration with database authentication disabled, and version is 3.1 build prior to 3119.001

You are affected if running Crimson 3.1 with a build number lower than 3119.001 AND the database is configured to allow unauthenticated access (default vulnerable state).

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Crimson 3.1 to build 3119.001 or later, or reconfigure the default settings to require authentication for database access.

Recommended fix High confidence

Crimson 3.1 Build 3119.001 or later

  1. Identify the current installed version of Crimson 3.1 by checking the build number in the application or system information
  2. Verify if the current build version is prior to 3119.001
  3. If the version is prior to 3119.001, obtain the fixed release (build 3119.001 or later) from the vendor's official distribution channels
  4. Apply the upgrade following the vendor's standard upgrade procedure for Crimson 3.1
  5. After upgrade, verify the build number reflects 3119.001 or later
  6. Confirm that authentication is now required for database access by attempting an unauthenticated connection (which should fail)

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Crimson Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,440
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-27285 — 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-2020-27285 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