CVE-2020-27285: The default configuration of Crimson 3.1 (Build versions prior to 3119.001) allows a user to be able to rea...
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.
Security readout for executives and security teams
Plain-English summary
Crimson 3.1 builds before 3119.001 can allow database reading and modification without authentication in the default configuration. This is not described as system takeover, but unauthorized changes to operational data can create business and reliability risk.
Executive priority
Moderate priority. Accelerate remediation if Crimson is reachable from untrusted networks or supports operational systems where unauthorized database changes could affect safety, reliability, or service delivery.
Technical view
The issue is CWE-306: missing authentication for a database access path in Crimson 3.1. CVSS 3.1 is 6.5: network reachable, low complexity, no privileges, no user interaction, with low confidentiality and integrity impact and no stated availability impact.
Likely exposure
Exposure is most likely in environments running Crimson 3.1 builds earlier than 3119.001, especially where the affected interface is reachable over a network. The sources do not provide deployment prevalence or internet exposure data.
Exploitation context
The bundle does not show CISA KEV status or any cited report of active exploitation. Risk still matters because the vulnerability requires no authentication and can be reached over the network under the stated default configuration.
Researcher notes
Evidence is limited to the CVE description, CVSS vector, affected build range, CWE-306 classification, and CISA ICS advisory reference. The bundle does not include technical exploit details, affected CPEs, or confirmation of active exploitation.
Mitigation direction
Upgrade Crimson 3.1 to build 3119.001 or later.
Review current vendor and CISA guidance before operational rollout.
Restrict network access to Crimson management or database interfaces.
Remove unnecessary external exposure from control-system networks.
Monitor for unexpected database reads or modifications.
Validation and detection
Inventory Crimson 3.1 installations and record build numbers.
Identify systems running builds earlier than 3119.001.
Confirm database access now requires authentication.
Review firewall rules for reachable Crimson services.
Check change records and logs for unauthorized database modifications.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-306: Credential and account abuse lookup
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-306 · source CWE mapping
Missing Authentication for Critical Function
Missing Authentication for Critical Function represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.