Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 628684 - <dev-libs/libmspack-0.5_alpha-r1: heap-based buffer overflow in mspack/lzxd.c (CVE-2017-6419)
Summary: <dev-libs/libmspack-0.5_alpha-r1: heap-based buffer overflow in mspack/lzxd.c...
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Security
Classification: Unclassified
Component: Vulnerabilities (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo Security
URL: https://bugzilla.redhat.com/show_bug....
Whiteboard: B3 [noglsa cve]
Keywords:
Depends on:
Blocks: CVE-2017-6419
  Show dependency tree
 
Reported: 2017-08-23 07:59 UTC by Agostino Sarubbo
Modified: 2018-03-27 02:40 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Agostino Sarubbo gentoo-dev 2017-08-23 07:59:45 UTC
From ${URL} :

mspack/lzxd.c in libmspack 0.5alpha, as used in ClamAV 0.99.2, allows
remote attackers to cause a denial of service (heap-based buffer
overflow and application crash) or possibly have unspecified other
impact via a crafted CHM file.

Upstream patch:

https://github.com/vrtadmin/clamav-devel/commit/a83773682e856ad6529ba6db8d1792e6d515d7f1


@maintainer(s): after the bump, in case we need to stabilize the package, please let us know if it is ready for the stabilization or not.
Comment 1 Maciej Mrozowski gentoo-dev 2017-08-24 20:09:11 UTC
libmspack-0.5_alpha-r1 with patch from clamav in repo.

I would say it's ready for stabilization.
I wonder about relation to bug 625634.
Comment 2 Maciej Mrozowski gentoo-dev 2017-10-19 23:12:39 UTC
libmspack-0.6_alpha in portage. Please stabilize this one instead. Also see bug 625634.
Comment 3 Thomas Deutschmann (RETIRED) gentoo-dev 2018-03-02 00:23:09 UTC
Freeing CVE-2017-6419 alias to create a tracker bug.
Comment 4 Aaron Bauman (RETIRED) gentoo-dev 2018-03-27 02:40:06 UTC
No PoC for ACE/RCE.  Downgraded to B3.  Cleanup will be tracked in bug #625634