dbcve.org
Skybridge Basic Mb A130 FirmwareOperating system · Seiko Sol

CVE-2023-25184

HIGH · 7.5 CVSS v3.1 Published 2023-05-10
Fix available
A fix is available. Upgrade to after 1.4.1 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Use of weak credentials exists in Seiko Solutions SkyBridge and SkySpider series, which may allow a remote unauthenticated attacker to decrypt password for the WebUI of the product. Affected products and versions are as follows: SkyBridge MB-A200 firmware Ver. 01.00.05 and earlier, SkyBridge BASIC MB-A130 firmware Ver. 1.4.1 and earlier, and SkySpider MB-R210 firmware Ver. 1.01.00 and earlier.

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 confidence

This vulnerability in Seiko Solutions SkyBridge and SkySpider series devices allows a remote unauthenticated attacker to decrypt WebUI passwords due to weak credential storage mechanisms. The flaw affects firmware versions prior to updates for all three affected models (MB-A200, MB-A130, MB-R210). An attacker can capture authentication material and decrypt it offline without requiring valid credentials.

MitigationApply vendor-provided firmware updates to all affected devices (MB-A200 to Ver.01.00.06 or later, MB-A130 to Ver.1.4.2 or later, MB-R210 to Ver.1.01.01 or later). Until patched, restrict network access to WebUI interfaces via firewall rules or VPN access controls.

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
Skybridge Basic Mb A130 FirmwareOperating system
Affected:<= 1.4.1
Skybridge Mb A200 FirmwareOperating system
Affected:<= 01.00.05
Skyspider Mb R210 FirmwareOperating system
Affected:<= 1.01.00

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify device model
    Access the device administration interface or check the device label to confirm the exact model number is one of: MB-A200, MB-A130, or MB-R210
    Affected if The model is MB-A200, MB-A130, or MB-R210 and you cannot confirm it has been updated to a patched version
  2. Check MB-A200 firmware version
    Log into the device WebUI or CLI and navigate to System Information or Firmware Version settings. Compare the installed version against <= 01.00.05
    Affected if Firmware version is 01.00.05 or earlier on an MB-A200 device
  3. Check MB-A130 firmware version
    Log into the device WebUI or CLI and navigate to System Information or Firmware Version settings. Compare the installed version against <= 1.4.1
    Affected if Firmware version is 1.4.1 or earlier on an MB-A130 device
  4. Check MB-R210 firmware version
    Log into the device WebUI or CLI and navigate to System Information or Firmware Version settings. Compare the installed version against <= 1.01.00
    Affected if Firmware version is 1.01.00 or earlier on an MB-R210 device
  5. Assess WebUI exposure
    Review network firewall rules or access control lists to determine if the device WebUI interface (typically ports 80/443) is accessible from untrusted networks or the internet
    Affected if The WebUI is directly accessible from untrusted networks without VPN or additional authentication controls

You are affected if you operate any MB-A200, MB-A130, or MB-R210 device running firmware at or below the affected version thresholds, and the WebUI is network-accessible to potential attackers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 1.4.1
Interim mitigation

Apply vendor-provided firmware updates to all affected devices (MB-A200 to Ver.01.00.06 or later, MB-A130 to Ver.1.4.2 or later, MB-R210 to Ver.1.01.01 or later). Until patched, restrict network access to WebUI interfaces via firewall rules or VPN access controls.

Fix this in Skybridge Basic Mb A130 Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-25184 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-25184 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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