# CVE-2022-30271: Hardcoded credentials in n/a

> Attackers can use a hardcoded SSH private key to gain unauthorized access to Motorola ACE1000 RTUs, potentially leading to full system compromise.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Jul 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-59rw-g46v-6c42

## What is CVE-2022-30271?

CVE-2022-30271 is a critical vulnerability in n/a, published on 26 Jul 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Motorola ACE1000 RTU through 2022-05-02 ships with a hardcoded SSH private key and initialization scripts (such as /etc/init.d/sshd_service) only generate a new key if no private-key file exists. Thus, this hardcoded key is likely to be used by default.

Weakness: CWE-798 (Use of Hard-coded Credentials), CWE-259 (Use of Hard-coded Password)

## Which versions are affected by CVE-2022-30271?

It affects 1 product.


Products: Motorola Ace1000 Firmware.

## How do I fix CVE-2022-30271?

No fix has been published for CVE-2022-30271 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-30271 being exploited?

There is no known exploitation of CVE-2022-30271 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2022-30270](https://insights.sbomify.com/CVE-2022-30270/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2022-30274](https://insights.sbomify.com/CVE-2022-30274/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2022-30269](https://insights.sbomify.com/CVE-2022-30269/): Security feature bypass in n/a (high 8.8)
- [CVE-2022-30272](https://insights.sbomify.com/CVE-2022-30272/): Security feature bypass in n/a (high 7.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-30271 and fix it if it is affected.

What it is: CVE-2022-30271 is a critical vulnerability in n/a, published on 26 Jul 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-30271 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-30271/ (Markdown: https://insights.sbomify.com/CVE-2022-30271/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-30271
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-30271
- OSV: https://osv.dev/vulnerability/CVE-2022-30271

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-30271/
Summaries are generated and may contain mistakes; the official description above is the record.