Vulnerability in ros-ros-comm (DEBIAN-CVE-2019-13566)

Summary

Vulnerability in ros-ros-comm (DEBIAN-CVE-2019-13566). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 1.14.3+ds1-10 or later.

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. A buffer overflow allows attackers to cause a denial of service and possibly execute arbitrary code via an IP address with a long hostname.

Source: OSV.dev (Open Source Vulnerabilities) OSV

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-13566 has been found in ros-ros-comm.
Successful exploitation can lead to full system takeover.
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-13566" on the vendor's site.

DEBIAN-CVE-2019-13566 (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.

❓ 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: ?. Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 1.14.3+ds1-10.

🛡️ 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
Identify exposure identify
```
grep -r 'ros-ros-comm' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で ros-ros-comm を grep し、稼働しているサービス・バージョンを把握する。
2
Apply patch patch
```
Upgrade ros-ros-comm to 1.14.3+ds1-10
```
ステージング環境で 1.14.3+ds1-10 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
3
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Debian:12 ros-ros-comm

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.14.3+ds1-10"}]}]

Debian:13 ros-ros-comm

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.14.3+ds1-10"}]}]

Debian:14 ros-ros-comm

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.14.3+ds1-10"}]}]

References

advisory security-tracker.debian.org