Syslog-ng: Chroot escape
1.
Gentoo Linux Security Advisory
Version Information
| Advisory Reference |
GLSA 200907-10 / syslog-ng |
| Release Date |
July 12, 2009 |
| Latest Revision |
July 12, 2009: 01 |
| Impact |
low |
| Exploitable |
local |
| Package |
Vulnerable versions |
Unaffected versions |
Architecture(s) |
| app-admin/syslog-ng |
<
2.1.3 |
revision >=
2.0.10,
>=
2.1.3 |
All supported architectures
|
Related bugreports:
#247278
Synopsis
Syslog-ng does not properly initialize its chroot jail allowing for an
escape if a separate vulnerability in Syslog-ng is exploited.
2.
Impact Information
Background
Syslog-ng is a flexible and scalable system logger.
Description
Florian Grandel reported that Syslog-ng does not call chdir() before
chroot() which leads to an inherited file descriptor to the current
working directory.
Impact
A local attacker might exploit a separate vulnerability in Syslog-ng
and use this vulnerability to escape the chroot jail.
3.
Resolution Information
Workaround
There is no known workaround at this time.
Resolution
All Syslog-ng 2.0 users should upgrade to the latest version:
Code Listing 3.1: Resolution |
# emerge --sync
# emerge --ask --oneshot --verbose ">=app-admin/syslog-ng-2.0.10"
|
All Syslog-ng 2.1 users should upgrade to the latest version:
Code Listing 3.2: Resolution |
# emerge --sync
# emerge --ask --oneshot --verbose ">=app-admin/syslog-ng-2.1.3"
|
4.
References
|