GHSA-7pjr-2rgh-fc5g CVE-2024-34717
Anonymous PrestaShop customer can download other customers' invoices
- Severity
- 5.3 / 10
- Medium · CVSS 3.1
- Exploit chance (EPSS)
- 0.53%
- Chance of exploitation in the next 30 days. Higher than 44.56% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
- Fix
8.1.6- Upgrade prestashop/prestashop to this version or later
Description
Impact
Since PrestaShop 8.1.5, any invoice can be downloaded from front-office in anonymous mode, by supplying a random secure_key parameter in the url.
Patches
Patched in 8.1.6
Workarounds
Upgrade to 8.1.6
Thank you to Samuel Bodevin, who found this vulnerability and shared it with the PrestaShop team.
Affected versions
Packagist
| Package | Vulnerable | Fixed in |
|---|---|---|
| prestashop/prestashop | >= 8.1.5, < 8.1.6 |
8.1.6 |
How to fix
Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.
prestashop/prestashop Packagist → 8.1.6
- composer
composer require prestashop/prestashop:^8.1.6
Severity breakdown
CVSS 3.1 5.3
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
Weakness
CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
How to prevent it
- Architecture and Design: Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.
References
Advisories
Packages
Other links
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why it's related |
|---|---|---|
| GHSA-w9f3-qc75-qgx9 PrestaShop has a stored XSS executable in customer service view | Critical | Also affects prestashop/prestashop |
| GHSA-35pf-37c6-jxjv PrestaShop has multiple stored XSS vulnerabilities via unprotected Template variables | Medium | Also affects prestashop/prestashop |
| GHSA-283w-xf3q-788v PrestaShop: Improper Use of Validation Framework | Medium | Also affects prestashop/prestashop |
| GHSA-67v7-3g49-mxh2 PrestaShop affected by time based enumeration in FO login form | Medium | Also affects prestashop/prestashop |
| GHSA-8xx5-h6m3-jr33 Presta Shop vulnerable to email enumeration | Low | Also affects prestashop/prestashop |
| GHSA-45vm-3j38-7p78 PrestaShop cross-site scripting via customer contact form in FO, through file upload | Medium | Also affects prestashop/prestashop |
| GHSA-3366-9287-7qpr Path disclosure in JavaScript variable | Medium | Also affects prestashop/prestashop |
| GHSA-vr7m-r9vm-m4wf PrestaShop XSS can be stored in DB from "add a message form" in order detail page (FO) | Medium | Also affects prestashop/prestashop |
MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.
Check your repos with MergeHarbor