CVE-2022-33948
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 · uneditedHOME SPOT CUBE2 V102 contains an OS command injection vulnerability due to improper processing of data received from DHCP server. An adjacent attacker may execute an arbitrary OS command on the product if a malicious DHCP server is placed on the WAN side of the product.
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 HOME SPOT CUBE2 V102 router contains an OS command injection vulnerability in its DHCP client processing. When the device receives DHCP responses from the WAN interface, data is improperly handled and passed to system commands without adequate sanitization, allowing an adjacent attacker with a malicious DHCP server to inject and execute arbitrary OS commands.
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<= v102CVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/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.
-
Confirm router modelIdentify the exact router hardware model. Look for 'HOME SPOT CUBE2' or 'Home Spot Cube 2' labeling on the device or in its management interface under Device Information or Status pages.Affected if The device is not a HOME SPOT CUBE2 router from Kddi.
-
Check firmware versionAccess the router web administration interface and navigate to the firmware or software version information page, typically found under System, Administration, or Status. Record the firmware version number displayed.Affected if The firmware version is v102 or lower.
-
Verify WAN DHCP client is enabledIn the router web interface, locate the WAN or Internet connection settings. Confirm that the WAN interface is configured to obtain an IP address automatically via DHCP from the ISP.Affected if The WAN interface uses DHCP client mode and is actively connected.
-
Assess network exposureDetermine whether the WAN port is directly exposed to an untrusted or shared network segment where a rogue DHCP server could be introduced. Check if the router is deployed in an environment with controlled network access.Affected if The WAN segment is not isolated or controlled, allowing potential rogue DHCP servers.
A defender is affected only if they are running a HOME SPOT CUBE2 router with firmware version v102 or lower AND the WAN interface is connected to a network where an adjacent attacker could deploy a malicious DHCP server.
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 dataIsolate the WAN segment to prevent unauthorized DHCP servers; implement DHCP snooping on upstream switches to block rogue DHCP servers; apply vendor firmware patches when available.
- Consultation3.0 h
- Implementation6.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-33948 — 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-33948 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