blob: cea7d0f601d5ec72d07c41d6e78adb1ca4038248 (
plain)
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
35
36
37
38
39
40
41
42
|
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE glsa SYSTEM "http://www.gentoo.org/dtd/glsa.dtd">
<glsa id="202406-04">
<title>LZ4: Memory Corruption</title>
<synopsis>A vulnerability has been discovered in LZ4, which can lead to memory corruption.</synopsis>
<product type="ebuild">lz4</product>
<announced>2024-06-22</announced>
<revised count="1">2024-06-22</revised>
<bug>791952</bug>
<access>local</access>
<affected>
<package name="app-arch/lz4" auto="yes" arch="*">
<unaffected range="ge">1.9.3-r1</unaffected>
<vulnerable range="lt">1.9.3-r1</vulnerable>
</package>
</affected>
<background>
<p>LZ4 is a lossless compression algorithm, providing compression speed > 500 MB/s per core, scalable with multi-cores CPU. It features an extremely fast decoder, with speed in multiple GB/s per core, typically reaching RAM speed limits on multi-core systems.</p>
</background>
<description>
<p>An attacker who submits a crafted file to an application linked with lz4 may be able to trigger an integer overflow, leading to calling of memmove() on a negative size argument, causing an out-of-bounds write and/or a crash.</p>
</description>
<impact type="normal">
<p>The greatest impact of this flaw is to availability, with some potential impact to confidentiality and integrity as well.</p>
</impact>
<workaround>
<p>There is no known workaround at this time.</p>
</workaround>
<resolution>
<p>All LZ4 users should upgrade to the latest version:</p>
<code>
# emerge --sync
# emerge --ask --oneshot --verbose ">=app-arch/lz4-1.9.3-r1"
</code>
</resolution>
<references>
<uri link="https://nvd.nist.gov/vuln/detail/CVE-2021-3520">CVE-2021-3520</uri>
</references>
<metadata tag="requester" timestamp="2024-06-22T08:02:03.295621Z">graaff</metadata>
<metadata tag="submitter" timestamp="2024-06-22T08:02:03.298226Z">graaff</metadata>
</glsa>
|
GitWeb
