CVE-2019-13465
Published: 30 December 2019
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.
Priority
Status
Package | Release | Status |
---|---|---|
ros-ros-comm Launchpad, Ubuntu, Debian |
bionic |
Needs triage
|
disco |
Ignored
(end of life)
|
|
eoan |
Ignored
(end of life)
|
|
focal |
Not vulnerable
(1.14.3+ds1-11)
|
|
groovy |
Not vulnerable
(1.14.3+ds1-11)
|
|
hirsute |
Not vulnerable
(1.14.3+ds1-11)
|
|
impish |
Not vulnerable
(1.14.3+ds1-11)
|
|
jammy |
Not vulnerable
(1.14.3+ds1-11)
|
|
kinetic |
Not vulnerable
(1.14.3+ds1-11)
|
|
lunar |
Not vulnerable
(1.14.3+ds1-11)
|
|
mantic |
Not vulnerable
(1.14.3+ds1-11)
|
|
trusty |
Does not exist
|
|
upstream |
Needs triage
|
|
xenial |
Needs triage
|
Severity score breakdown
Parameter | Value |
---|---|
Base score | 8.6 |
Attack vector | Network |
Attack complexity | Low |
Privileges required | None |
User interaction | None |
Scope | Changed |
Confidentiality | None |
Integrity impact | None |
Availability impact | High |
Vector | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H |