LiveActive security incident?Get immediate response
CVE Record

CVE-2022-30623: Chcnav - P5E GNSS Authentication bypass

The server checks the user's cookie in a non-standard way, and a value is entered in the cookie value name of the status and its value is set to true to bypass the identification with the system using a username and password.

MediumCVSS 5.9Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2022-30623 is an authentication bypass in CHCNAV P5E GNSS version 4.2. The device can incorrectly trust cookie status data instead of normal username and password authentication. The rated impact is moderate, with limited confidentiality, integrity, and availability effects.

Executive priority

Treat this as a moderate operational security issue. Prioritize if CHCNAV P5E GNSS 4.2 supports field operations, critical surveying, or infrastructure workflows, especially where local access is broadly available.

Technical view

The CVE describes CWE-288 authentication bypass caused by non-standard cookie validation. A cookie status value can satisfy identification checks without valid credentials. The published CVSS 3.1 score is 5.9 with local attack vector and low complexity. Only CHCNAV P5E GNSS 4.2 is listed in the provided sources.

Likely exposure

Exposure appears limited to organizations operating CHCNAV P5E GNSS devices on version 4.2. The CVSS vector indicates local access, so internet-wide exposure is not supported by the provided evidence.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation evidence. The CVE description explains the authentication weakness, but no public exploit status, patch status, or campaign activity is provided.

Researcher notes

Evidence is sparse. The bundle names one affected product/version and describes cookie-based authentication bypass, but provides no CPEs, patch details, exploit telemetry, or detailed advisory text. Avoid broad product assumptions beyond P5E GNSS 4.2.

Mitigation direction

  • Identify CHCNAV P5E GNSS devices and confirm whether version 4.2 is present.
  • Check CHCNAV or government advisory guidance for firmware updates or vendor-approved mitigations.
  • Restrict access to device management paths to trusted operators and controlled networks.
  • Monitor for unexpected authenticated sessions where device logging supports it.

Validation and detection

  • Inventory GNSS assets and record model, firmware, and management exposure.
  • Confirm whether any device matches CHCNAV P5E GNSS version 4.2.
  • Review authentication behavior against vendor guidance without using production-disruptive tests.
  • Check available logs for anomalous session creation or configuration changes.
Prepared
Confidence
medium
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-288: 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-2022-30623 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
Medium
CVSS
5.9 (3.1)
Known Exploited
No
Published

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

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
5.9CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L2.53.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.9Medium
CVSS 3.1 vector shape for CVE-2022-30623Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
ChcnavChcnav - P5E GNSS4.2Listed
Weakness

CWE details

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

CWE-288 · source CWE mapping

Authentication Bypass Using an Alternate Path or Channel

Authentication Bypass Using an Alternate Path or Channel represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.