Summary: | media-libs/imlib2: unspecified errors leading to DoS and execution of code (CVE-2006-480[6789]) | ||||||
---|---|---|---|---|---|---|---|
Product: | Gentoo Security | Reporter: | Raphael Marichez (Falco) (RETIRED) <falco> | ||||
Component: | Vulnerabilities | Assignee: | Gentoo Security <security> | ||||
Status: | RESOLVED FIXED | ||||||
Severity: | major | CC: | rico32 | ||||
Priority: | High | ||||||
Version: | unspecified | ||||||
Hardware: | All | ||||||
OS: | Linux | ||||||
URL: | http://secunia.com/advisories/22732/ | ||||||
Whiteboard: | A/B? 1?/2 [glsa] Falco | ||||||
Package list: | Runtime testing required: | --- | |||||
Attachments: |
|
Description
Raphael Marichez (Falco) (RETIRED)
![]() Ubuntu seems to have a patch for this. The new packages are linked on http://www.securityfocus.com/archive/1/450551 and when applying the Ubuntu-specific package patch to the original source tree there appears a file debian/patches/99_loader_overflows.patch which supposedly fixes this vulnerability. Created attachment 101331 [details, diff]
99_loader_overflows.patch for imlib2-1.2.1 from Ubuntu
ive used the actual fix committed upstream and added 1.3.0 with it looks like a forgotten bug here 1.3.0 has been marked stable on all arches CVEs talk about <1.2.1 being affected, can someone confirm that <1.3.0 has been affected as well? looks like this will need a GLSA then (In reply to comment #4) > CVEs talk about <1.2.1 being affected, can someone confirm that <1.3.0 has been > affected as well? that's a good question > > looks like this will need a GLSA then > i agree Yeah I think we need a GLSA for this one. Seems to by my affirmative day today. "Yes". Hu, what are exactly the vulnerable and the fixed versions?? GLSA 200612-20 , thanks everybody! |