Know every vulnerabilitybefore it knows you.
DevGuard continuously monitors your dependencies and alerts you when CVEs like this one affect your stack — with real-time threat intelligence built for developers.
GHSA-5vrp-638w-p8m2
No affected components available
Impact
This XSS vulnerability is about the system configs
- design/header/welcome
- design/header/logo_src
- design/header/logo_src_small
- design/header/logo_alt
They are intended to enable admins to set a text in the two cases, and to define an image url for the other two cases. But because of previously missing escaping allowed to input arbitrary html and as a consequence also arbitrary JavaScript.
While this is in most usage scenarios not a relevant issue, some people work with more restrictive roles in the backend. Here the ability to inject JavaScript with these settings would be an unintended and unwanted privilege.
Patches
Has the problem been patched? What versions should users upgrade to?
The problem is patched with Version 20.10.1 or higher.
Workarounds
Is there a way for users to fix or remediate the vulnerability without upgrading?
Possible mitigations are
- Restricting access to the System Configs
- checking templates where these settings are used to apply proper html filtering
For Users relying on this possibility
Some Users might actually rely on the ability to use html there.
You can restore the previous behavior by making use of the new introduced ->getUnescapedValue() method on this escaped elements. Developers should have a look at the newly introduced Mage_Core_Model_Security_HtmlEscapedString
Credit
Credit goes to Aakash Adhikari @justlife4x4 for finding this issue
The vulnerability can be exploited over the network without needing physical access. It is easy for an attacker to exploit this vulnerability. An attacker needs high-level or administrative privileges. No user interaction is needed for the attacker to exploit this vulnerability. The vulnerability can affect other systems as well, not just the initial system. There is a low impact on the integrity of the data.
Limited exploitation activity has been observed. Close monitoring and planned remediation are recommended.
The exploit probability is very low. The vulnerability is unlikely to be exploited in the next 30 days.
We did not find any exploit available. Neither in GitHub repositories nor in the Exploit-Database.
Browse More
Continuously monitor your dependencies and get alerted when vulnerabilities like this one affect your stack.
Checkout DevGuard