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-wf2x-8w6j-qw37
No affected components available
Impact
What kind of vulnerability is it? Who is impacted?
This is an XSS vulnerability that has the potential to impact anyone rendering a component directly from a controller with the view_component gem. Note that only components that define a #call method (i.e. instead of using a sidecar template) are affected. The return value of the #call method is not sanitized and can include user-defined content.
In addition, the return value of the #output_postamble method is not sanitized, which can also lead to XSS issues.
Patches
Has the problem been patched? What versions should users upgrade to?
Versions 3.9.0 has been released and fully mitigates both the #call and the #output_postamble vulnerabilities.
Workarounds
Is there a way for users to fix or remediate the vulnerability without upgrading?
Sanitize the return value of #call, eg:
class MyComponent < ApplicationComponent
def call
html_escape("<div>#{user_input}</div>")
end
end
References
Are there any links users can visit to find out more?
https://github.com/ViewComponent/view_component/pull/1950
For more information
If you have any questions or comments about this advisory:
Open an issue in the github/view_component project.
The vulnerability can be exploited over the network without needing physical access. It is easy for an attacker to exploit this vulnerability. An attacker does not need any special privileges or access rights. The attacker needs the user to perform some action, like clicking a link. The vulnerability can affect other systems as well, not just the initial system. There is a low impact on the confidentiality of the information. There is a low impact on the integrity of the data.
Exploitation attempts have been detected. Elevated vigilance and prompt remediation are advised.
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