You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

76 lines
2.5 KiB

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE glsa SYSTEM "http://www.gentoo.org/dtd/glsa.dtd">
<glsa id="201111-09">
<title>Perl Safe module: Arbitrary Perl code injection</title>
<synopsis>The Safe module for Perl does not properly restrict code, allowing
a remote attacker to execute arbitrary Perl code outside of a restricted
compartment.
</synopsis>
<product type="ebuild">Safe</product>
<announced>2011-11-20</announced>
<revised count="1">2011-11-20</revised>
<bug>325563</bug>
<access>remote</access>
<affected>
<package name="perl-core/Safe" auto="yes" arch="*">
<unaffected range="ge">2.27</unaffected>
<vulnerable range="lt">2.27</vulnerable>
</package>
<package name="virtual/perl-Safe" auto="yes" arch="*">
<unaffected range="ge">2.27</unaffected>
<vulnerable range="lt">2.27</vulnerable>
</package>
</affected>
<background>
<p>Safe is a Perl module to compile and execute code in restricted
compartments.
</p>
</background>
<description>
<p>Unsafe code evaluation prevents the Safe module from properly
restricting the code of implicitly called methods on implicitly blessed
objects.
</p>
</description>
<impact type="normal">
<p>A remote attacker could entice a user to load a specially crafted Perl
script, resulting in execution arbitrary Perl code outside of a
restricted compartment.
</p>
</impact>
<workaround>
<p>There is no known workaround at this time.</p>
</workaround>
<resolution>
<p>All users of the standalone Perl Safe module should upgrade to the
latest version:
</p>
<code>
# emerge --sync
# emerge --ask --oneshot --verbose "&gt;=perl-core/Safe-2.27"
</code>
<p>All users of the Safe module bundled with Perl should upgrade to the
latest version:
</p>
<code>
# emerge --sync
# emerge --ask --oneshot --verbose "&gt;=virtual/perl-Safe-2.27"
</code>
<p>NOTE: This is a legacy GLSA. Updates for all affected architectures are
available since July 18, 2010. It is likely that your system is already
no longer affected by this issue.
</p>
</resolution>
<references>
<uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2010-1168">CVE-2010-1168</uri>
</references>
<metadata timestamp="2011-10-07T23:37:03Z" tag="requester">
underling
</metadata>
<metadata timestamp="2011-11-20T17:56:51Z" tag="submitter">ackle</metadata>
</glsa>