CVE-2022-30270
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 · uneditedThe Motorola ACE1000 RTU through 2022-05-02 has default credentials. It exposes an SSH interface on port 22/TCP. This interface is used for remote maintenance and for SFTP file-transfer operations that are part of engineering software functionality. Access to this interface is controlled by 5 preconfigured accounts (root, abuilder, acelogin, cappl, ace), all of which come with default credentials. Although the ACE1000 documentation mentions the root, abuilder and acelogin accounts and instructs users to change the default credentials, the cappl and ace accounts remain undocumented and thus are unlikely to have their credentials changed.
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 Motorola ACE1000 RTU exposes an SSH service on port 22 with five preconfigured accounts (root, abuilder, acelogin, cappl, ace) using default credentials. The undocumented cappl and ace accounts likely retain factory defaults, enabling unauthenticated remote access for maintenance and SFTP file transfers.
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 dataall versionsCVSS 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.
-
Identify the device modelCheck the system banner, login prompt, or run a command like 'uname -a', 'cat /proc/cpuinfo', or check the web interface for device identification to confirm it is a Motorola ACE1000 RTUAffected if The device is not a Motorola ACE1000 RTU - this CVE only applies to that specific product
-
Verify SSH service is runningCheck if port 22 is listening by running 'netstat -an | grep :22' or 'nmap -p 22 <target>' or 'ss -tlnp | grep :22'Affected if Port 22 is not open or SSH service is not running - the vulnerability requires SSH to be accessible
-
Test default credentials on SSHAttempt SSH login using each of these accounts with their suspected default passwords: root, abuilder, acelogin, cappl, ace. Try common default passwords such as the username itself, 'motorola', 'admin', 'password', or leave blank. Use: ssh <account>@<target_ip>Affected if Any of the five accounts accepts a default factory password, indicating they have not been changed from defaults
-
Verify undocumented accounts existAfter successful SSH login with any account, check for the presence of 'cappl' and 'ace' users in /etc/passwd or by running 'id cappl' and 'id ace', or attempt to switch to these users with 'su - cappl' or 'su - ace'Affected if The undocumented 'cappl' and 'ace' accounts exist and can be accessed with default credentials
You are affected if you have a Motorola ACE1000 RTU with SSH enabled and any of the five preconfigured accounts (root, abuilder, acelogin, cappl, or ace) retain their factory default passwords.
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 default passwords for all five accounts, prioritizing the undocumented cappl and ace accounts; disable SSH if not required, or implement key-based authentication and network access controls to limit exposure.
- Consultation4.0 h
- Implementation3.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-30270 — 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-30270 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