# CVE-2022-30276: Missing authorization in n/a

> Attackers can invoke RTU functionality without authentication via the IP Gateway protocol, requiring network access to the device.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **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-qf39-vcfc-vp3j

## What is CVE-2022-30276?

CVE-2022-30276 is a high-severity missing authorization 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 MOSCAD and ACE line of RTUs through 2022-05-02 omit an authentication requirement. They feature IP Gateway modules which allow for interfacing between Motorola Data Link Communication (MDLC) networks (potentially over a variety of serial, RF and/or Ethernet links) and TCP/IP networks. Communication with RTUs behind the gateway is done by means of the proprietary IPGW protocol (5001/TCP). This protocol does not have any authentication features, allowing any attacker capable of communicating with the port in question to invoke (a subset of) desired functionality.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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

It affects 2 products.


Products: Motorola Ace Ip Gateway \(4600\) Firmware, Motorola Moscad Ip Gateway Firmware.

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

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

## Is CVE-2022-30276 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-30276 is a high-severity missing authorization 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-30276 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-30276/ (Markdown: https://insights.sbomify.com/CVE-2022-30276/index.md)
```

## Sources

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

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