CVE-2022-1795: Use After Free in gpac/gpac
Published May 18, 2022
·Updated
Use After Free in GitHub repository gpac/gpac prior to v2.1.0-DEV.
Affected Software
2 affected componentsFixes available
debian/gpac<=0.5.2-426-gc5ad4e4+dfsg5-5
1.0.1+dfsg1-4+deb11u32.2.1+dfsg1-3
Gpac GPAC<2.1.0
Remediation
Event History
May 18, 2022
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
DescriptionSeverityWeakness
Frequently Asked Questions
1
What is the severity of CVE-2022-1795?
CVE-2022-1795 is classified as a high severity vulnerability due to the potential for exploitation through use after free issues.
2
How do I fix CVE-2022-1795?
To fix CVE-2022-1795, upgrade the gpac software to version 2.1.0 or later.
3
Which versions of gpac are affected by CVE-2022-1795?
CVE-2022-1795 affects gpac versions prior to 2.1.0, including versions up to 2.1.0-DEV.
4
What type of vulnerability is CVE-2022-1795?
CVE-2022-1795 is a use after free vulnerability that can lead to potential memory corruption.
5
Where can I find more information about CVE-2022-1795?
More information about CVE-2022-1795 can be found in the security tracking databases and GitHub repository.