# CVE-2022-30272: Security feature bypass in n/a

> Attackers can install malicious firmware on Motorola ACE1000 RTUs because updates lack cryptographic signing, allowing arbitrary code execution.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Jul 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-23v4-qfpm-c2cx

## What is CVE-2022-30272?

CVE-2022-30272 is a high-severity vulnerability in n/a, published on 26 Jul 2022. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The Motorola ACE1000 RTU through 2022-05-02 mishandles firmware integrity. It utilizes either the STS software suite or ACE1000 Easy Configurator for performing firmware updates. In case of the Easy Configurator, firmware updates are performed through access to the Web UI where file system, kernel, package, bundle, or application images can be installed. Firmware updates for the Front End Processor (FEP) module are performed via access to the SSH interface (22/TCP), where a .hex file image is transferred and a bootloader script invoked. File system, kernel, package, and bundle updates are supplied as RPM (RPM Package Manager) files while FEP updates are supplied as S-rec files. In all cases, firmware images were found to have no authentication (in the form of firmware signing) and only relied on insecure checksums for regular integrity checks.

Weakness: CWE-345 (Insufficient Verification of Data Authenticity)

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

It affects 1 product.


Products: Motorola Ace1000 Firmware.

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

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

## Is CVE-2022-30272 being exploited?

There is no known exploitation of CVE-2022-30272 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-30271](https://insights.sbomify.com/CVE-2022-30271/): 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)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-30272 is a high-severity vulnerability in n/a, published on 26 Jul 2022. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-30272 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-30272/ (Markdown: https://insights.sbomify.com/CVE-2022-30272/index.md)
```

## Sources

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

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