CVE-2020-9579: Critical severity centos libgcc vulnerability
Published Jun 26, 2020
·Updated
Magento versions 2.3.4 and earlier, 2.2.11 and earlier (see note), 1.14.4.4 and earlier, and 1.9.4.4 and earlier have a security mitigation bypass vulnerability. Successful exploitation could lead to arbitrary code execution.
Affected Software
9 affected componentsFixes available
composer/magento/core<1.9.4.5
1.9.4.5
composer/magento/community-edition>=2.3.0<2.3.4-p2
2.3.4-p2
composer/magento/community-edition<=2.2.11
Magento Magento<=1.9.4.4
Magento Magento<=1.14.4.4
Magento Magento>=2.2.0<=2.2.11
Magento Magento>=2.2.0<=2.2.11
Magento Magento>=2.3.0<=2.3.4
Magento Magento>=2.3.0<=2.3.4
Event History
Jun 26, 2020
CVE Published
via MITRE·08:18 PM
Data Sourced
via MITRE·08:18 PM
DescriptionWeakness
May 24, 2022
Advisory Published
via GitHub·05:21 PM
Frequently Asked Questions
1
What is the severity of CVE-2020-9579?
CVE-2020-9579 has a high severity rating as it allows for arbitrary code execution.
2
How do I fix CVE-2020-9579?
To fix CVE-2020-9579, upgrade to Magento version 1.9.4.5, 2.3.4-p2, or later.
3
Which Magento versions are affected by CVE-2020-9579?
CVE-2020-9579 affects Magento versions 2.3.4 and earlier, 2.2.11 and earlier, and several earlier versions of Magento 1.x.
4
Can CVE-2020-9579 be exploited remotely?
Yes, CVE-2020-9579 can be exploited remotely if the vulnerable version of Magento is accessible.
5
What are the potential impacts of exploiting CVE-2020-9579?
Exploiting CVE-2020-9579 can lead to full control of the affected Magento installation, including sensitive data access.