Vulnerability in ros-ros-comm
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as DEBIAN-CVE-2019-13465 has been found in ros-ros-comm.
Risk of unauthorized operations or information disclosure.
What to do: upgrade ros-ros-comm to 1.14.3+ds1-10 or later.
If unsure, ask your IT team or search "ros-ros-comm DEBIAN-CVE-2019-13465" on the vendor's site.
DEBIAN-CVE-2019-13465 (ros-ros-comm)
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 1.14.3+ds1-10 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (unclassified) exists in ros-ros-comm.
Check the vendor advisory for the affected versions of ros-ros-comm.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 1.14.3+ds1-10.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'ros-ros-comm' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1
Identify exposureidentify
grep -r 'ros-ros-comm' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
ros-ros-commを grep し、稼働しているサービス・バージョンを把握する。 -
2
Apply patchpatch
Upgrade ros-ros-comm to 1.14.3+ds1-10ステージング環境で 1.14.3+ds1-10 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3
Post-deployment verificationverify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
| Ecosystem | Package | Affected | Fixed |
|---|---|---|---|
| Debian:12 | ros-ros-comm |
< 1.14.3+ds1-10 |
1.14.3+ds1-10 |
| Debian:13 | ros-ros-comm |
< 1.14.3+ds1-10 |
1.14.3+ds1-10 |
| Debian:14 | ros-ros-comm |
< 1.14.3+ds1-10 |
1.14.3+ds1-10 |
Original description The description as published by the source.
An issue was discovered in the ROS communications-related packages (aka ros_comm or ros-melodic-ros-comm) through 1.14.3. ROS_ASSERT_MSG only works when ROS_ASSERT_ENABLED is defined. This leads to a problem in the remove() function in clients/roscpp/src/libros/spinner.cpp. When ROS_ASSERT_ENABLED is not defined, the iterator loop will run out of the scope of the array, and cause denial of service for other components (that depend on the communication-related functions of this package). NOTE: The reporter of this issue now believes it was a false alarm.
Source: OSV.dev (Open Source Vulnerabilities) OSV
References
- advisory security-tracker.debian.org