CVE-2022-30626
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 · uneditedBrowsing the path: http://ip/wifi_ap_pata_get.cmd, will show in the name of the existing access point on the component, and a password in clear text.
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 confidenceThis is an information disclosure vulnerability in embedded network devices (likely IP cameras or similar) where accessing the unauthenticated endpoint /wifi_ap_pata_get.cmd returns the WiFi access point SSID and password in clear text. An attacker can remotely obtain wireless network credentials without any authentication.
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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm device modelIdentify if the target device is a Chcnav P5e Gnss unit by checking the device label, web interface, or SNMP inventoryAffected if Device is not a Chcnav P5e Gnss - not affected by this CVE
-
Check firmware versionAccess the device admin panel or use firmware extraction methods to determine the installed firmware versionAffected if Firmware version is 4.1 or 4.2 - potentially affected; other versions are not in scope
-
Test unauthenticated endpoint accessSend an HTTP GET request to http://<device_ip>/wifi_ap_pata_get.cmd without providing any authentication credentialsAffected if Endpoint responds with HTTP 200 and returns data - vulnerable endpoint is exposed
-
Verify credential disclosureExamine the response body from the /wifi_ap_pata_get.cmd endpoint for fields containing WiFi SSID and password in clear text (not hashed or masked)Affected if Response contains plaintext WiFi network name and password - CONFIRMS the vulnerability is present
A device is affected if it is a Chcnav P5e Gnss with firmware version 4.1 or 4.2 and the unauthenticated /wifi_ap_pata_get.cmd endpoint returns WiFi SSID and password in clear text.
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 dataRestrict access to the /wifi_ap_pata_get.cmd endpoint by implementing proper authentication and authorization checks. Alternatively, disable or remove this debugging/management endpoint from production firmware.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-30626 — 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-30626 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