CVE-2023-23901
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 following of a certificate's chain of trust exists in SkyBridge MB-A200 firmware Ver. 01.00.05 and earlier, and SkyBridge BASIC MB-A130 firmware Ver. 1.4.1 and earlier, which may allow a remote unauthenticated attacker to eavesdrop on or alter the communication sent to the WebUI 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 confidenceThe SkyBridge MB-A200 and MB-A130 devices fail to properly validate the certificate chain of trust in their WebUI, allowing attackers to perform man-in-the-middle attacks and intercept or modify encrypted communications.
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<= 1.4.1<= 01.00.05CVSS 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
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/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 device modelCheck the product label on the device or access the WebUI system information page to confirm whether the device is an MB-A130 or MB-A200 model.Affected if The device is a Seiko Sol Skybridge MB-A130 or MB-A200 unit.
-
Check MB-A130 firmware versionAccess the WebUI system status or firmware information page, or log into the device CLI and run the command to display firmware version (typically 'show firmware' or checking /proc/version), then compare the version number to 1.4.1.Affected if The device is an MB-A130 with firmware version 1.4.1 or lower.
-
Check MB-A200 firmware versionAccess the WebUI system status or firmware information page, or log into the device CLI and run the command to display firmware version, then compare the version number to 01.00.05.Affected if The device is an MB-A200 with firmware version 01.00.05 or lower.
-
Confirm WebUI is accessibleVerify that the WebUI interface is enabled and reachable on the network by attempting to access the device's IP address via HTTPS in a browser, or check the network configuration settings.Affected if The WebUI is enabled and accessible over the network (this is the vulnerable component where certificate validation is improper).
You are affected if you have an MB-A130 device on firmware 1.4.1 or lower, or an MB-A200 device on firmware 01.00.05 or lower, and the WebUI is enabled and accessible.
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 dataUpdate firmware to versions newer than 01.00.05 for MB-A200 and newer than 1.4.1 for MB-A130, or avoid accessing the WebUI over untrusted networks until the update can be applied.
- Consultation3.0 h
- Implementation2.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 $2,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-23901 — 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-23901 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