First published: Tue Oct 08 2019(Updated: )
A remote code execution vulnerability exists in Magento 2.2 prior to 2.2.10, Magento 2.3 prior to 2.3.3 or 2.3.2-p1. An authenticated user can craft a malicious CSRF payload that can result in arbitrary command execution.
Credit: psirt@adobe.com
Affected Software | Affected Version | How to fix |
---|---|---|
composer/magento/product-community-edition | >=2.2<2.2.10>=2.3<2.3.2-p2 | |
composer/magento/community-edition | >=2.3.0<2.3.2-p1 | 2.3.2-p1 |
composer/magento/community-edition | >=2.2.0<2.2.10 | 2.2.10 |
CentOS Libgcc | >=2.2.0<2.2.10 | |
CentOS Libgcc | >=2.2.0<2.2.10 | |
CentOS Libgcc | >=2.3.0<2.3.2 | |
CentOS Libgcc | >=2.3.0<2.3.2 | |
CentOS Libgcc | =2.3.2 | |
CentOS Libgcc | =2.3.2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2019-8109 is a critical vulnerability that allows remote code execution via crafted CSRF payloads.
To fix CVE-2019-8109, upgrade to Magento version 2.2.10 or 2.3.2-p1 or later.
CVE-2019-8109 affects Magento versions prior to 2.2.10 and 2.3.3 or 2.3.2-p1.
An exploit of CVE-2019-8109 could allow authenticated attackers to execute arbitrary commands on your Magento store.
Yes, there is a specific method to exploit CVE-2019-8109 using CSRF that could lead to remote code execution.