radvd >= 2.0 blocks router update processing
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mirantis OpenStack |
Fix Committed
|
High
|
Alexander Ignatov | ||
6.0.x |
Fix Released
|
High
|
Denis Meltsaykin | ||
6.1.x |
Fix Released
|
High
|
Alexander Ignatov |
Bug Description
This is [pre-OSSA] Vulnerability in OpenStack Neutron (CVE-2014-8153)
Original bug: https:/
=======
In radvd 2.0+, daemonization code was rewritten, switching from libdaemon's daemon_fork() to Linux daemon() call.
If no logging method (-m option) is passed to radvd, and the default logging method is used (which is L_STDERR_SYSLOG), then daemon() is called with (1, 1) arguments, meaning no chroot (fine) and not closing stderr (left there for logging) (not fine). So execute() call that spawns radvd and expects it to daemonize and return code never actually completes, blocked on stderr.
The fix is to pass e.g. -m syslog to radvd to make it close stderr and return.
CVE References
information type: | Private Security → Public Security |
tags: | added: feature-security |
Fix is not applicable for 5.x versions since there was no radvd tool