Bug 19937 - libcryptopp new security issue CVE-2016-9939
Summary: libcryptopp new security issue CVE-2016-9939
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: Security (show other bugs)
Version: 5
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: QA Team
QA Contact: Sec team
URL: https://lwn.net/Vulnerabilities/710210/
Whiteboard: has_procedure MGA5-32-OK advisory MGA...
Keywords: validated_update
Depends on:
Blocks:
 
Reported: 2016-12-13 12:40 CET by David Walser
Modified: 2017-01-07 22:40 CET (History)
5 users (show)

See Also:
Source RPM: libcryptopp-5.6.3-4.mga6.src.rpm
CVE:
Status comment:


Attachments

Description David Walser 2016-12-13 12:40:35 CET
A CVE has been assigned for a security issue in libcryptopp:
http://www.openwall.com/lists/oss-security/2016/12/12/7

I don't believe a fix is available yet.

Mageia 5 is also affected.
David Walser 2016-12-13 12:40:54 CET

Whiteboard: (none) => MGA5TOO

Comment 1 Marja Van Waes 2016-12-14 19:45:58 CET
Assigning to all packagers collectively, since there is no registered maintainer for this package.

CC: (none) => marja11
Assignee: bugsquad => pkg-bugs

Comment 2 Mike Rambo 2016-12-16 17:58:41 CET
Found patches at https://github.com/weidai11/cryptopp/pull/347/files.

Working on fixes for both cauldron and mga5.

CC: (none) => mrambo

Comment 3 Mike Rambo 2016-12-16 21:14:04 CET
Patched package has been uploaded for both Cauldron and MGA5.

Testing procedure https://bugs.mageia.org/show_bug.cgi?id=19381#c6


Advisory:
========================

Updated libcryptopp package fixes security vulnerability:

When Crypto++ library parses an ASN.1 data value, the library allocates for the content octets based on the length octets. Later, if there's too few or too little content octets, the library throws a BERDecodeErr exception. The memory for the content octets will be zeroized (even if unused), which could take a long time on a large allocation (CVE-2016-9939).

References:
http://www.openwall.com/lists/oss-security/2016/12/12/7
https://github.com/weidai11/cryptopp/issues/346
========================

Updated packages in core/updates_testing:
========================
lib64cryptopp6-5.6.3-1.3.mga5
lib64cryptopp-devel-5.6.3-1.3.mga5
libcryptopp-debuginfo-5.6.3-1.3.mga5
libcryptopp-progs-5.6.3-1.3.mga5

from libcryptopp-5.6.3-1.3.mga5.src.rpm

Version: Cauldron => 5
Assignee: pkg-bugs => qa-bugs
Whiteboard: MGA5TOO => has_procedure

Comment 4 Herman Viaene 2016-12-22 15:06:25 CET
MGA5-32 on Acer D620 Xfce
Installation: the debuginfo package seems to be missing here
All tests as per bug 19381 passed.

CC: (none) => herman.viaene
Whiteboard: has_procedure => has_procedure MGA5-32-OK

Comment 5 David Walser 2016-12-26 18:54:57 CET
Debian has issued an advisory for this today (December 26):
https://lists.debian.org/debian-security-announce/2016/msg00332.html

The DSA will be posted here:
https://www.debian.org/security/2016/dsa-3748

URL: (none) => https://lwn.net/Vulnerabilities/710210/

Comment 6 Lewis Smith 2016-12-28 11:35:54 CET
Added advisory as per Comment 3, but unsure whether I should have included the 2 'references' URLs in comment 5.

CC: (none) => lewyssmith
Whiteboard: has_procedure MGA5-32-OK => has_procedure MGA5-32-OK advisory

Comment 7 Lewis Smith 2017-01-06 21:28:36 CET
Testing M5 64-bit real h/w

Updated existing pkgs to:
 libcryptopp-progs-5.6.3-1.3.mga5
 lib64cryptopp6-5.6.3-1.3.mga5

 $ cryptest v > tmp/cryptest_v        [the essential self-test, lots of output]
 $ less  tmp/cryptest_v               [to easily scan/search the output]

Lots of "passed"; many "Failed tests = 0"; no other fail|FAIL|Fail.
O/P ended traditionally with:
"CryptoPP::Exception caught: Can not open file TestVectors/dsa.txt for reading"

Update deemed OK. Validating; advisory already in place - without the 2 refs from Comment 5. Can add them if advised to do so (asked already).

Keywords: (none) => validated_update
Whiteboard: has_procedure MGA5-32-OK advisory => has_procedure MGA5-32-OK advisory MGA5-64-OK
CC: (none) => sysadmin-bugs

Comment 8 Mageia Robot 2017-01-07 22:40:47 CET
An update for this issue has been pushed to the Mageia Updates repository.

http://advisories.mageia.org/MGASA-2017-0010.html

Status: NEW => RESOLVED
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.