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

> Attackers controlling a ROS node can manipulate robot behavior by exploiting an unvalidated topic name parameter in the ntpd driver.

- **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:** 1 Jan 2023
- **Updated:** 11 Apr 2025
- **Also known as:** GHSA-92fc-jgvr-56vr

## What is CVE-2022-48198?

CVE-2022-48198 is a critical missing authorization vulnerability in n/a, published on 1 Jan 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The ntpd_driver component before 1.3.0 and 2.x before 2.2.0 for Robot Operating System (ROS) allows attackers, who control the source code of a different node in the same ROS application, to change a robot's behavior. This occurs because a topic name depends on the attacker-controlled time_ref_topic parameter.

Weakness: CWE-668 (Exposure of Resource to Wrong Sphere)

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

It affects 1 product.


Products: Ntpd Driver Project Ntpd Driver.

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

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

## Is CVE-2022-48198 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-48198 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2022-48198 is a critical missing authorization vulnerability in n/a, published on 1 Jan 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-48198 exists.

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-48198/ (Markdown: https://insights.sbomify.com/CVE-2022-48198/index.md)
```

## Sources

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

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