algolia/algoliasearch-magento-2
Affected
- introduced
3.17.0-beta.1, fixed3.17.2(ecosystem)
Fixed versions
3.17.2
Fix
The export has no generic command for this ecosystem.
Advisory
Also known as: None
Algolia Search & Discovery for Magento 2 Has Untrusted Data Handling
Impact
Versions of the Algolia Search & Discovery extension for Magento 2 prior to 3.17.2 and 3.16.2 contain a vulnerability where data read from the database was treated as a trusted source during job execution.
If an attacker is able to modify records used by the extension’s indexing queue, this could result in arbitrary PHP code execution when the affected job is processed.
Exploitation requires the ability to write malicious data to the Magento database and for the indexing queue to be enabled.
---
Patches
This vulnerability has been fixed in the following versions:
Merchants should upgrade to a supported patched version immediately.
Versions outside the supported maintenance window do not receive security updates and remain vulnerable.
---
Workarounds
Upgrading to a patched version is the only recommended remediation.
If an immediate upgrade is not possible, the following temporary risk mitigations may reduce exposure:
algoliasearch_queue table for unexpected or unrecognized entries.algoliasearch_queue_archive.These mitigations are provided as guidance only and do not replace upgrading to a patched version.
---
References
Medium Basis: The source's own band: MODERATE
3.17.0-beta.1, fixed 3.17.2 (ecosystem)3.17.2
The export has no generic command for this ecosystem.
0, fixed 3.16.2 (ecosystem)3.16.2
The export has no generic command for this ecosystem.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0