CVE-2022-38600: Medium severity Mplayerhq Mplayer vulnerability
Published Sep 15, 2022
·Updated
Mplayer SVN-r38374-13.0.1 is vulnerable to Memory Leak via vf.c and vfvo.c.
Affected Software
5 affected componentsFixes available
Mplayerhq Mplayer=svn-r38374-13.0.1
debian/mplayer<2:1.5+svn38408-1
2:1.5+svn38408-1
debian/mplayer<2:1.5+svn38408-1
2:1.5+svn38408-1
debian/mplayer<2:1.5+svn38408-1
2:1.5+svn38408-1
debian/mplayer
2:1.5+svn38408-12:1.5+svn38674-22:1.5+svn38681-2
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/mplayerto a version that resolves this vulnerability.Fixed in 2:1.5+svn38408-1Fixed in 2:1.5+svn38674-2Fixed in 2:1.5+svn38681-2 - Upgrade
Upgrade
debian/mplayerto a version that resolves this vulnerability.Fixed in 2:1.5+svn38408-1
Event History
Sep 15, 2022
CVE Published
via MITRE·03:07 PM
Data Sourced
via MITRE·03:07 PM
Description
Data Sourced
via OSV·04:15 PM
DescriptionSeverityAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2022-38600?
CVE-2022-38600 has a medium severity level due to its potential to cause memory leaks.
2
How do I fix CVE-2022-38600?
To fix CVE-2022-38600, update MPlayer to a version that addresses this memory leak issue.
3
What software is affected by CVE-2022-38600?
CVE-2022-38600 affects MPlayer version SVN-r38374-13.0.1.
4
What are the potential consequences of CVE-2022-38600?
The consequences of CVE-2022-38600 include excessive memory consumption which may lead to application crashes.
5
Is there a workaround for CVE-2022-38600 if I cannot update?
A potential workaround for CVE-2022-38600 could be to minimize the use of features that trigger the memory leak.