CVE-2023-35837
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 · uneditedAn issue was discovered in SolaX Pocket WiFi 3 through 3.001.02. Authentication for web interface is completed via an unauthenticated WiFi AP. The administrative password for the web interface has a default password, equal to the registration ID of the device. This same registration ID is used as the WiFi SSID name. No routine is in place to force a change to this password on first use or bring its default state to the attention of the user. Once authenticated, an attacker can reconfigure the device or upload new firmware, both of which can lead to Denial of Service, code execution, or Escalation of Privileges.
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 confidenceThe SolaX Pocket WiFi 3 device uses a default administrative password equal to its registration ID, which is also exposed as the WiFi SSID. Attackers connecting to the unauthenticated WiFi access point can obtain this ID and use it to authenticate with full administrative privileges, allowing firmware uploads or device reconfiguration leading to code execution or denial of service.
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>= 3.0.0, <= 3.009.03_20230504CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 SolaX Pocket WiFi 3 deviceScan for WiFi access points and look for SSIDs matching the pattern 'SolaX_*' or similar naming convention associated with SolaX Pocket WiFi 3 devicesAffected if A WiFi access point with SSID pattern matching SolaX Pocket WiFi 3 is present in the environment
-
Check device firmware versionConnect to the device's web interface (typically via the WiFi AP or LAN connection) and navigate to the device information or settings page to view the firmware versionAffected if The installed firmware version is >= 3.0.0 and <= 3.009.03_20230504
-
Verify default WiFi SSID contains registration IDExamine the WiFi SSID of the SolaX device - the registration ID should be visible as part of or as the full SSIDAffected if The WiFi SSID contains or equals the device registration ID (typically a numeric identifier)
-
Test default administrative credentialAccess the device web administration panel and attempt to log in using the registration ID (from the SSID) as both username and password, or as the password with default admin usernameAffected if Authentication succeeds with the registration ID as the password, indicating the default password has not been changed
-
Confirm WiFi AP is active and accessibleVerify the device is broadcasting its unauthenticated WiFi access point and is accessible without prior authenticationAffected if The device WiFi AP is active and allows connection without any pre-authentication
If a SolaX Pocket WiFi 3 device with firmware between 3.0.0 and 3.009.03_20230504 is found with its default WiFi SSID exposing the registration ID, and the admin password still equals that ID, the environment is affected by this vulnerability.
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 change the default administrative password on all affected devices and restrict physical/network access to the device's WiFi access point. Consider network segmentation to isolate IoT devices.
- Consultation8.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,608.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-35837 — 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-2023-35837 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