Headline
GHSA-cqf3-vpx7-rxhw: Improper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS) in Pay
Impact
A payments info page of Pay is susceptible to reflected Cross-site scripting. An attacker could create a working URL that renders a javascript link to a user on a Rails application that integrates Pay. This URL could be distributed via email to specifically target certain individuals. If the targeted application contains a functionality to submit user-generated content (such as comments) the attacker could even distribute the URL using that functionality.
Patches
This has been patched in version 6.3.2 and above.
Pay will now sanitize the back parameter and only permit relative paths.
Package
Affected versions
< 6.3.2
Description
Impact
A payments info page of Pay is susceptible to reflected Cross-site scripting. An attacker could create a working URL that renders a javascript link to a user on a Rails application that integrates Pay. This URL could be distributed via email to specifically target certain individuals. If the targeted application contains a functionality to submit user-generated content (such as comments) the attacker could even distribute the URL using that functionality.
Patches
This has been patched in version 6.3.2 and above.
Pay will now sanitize the back parameter and only permit relative paths.
References
- GHSA-cqf3-vpx7-rxhw
- https://nvd.nist.gov/vuln/detail/CVE-2023-30614
- pay-rails/pay@5d6283a
- pay-rails/pay@c067771
Published to the GitHub Advisory Database
Apr 20, 2023
Last updated
Apr 20, 2023
Related news
Pay is a payments engine for Ruby on Rails 6.0 and higher. In versions prior to 6.3.2 a payments info page of Pay is susceptible to reflected Cross-site scripting. An attacker could create a working URL that renders a javascript link to a user on a Rails application that integrates Pay. This URL could be distributed via email to specifically target certain individuals. If the targeted application contains a functionality to submit user-generated content (such as comments) the attacker could even distribute the URL using that functionality. This has been patched in version 6.3.2 and above. Users are advised to upgrade. There are no known workarounds for this vulnerability.