CVE-2022-30622
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 · uneditedDisclosure of information - the system allows you to view usernames and passwords without permissions, thus it will be possible to enter the system. Path access: http://api/sys_username_passwd.cmd - The server loads the request clearly by default. Disclosure of hard-coded credit information within the JS code sent to the customer within the Login.js file is a strong user (which is not documented) and also the password, which allow for super-user access. Username: chcadmin, Password: chcpassword.
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 confidenceUnauthenticated path access vulnerability allows retrieval of hard-coded administrative credentials (chcadmin/chcpassword) via the /api/sys_username_passwd.cmd endpoint. Additionally, the same credentials are embedded in plain text within the client-side Login.js JavaScript file, enabling unauthorized super-user access to the system.
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<= 4.1= 4.2CVSS 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
- Low
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify firmware versionAccess the device's web interface or administrative panel to locate the firmware version information. This is typically found in System Settings, About, or Status pages.Affected if Firmware version is 4.1 or lower, or exactly version 4.2
-
Test the sys_username_passwd.cmd endpointSend an unauthenticated HTTP GET request to /api/sys_username_passwd.cmd on the device (for example: http://<device-ip>/api/sys_username_passwd.cmd) and inspect the response body.Affected if The endpoint returns hard-coded credentials (specifically chcadmin and chcpassword) without requiring authentication
-
Inspect Login.js for embedded credentialsLocate the Login.js JavaScript file in the web application's client-side files (typically in /js/ or similar directory) and search for plain text string values representing credentials.Affected if The Login.js file contains the hard-coded credentials chcadmin and chcpassword in plain text
-
Verify credential exploitation potentialAttempt to authenticate to the device using the obtained credentials (chcadmin/chcpassword) through the normal login interface.Affected if The credentials grant super-user or administrative access without proper authorization
The environment is affected if the device runs Chcnav P5e Gnss firmware version 4.1 or lower, or exactly version 4.2, and either the /api/sys_username_passwd.cmd endpoint exposes credentials or Login.js contains hard-coded credentials, enabling unauthorized administrative access.
Generated from the published advisory. Verify against your own configuration.
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 dataImmediately remove or restrict access to the /api/sys_username_passwd.cmd endpoint and remove hard-coded credentials from Login.js. Rotate the exposed credentials and implement proper authentication/authorization mechanisms.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-30622 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-30622 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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