Skip to content
This page tracks the Debian fix status. The vulnerability itself is described on the main CVE page. View CVE-2021-37146 →
Unrated

Vulnerability in ros-ros-comm

DEBIAN-CVE-2021-37146 First seen on SecPulse

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-2021-37146 has been found in ros-ros-comm.
Risk of unauthorized operations or information disclosure.
What to do: upgrade ros-ros-comm to 1.15.13+ds1-2 or later.
If unsure, ask your IT team or search "ros-ros-comm DEBIAN-CVE-2021-37146" on the vendor's site.

DEBIAN-CVE-2021-37146 (ros-ros-comm)
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 1.15.13+ds1-2 — 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.

What is the problem

A vulnerability (unclassified) exists in ros-ros-comm.

Affected scope

Check the vendor advisory for the affected versions of ros-ros-comm.

Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

How to fix

Update to 1.15.13+ds1-2.

Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

Detection

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. 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. 2
    Apply patchpatch
    Upgrade ros-ros-comm to 1.15.13+ds1-2

    ステージング環境で 1.15.13+ds1-2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verificationverify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

EcosystemPackageAffectedFixed
Debian:12 ros-ros-comm
< 1.15.13+ds1-2
1.15.13+ds1-2
Debian:13 ros-ros-comm
< 1.15.13+ds1-2
1.15.13+ds1-2
Debian:14 ros-ros-comm
< 1.15.13+ds1-2
1.15.13+ds1-2
Original description The description as published by the source.

An infinite loop in Open Robotics ros_comm XMLRPC server in ROS Melodic through 1.4.11 and ROS Noetic through1.15.11 allows remote attackers to cause a Denial of Service in ros_comm via a crafted XMLRPC call.

Source: OSV.dev (Open Source Vulnerabilities) OSV

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details