CVE-2008-5244: Critical severity xine vulnerability
Published Nov 26, 2008
·Updated
Unspecified vulnerability in xine-lib before 1.1.15 has unknown impact and attack vectors related to libfaad. NOTE: due to the lack of details, it is not clear whether this is an issue in xine-lib or in libfaad.
Affected Software
49 affected components
xine Xine-lib=1.1.10
xine Xine-lib=1-rc3a
xine Xine-lib=1.1.10.1
xine Xine-lib=1.1.9.1
xine Xine-lib=1_beta7
xine Xine-lib=1.1.11
xine Xine-lib=1-rc3
xine Xine-lib=1_beta9
xine Xine-lib=1.1.0
xine Xine-lib=1.1.7
xine Xine-lib=1-rc3b
xine Xine-lib=1-rc5
xine Xine-lib=1.1.2
xine Xine-lib=1_beta4
xine Xine-lib<=1.1.15
xine Xine-lib=1.1.9
xine Xine-lib=1.0.3a
xine Xine-lib=1-rc4a
xine Xine-lib=1.1.12
xine Xine-lib=1.0.1
xine Xine-lib=1-rc8
xine Xine-lib=1.1.13
xine Xine-lib=1.1.11.1
xine Xine-lib=1-rc2
xine Xine-lib=1.0.2
xine Xine-lib=1.1.8
xine Xine-lib=1_beta2
xine Xine-lib=1-rc7
xine Xine-lib=1_beta5
xine Xine-lib=1_beta11
xine Xine-lib=1-rc1
xine Xine-lib=1.1.3
xine Xine-lib=1.1.4
xine Xine-lib=1.1.5
xine Xine-lib=0.9.13
xine Xine-lib=1.0
xine Xine-lib=1-rc3c
xine Xine-lib=1_beta6
xine Xine-lib=1.1.14
xine Xine-lib=1-rc4
xine Xine-lib=1_beta1
xine Xine-lib=1.1.6
xine Xine-lib=1_beta12
xine Xine-lib=1.1.1
xine Xine-lib=1_beta10
xine Xine-lib=1_beta8
xine Xine-lib=1-rc0a
xine Xine-lib=1-rc6a
xine Xine-lib=1_beta3
Event History
Nov 26, 2008
CVE Published
via MITRE·01:00 AM
Data Sourced
via MITRE·01:00 AM
Description
Frequently Asked Questions
1
What is the severity of CVE-2008-5244?
The severity of CVE-2008-5244 is currently unknown due to the lack of detailed information about the vulnerability.
2
How do I fix CVE-2008-5244?
To fix CVE-2008-5244, update xine-lib to version 1.1.15 or later.
3
Which versions of xine-lib are affected by CVE-2008-5244?
CVE-2008-5244 affects xine-lib versions before 1.1.15.
4
What does CVE-2008-5244 impact?
CVE-2008-5244 relates to an unspecified vulnerability that may involve libfaad, affecting xine-lib.
5
Is there any workaround for CVE-2008-5244?
There is no known workaround for CVE-2008-5244; updating to the latest version is advised.