Security advisory
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."
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2022-48217
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 4 Nov 2026, 00:53 UTC · Revision 1
Source evidence
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."
osv:CVE-2022-48217
Complete source record
{
"id": "83f89dc9cef599f5a83858113e9ec6364e50995b8903e50dd7a181c0a5ae1c14",
"url": "https://osv.dev/vulnerability/CVE-2022-48217",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "CVE-2022-48217",
"summary": "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.\"",
"evidence": "osv:CVE-2022-48217",
"products": [],
"severity": "high",
"structured": {
"id": "CVE-2022-48217",
"aliases": [
"CVE-2022-48217"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/tradr-project/tf_remapper_cpp",
"type": "GIT",
"events": [
{
"introduced": "ff9ede0b9c4b40bf0a025dead691e0406532e928"
},
{
"last_affected": "ff9ede0b9c4b40bf0a025dead691e0406532e928"
}
],
"database_specific": {
"extracted_events": [
{
"cpe": "cpe:2.3:a:tradr-project:tf_remapper:1.1.1:*:*:*:*:robot_operating_system:*:*",
"range": [
{
"introduced": "1.1.1"
},
{
"last_affected": "1.1.1"
}
],
"source": "CPE_STRING"
}
]
}
}
],
"versions": [
"1.1.1"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2022-48217.json"
}
}
],
"modified": "2026-10-28T02:30:32.602326563Z",
"provider": "osv",
"references": [
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/48xxx/CVE-2022-48217.json",
"https://nvd.nist.gov/vuln/detail/CVE-2022-48217",
"https://github.com/tradr-project/tf_remapper_cpp/issues/1"
],
"provider_metadata": {
"isDisputed": true,
"cna_assigner": "mitre",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/48xxx/CVE-2022-48217.json"
}
},
"related_cves": [
{
"value": "CVE-2022-48217",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 499374,
"published_at": "2023-01-04T00:00:00+00:00"
}