LiveActive security incident?Get immediate response
CVE Record

CVE-2020-7378: CRIXP OpenCRX Unverified Password Change

CRIXP OpenCRX version 4.30 and 5.0-20200717 and prior suffers from an unverified password change vulnerability. An attacker who is able to connect to the affected OpenCRX instance can change the password of any user, including admin-Standard, to any chosen value. This issue was resolved in version 5.0-20200904, released September 4, 2020.

CriticalCVSS 9.1Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

This flaw lets someone who can reach an affected OpenCRX system change any user's password, including the standard admin account. That can lead to account takeover and access to sensitive business data. The source bundle says the issue was fixed in OpenCRX 5.0-20200904.

Executive priority

Prioritize urgently if OpenCRX is deployed and reachable. The business risk is privileged account takeover without credentials, which can undermine confidentiality and integrity. If OpenCRX is not used, or all instances are already fixed and access-controlled, residual priority drops.

Technical view

CVE-2020-7378 is an unverified password change vulnerability in CRIXP OpenCRX 4.30, 5.0-20200717, and prior. The CVSS 3.1 score is 9.1 with network attack vector, low complexity, no privileges, and no user interaction. The weakness is mapped to CWE-620.

Likely exposure

Exposure is likely limited to organizations running affected OpenCRX versions reachable by untrusted users or networks. Internet-facing or broadly accessible instances have the highest concern. The provided sources do not name additional affected products.

Exploitation context

The provided bundle does not show CISA KEV listing or active exploitation evidence. However, the vulnerability requires no authentication and can change privileged passwords if the affected instance is reachable.

Researcher notes

Evidence supports a critical unauthenticated password-change issue in specific OpenCRX versions, fixed September 4, 2020. Avoid assuming exploit activity from severity alone. Focus validation on version confirmation, exposure path, and account-change telemetry.

Mitigation direction

  • Upgrade affected OpenCRX deployments to version 5.0-20200904 or later.
  • Restrict network access to OpenCRX until remediation is complete.
  • Review accounts for unexpected password changes, especially admin-Standard.
  • Check vendor guidance for supported upgrade and hardening details.

Validation and detection

  • Inventory OpenCRX deployments and record exact versions or build dates.
  • Identify any 4.30, 5.0-20200717, or earlier deployments.
  • Confirm remediated systems run 5.0-20200904 or later.
  • Check whether OpenCRX is reachable from untrusted networks.
  • Review authentication and account-change logs for suspicious password resets.
Prepared
Confidence
high
Sources
3

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 · low confidence lookup

CWE-620: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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.

Open ATT&CK lookup
description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2020-7378 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.1 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

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.

ScoreVersionSeverityVectorExploitImpactSource
9.1CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N3.95.2Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.1Critical
CVSS 3.1 vector shape for CVE-2020-7378Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
CRIXPOpenCRX4.30, 5.0-20200717Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-620 · source CWE mapping

Unverified Password Change

Unverified Password Change represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.