blob: a7eb0bd92ecaa5f79a83e0b5c8e8f73bfb94d038 (
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
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
|
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE glsa SYSTEM "http://www.gentoo.org/dtd/glsa.dtd">
<glsa id="201702-15">
<title>OCaml: Buffer overflow and information disclosure</title>
<synopsis>A buffer overflow in OCaml might allow remote attackers to obtain
sensitive information or crash an OCaml-based application.
</synopsis>
<product type="ebuild">ocaml</product>
<announced>2017-02-20</announced>
<revised>2017-02-20: 1</revised>
<bug>581946</bug>
<access>remote</access>
<affected>
<package name="dev-lang/ocaml" auto="yes" arch="*">
<unaffected range="ge">4.04.0</unaffected>
<vulnerable range="lt">4.04.0</vulnerable>
</package>
</affected>
<background>
<p>OCaml is a high-level, strongly-typed, functional, and object-oriented
programming language from the ML family of languages.
</p>
</background>
<description>
<p>It was discovered that OCaml was vulnerable to a runtime bug that, on
64-bit platforms, causes size arguments to internal memmove calls to be
sign-extended from 32- to 64-bits before being passed to the memmove
function. This leads to arguments between 2GiB and 4GiB being interpreted
as larger than they are (specifically, a bit below 2^64), causing a
buffer overflow. Further, arguments between 4GiB and 6GiB are interpreted
as 4GiB smaller than they should be causing a possible information leak.
</p>
</description>
<impact type="normal">
<p>A remote attacker, able to interact with an OCaml-based application,
could possibly obtain sensitive information or cause a Denial of Service
condition.
</p>
</impact>
<workaround>
<p>There is no known workaround at this time.</p>
</workaround>
<resolution>
<p>All OCaml users should upgrade to the latest version:</p>
<code>
# emerge --sync
# emerge --ask --oneshot --verbose ">=dev-lang/ocam-4.04.0"
</code>
<p>Packages which depend on OCaml may need to be recompiled. Tools such as
qdepends (included in app-portage/portage-utils) may assist in
identifying these packages:
</p>
<code>
# emerge --oneshot --ask --verbose $(qdepends -CQ dev-lang/ocaml | sed
's/^/=/')
</code>
</resolution>
<references>
<uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-8869">CVE-2015-8869</uri>
</references>
<metadata tag="requester" timestamp="2017-02-13T00:59:45Z">whissi</metadata>
<metadata tag="submitter" timestamp="2017-02-20T23:19:06Z">whissi</metadata>
</glsa>
|
GitWeb
