CVE-2022-36560
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 · uneditedSeiko SkyBridge MB-A200 v01.00.04 and below was discovered to contain multiple hard-coded passcodes for root. Attackers are able to access the passcodes at /etc/srapi/config/system.conf and /usr/sbin/ssol-sshd.sh.
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 Seiko SkyBridge MB-A200 router firmware (v01.00.04 and below) contains multiple hard-coded root passwords embedded directly in system configuration files at /etc/srapi/config/system.conf and /usr/sbin/ssol-sshd.sh. Attackers who discover these credentials can gain full administrative access to the device, potentially compromising the entire network segment the device operates in.
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<= 01.00.04CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm device model is Seiko SkyBridge MB-A200Access the device admin web interface, check the device label, or use SNMP to identify the exact model number of the routerAffected if Device is not a Seiko SkyBridge MB-A200 router
-
Determine firmware versionLog into the device admin interface and navigate to the status or system information page, or use command-line access via SSH/Telnet to retrieve the firmware versionAffected if Firmware version is 01.00.04 or lower
-
Inspect system configuration file for hard-coded passwordsIf you have shell access to the device, examine the file /etc/srapi/config/system.conf and search for hard-coded password strings or encoded credentialsAffected if Hard-coded root passwords are present in /etc/srapi/config/system.conf
-
Inspect SSH daemon script for hard-coded passwordsIf you have shell access to the device, examine the file /usr/sbin/ssso-sshd.sh and search for hard-coded password strings or credentialsAffected if Hard-coded root passwords are present in /usr/sbin/ssso-sshd.sh
A user is affected if they are using a Seiko SkyBridge MB-A200 router with firmware version 01.00.04 or below and hard-coded root credentials exist in either /etc/srapi/config/system.conf or /usr/sbin/ssso-sshd.sh
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 dataImmediately change all default credentials on affected devices and contact the vendor for a firmware update that removes hard-coded passwords. If no update is available, restrict device management interfaces to trusted networks and implement network-level access controls.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-36560 — 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-36560 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