dbcve.org
Skybridge Mb A100 FirmwareOperating system · Seiko Sol

CVE-2022-36556

CRITICAL · 9.8 CVSS v3.1 Published 2022-08-29
Fix available
A fix is available. Upgrade to after 4.2.0 or later.
See remediation →
100/100
Remediation priority · Urgent
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
Seiko SkyBridge MB-A100/A110 v4.2.0 and below was discovered to contain a command injection vulnerability via the ipAddress parameter at 07system08execute_ping_01.

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

The Seiko SkyBridge MB-A100/A110 web interface contains an OS command injection vulnerability in the ping functionality. The ipAddress parameter passed to /system/execute_ping is not properly sanitized, allowing attackers to inject arbitrary shell commands by manipulating the input with command separators (e.g., ;, |, &&). This enables complete system compromise with root privileges since the ping function executes with elevated permissions.

MitigationImplement strict input validation using allowlists for IP addresses (rejecting any non-numeric/non-dot characters), or refactor to use language-native ping APIs instead of shell execution. If shell execution is unavoidable, use parameterized command construction and drop privileges where possible.

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 Mb A100 FirmwareOperating system
Affected:<= 4.2.0
Skybridge Mb A110 FirmwareOperating system
Affected:<= 4.2.0

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

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

  1. Confirm device model is SkyBridge MB-A100 or MB-A110
    Access the device web interface or check device documentation/labels to verify the exact model number
    Affected if Device is any variant other than MB-A100 or MB-A110 (not affected)
  2. Check firmware version
    Log into the web interface and navigate to the firmware or system information page, or use SNMP/CLI to query the firmware version
    Affected if Firmware version is 4.2.0 or lower (vulnerable version range)
  3. Verify web interface is accessible
    Attempt to reach the device web interface over HTTP/HTTPS on the management IP
    Affected if Web interface is reachable and responds (attack surface available)
  4. Confirm ping functionality is present
    Check if the /system/execute_ping endpoint exists by reviewing web application paths or attempting a request
    Affected if The ping feature endpoint exists and is enabled (vulnerable component exposed)
  5. Check if ipAddress parameter accepts injection
    Submit a test request to /system/execute_ping with a benign test value containing command separators (e.g., ;echo test) and observe if the response executes the injected command
    Affected if The parameter reflects or executes injected shell characters (vulnerability confirmed)

You are affected if you have a Seiko SkyBridge MB-A100 or MB-A110 device running firmware version 4.2.0 or lower with the web interface ping feature accessible.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 4.2.0
Interim mitigation

Implement strict input validation using allowlists for IP addresses (rejecting any non-numeric/non-dot characters), or refactor to use language-native ping APIs instead of shell execution. If shell execution is unavoidable, use parameterized command construction and drop privileges where possible.

Recommended fix Moderate confidence

Latest firmware version available from Seiko Solutions (contact vendor for specific version beyond 4.2.0)

  1. 1. Contact Seiko Solutions (www.seiko-sol.co.jp) or your authorized Seiko SkyBridge distributor to obtain the latest firmware version.
  2. 2. Download the most recent firmware release for your SkyBridge MB-A100 or MB-A110 device.
  3. 3. Review the firmware release notes to confirm the vulnerability (CVE-2022-36556) is addressed in the new version.
  4. 4. Backup the current device configuration before applying the firmware update.
  5. 5. Apply the firmware update following the manufacturer's documented upgrade procedure.
  6. 6. After upgrade, verify the device is functioning correctly and the vulnerability is resolved.
  7. 7. Validate that the execute_ping_01 function no longer accepts malicious ipAddress input.
Caveat Review release notes for any changes to functionality or configuration that may affect your deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Skybridge Mb A100 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-36556 — 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-2022-36556 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