Summary: | <media-video/vlc-1.1.12 NULL dereference in HTTP server (CVE-2010-3124,CVE-2011-1087) | ||
---|---|---|---|
Product: | Gentoo Security | Reporter: | Sean Amoss (RETIRED) <ackle> |
Component: | Vulnerabilities | Assignee: | Gentoo Security <security> |
Status: | RESOLVED FIXED | ||
Severity: | minor | CC: | media-video |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | http://www.videolan.org/security/sa1107.html | ||
Whiteboard: | C3 [glsa] | ||
Package list: | Runtime testing required: | --- |
Description
Sean Amoss (RETIRED)
![]() ![]() @maintainer: it looks like we have vlc-1.1.12 ebuild as ~arch. Is it ready to be tested for stable? (In reply to comment #1) > @maintainer: it looks like we have vlc-1.1.12 ebuild as ~arch. Is it ready to > be tested for stable? yes Arches, please test and mark stable: =media-video/vlc-1.1.12 Target KEYWORDS : "alpha amd64 ppc ppc64 sparc x86" CVE-2011-1087 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2011-1087): Buffer overflow in VideoLAN VLC media player 1.0.5 allows user-assisted remote attackers to cause a denial of service (memory corruption and application crash) or possibly execute arbitrary code via a crafted .mp3 file that is played during bookmark creation. CVE-2010-3124 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2010-3124): Untrusted search path vulnerability in bin/winvlc.c in VLC Media Player 1.1.3 and earlier allows local users, and possibly remote attackers, to execute arbitrary code and conduct DLL hijacking attacks via a Trojan horse wintab32.dll that is located in the same folder as a .mp3 file. amd64: pass NB: .la file present, I don't know if those should be fixed or not. (In reply to comment #5) > amd64: pass > > NB: .la file present, I don't know if those should be fixed or not. Fixed in 9999 version atm x86 stable amd64 done. Thanks Elijah and Agostino ppc/ppc64 stable alpha/sparc stable Thanks folks. Added glsa request vote. Thanks, everyone. We'll send this with the existing VLC bugs. This issue was resolved and addressed in GLSA 201411-01 at http://security.gentoo.org/glsa/glsa-201411-01.xml by GLSA coordinator Sean Amoss (ackle). |