blob: bb3d37e9d2d45c5a1967b5bc67d6ade22b238bf8 [file] [log] [blame]
<?xml version="1.0" encoding="utf-8"?>
<glsa id="200909-03">
<title>Apache Portable Runtime, APR Utility Library: Execution of arbitrary code</title>
Multiple integer overflows in the Apache Portable Runtime and its Utility
Library might allow for the remote execution of arbitrary code.
<product type="ebuild">apr apr-util</product>
<announced>September 09, 2009</announced>
<revised>September 09, 2009: 01</revised>
<package name="dev-libs/apr" auto="yes" arch="*">
<unaffected range="ge">1.3.8</unaffected>
<vulnerable range="lt">1.3.8</vulnerable>
<package name="dev-libs/apr-util" auto="yes" arch="*">
<unaffected range="ge">1.3.9</unaffected>
<vulnerable range="lt">1.3.9</vulnerable>
The Apache Portable Runtime (aka APR) provides a set of APIs for
creating platform-independent applications. The Apache Portable Runtime
Utility Library (aka APR-Util) provides an interface to functionality
such as XML parsing, string matching and databases connections.
Matt Lewis reported multiple Integer overflows in the apr_rmm_malloc(),
apr_rmm_calloc(), and apr_rmm_realloc() functions in misc/apr_rmm.c of
APR-Util and in memory/unix/apr_pools.c of APR, both occurring when
aligning memory blocks.
<impact type="normal">
A remote attacker could entice a user to connect to a malicious server
with software that uses the APR or act as a malicious client to a
server that uses the APR (such as Subversion or Apache servers),
possibly resulting in the execution of arbitrary code with the
privileges of the user running the application.
There is no known workaround at this time.
All Apache Portable Runtime users should upgrade to the latest version:
# emerge --sync
# emerge --ask --oneshot --verbose &quot;&gt;=dev-libs/apr-1.3.8&quot;</code>
All APR Utility Library users should upgrade to the latest version:
# emerge --sync
# emerge --ask --oneshot --verbose &quot;&gt;=dev-libs/apr-util-1.3.9&quot;</code>
<uri link="">CVE-2009-2412</uri>
<metadata tag="requester" timestamp="Thu, 06 Aug 2009 13:32:21 +0000">
<metadata tag="submitter" timestamp="Thu, 06 Aug 2009 13:46:29 +0000">
<metadata tag="bugReady" timestamp="Mon, 24 Aug 2009 20:40:13 +0000">