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

> Attackers can install malicious applications on Motorola ACE1000 RTUs by bypassing integrity checks that rely on insecure checksums instead of cryptographic signing.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Jul 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-p4gj-rmqv-7h27

## What is CVE-2022-30269?

CVE-2022-30269 is a high-severity vulnerability in n/a, published on 26 Jul 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Motorola ACE1000 RTUs through 2022-05-02 mishandle application integrity. They allow for custom application installation via either STS software, the C toolkit, or the ACE1000 Easy Configurator. In the case of the Easy Configurator, application images (as PLX/DAT/APP/CRC files) are uploaded via the Web UI. In case of the C toolkit, they are transferred and installed using SFTP/SSH. In each case, application 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-30269?

It affects 1 product.


Products: Motorola Ace1000 Firmware.

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

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

## Is CVE-2022-30269 being exploited?

There is no known exploitation of CVE-2022-30269 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-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-30269 and fix it if it is affected.

What it is: CVE-2022-30269 is a high-severity vulnerability in n/a, published on 26 Jul 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-30269 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-30269/ (Markdown: https://insights.sbomify.com/CVE-2022-30269/index.md)
```

## Sources

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

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