CVE-2023-22361
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 · uneditedImproper privilege management vulnerability in SkyBridge MB-A100/110 firmware Ver. 4.2.0 and earlier allows a remote authenticated attacker to alter a WebUI password 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 · moderate confidenceImproper privilege management vulnerability in SkyBridge MB-A100/110 firmware allows a remote authenticated attacker to alter WebUI passwords. This indicates a broken access control where the system fails to properly validate authorization when password change requests are made, potentially enabling privilege escalation or account takeover.
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.2.0<= 4.2.0CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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.
-
Identify the installed firmware versionAccess the device administrative interface or check system information pages to locate the firmware version number. On the SkyBridge MB-A100/110, this is typically found in the WebUI under System > Status or System > Firmware Upgrade. Alternatively, check the boot log or device label for the firmware build version.Affected if The displayed firmware version is 4.2.0 or any earlier version number.
-
Confirm the device model matches affected variantsVerify that the device is specifically a Seiko Sol SkyBridge MB-A100 or MB-A110 model by checking the device label, WebUI header, or boot splash screen.Affected if The device model is an MB-A100 or MB-A110 unit.
-
Determine WebUI accessibility scopeReview network configuration to determine if the WebUI administrative interface is reachable from untrusted network segments. Check firewall rules, NAT configurations, or port forwarding settings that expose HTTP/HTTPS ports (typically 80/443) to the internet or untrusted LAN zones.Affected if The WebUI is accessible from outside the trusted administrative network or from IP addresses not under your direct administrative control.
-
Review authentication mechanismInspect the WebUI login mechanism to determine if it relies solely on local account credentials without additional factor authentication, certificate-based auth, or IP whitelisting enforcement.Affected if The WebUI accepts standard password-based authentication without additional access controls.
You are affected if your SkyBridge MB-A100 or MB-A110 runs firmware version 4.2.0 or lower AND has the WebUI accessible to untrusted users or networks.
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 dataUpgrade to firmware version beyond 4.2.0 when available from vendor. Until then, restrict administrative access to the WebUI to trusted IP addresses only and monitor for unauthorized password changes.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.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,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-22361 — 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-22361 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