# CVE-2022-48217: Other in n/a

> Attackers controlling source code of another node can alter robot behavior via parameter injection in the tf_remapper_node component.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/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:** 4 Jan 2023
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-mxv6-m383-394f

## What is CVE-2022-48217?

CVE-2022-48217 is a high-severity vulnerability in n/a, published on 4 Jan 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The tf_remapper_node component 1.1.1 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 old_tf_topic_name and/or new_tf_topic_name parameter. NOTE: the vendor's position is "it is the responsibility of the programmer to make sure that only known and required parameters are set and unexpected parameters are not."

Weakness: CWE-75 (Failure to Sanitize Special Elements into a Different Plane)

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

It affects 1 product.


Products: Tradr-Project Tf Remapper.

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

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

## Is CVE-2022-48217 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-48217 is a high-severity vulnerability in n/a, published on 4 Jan 2023. 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-48217 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-48217/ (Markdown: https://insights.sbomify.com/CVE-2022-48217/index.md)
```

## Sources

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

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