GHSA-xw2r-f8xv-c8xp CVE-2023-39527
PrestaShop XSS injection through Validate::isCleanHTML method
Medium
Packagist
- Severity
- 8.3 / 10
- Medium · CVSS 3.1
- Exploit chance (EPSS)
- 0.51%
- Chance of exploitation in the next 30 days. Higher than 43.78% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-116 Improper Encoding or Escaping of Output
- Fix
8.1.1- Upgrade prestashop/prestashop to this version or later
Description
Impact
xss injection through isCleanHTML method
Patches
1.7.8.10 8.0.5 8.1.1
Found by
Aleksey Solovev (Positive Technologies)
Workarounds
References
Affected versions
Packagist
| Package | Vulnerable | Fixed in |
|---|---|---|
| prestashop/prestashop | >= 8.1.0, < 8.1.1 |
8.1.1 |
| prestashop/prestashop | >= 8.0.0, < 8.0.5 |
8.0.5 |
| prestashop/prestashop | < 1.7.8.10 |
1.7.8.10 |
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.1
- composer
composer require prestashop/prestashop:^8.1.1
Severity breakdown
CVSS 3.1 8.3
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:H/A:H
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- High
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- High
- Availability
- High
Weakness
CWE-116: Improper Encoding or Escaping of Output
The product prepares a structured message for communication with another component, but encoding or escaping of the data is either missing or done incorrectly. As a result, the intended structure of the message is not preserved.
How to prevent it
- Architecture and Design: Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, consider using the ESAPI Encoding control [REF-45] or a similar tool, library, or framework. These will help the programmer encode outputs in a manner less prone to error. Alternately, use built-in functions, but consider using wrappers in case those functions are discovered to have a vulnerability.
- Architecture and Design: If available, use structured mechanisms that automatically enforce the separation between data and code. These mechanisms may be able to provide the relevant quoting, encoding, and validation automatically, instead of relying on the developer to provide this capability at every point where output is generated. For example, stored procedures can enforce database query structure and reduce the likelihood of SQL injection.
- Architecture and Design, Implementation: Understand the context in which your data will be used and the encoding that will be expected. This is especially important when transmitting data between different components, or when generating outputs that can contain multiple encodings at the same time, such as web pages or multi-part mail messages. Study all expected communication protocols and data representations to determine the required encoding strategies.
- Architecture and Design: In some cases, input validation may be an important strategy when output encoding is not a complete solution. For example, you may be providing the same output that will be processed by multiple consumers that use different encodings or representations. In other cases, you may be required to allow user-supplied input to contain control information, such as limited HTML tags that support formatting in a wiki or bulletin board. When this type of requirement must be met, use an extremely strict allowlist to limit which control sequences can be used. Verify that the resulting syntactic structure is what you expect. Use your normal encoding methods for the remainder of the input.
- Architecture and Design: Use input validation as a defense-in-depth measure to reduce the likelihood of output encoding errors (see CWE-20).
- Requirements: Fully specify which encodings are required by components that will be communicating with each other.
- Implementation: When exchanging data between components, ensure that both components are using the same character encoding. Ensure that the proper encoding is applied at each interface. Explicitly set the encoding you are using whenever the protocol allows you to do so.
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-7pjr-2rgh-fc5g Anonymous PrestaShop customer can download other customers' invoices | Medium | 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 |
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