blob: ec12bbac80f0d37bd9384a73f830c31859156983 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
|
<define-tag description>LTS security update</define-tag>
<define-tag moreinfo>
<p>John Lightsey and Todd Rinaldo reported that the opportunistic loading
of optional modules can make many programs unintentionally load code
from the current working directory (which might be changed to another
directory without the user realising) and potentially leading to
privilege escalation, as demonstrated in Debian with certain
combinations of installed packages.</p>
<p>The problem relates to Perl loading modules from the includes directory
array ("@INC") in which the last element is the current directory (".").
That means that, when <q>perl</q> wants to load a module (during first
compilation or during lazy loading of a module in run time), perl will
look for the module in the current directory at the end, since '.' is
the last include directory in its array of include directories to seek.
The issue is with requiring libraries that are in "." but are not
otherwise installed.</p>
<p>With this update the Sys::Syslog Perl module is updated to not load
modules from current directory.</p>
<p>For Debian 7 <q>Wheezy</q>, these problems have been fixed in version
0.29-1+deb7u1.</p>
<p>We recommend that you upgrade your libsys-syslog-perl packages.</p>
<p>Further information about Debian LTS security advisories, how to apply
these updates to your system and frequently asked questions can be
found at: <a href="https://wiki.debian.org/LTS">https://wiki.debian.org/LTS</a></p>
</define-tag>
# do not modify the following line
#include "$(ENGLISHDIR)/lts/security/2016/dla-584.data"
# $Id: $
|
