-
-
Notifications
You must be signed in to change notification settings - Fork 3.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bootstrap Cross-Site Scripting (XSS) vulnerability - CVE-2024-6484 #1251
Comments
https://www.herodevs.com/vulnerability-directory/cve-2024-6484 How is this a CVE! You have to put your own hyperlink with malicious javascript on the page:
|
Would sanitizing the |
@twbs please, pay attention to this problem |
is there any solution for this issue? will this be patched or not? |
It's this really an issue? If you're building Carousels with unchecked user provided URLs, then that is the problem. I don't think it should be down to TWS to do the sanitisation here. |
it brings some problems in our pipeline (security check), are you able to solve the issue? |
some cms user may do something wrong - it requires additional issues on the website, but why not to protect against here? plus script is more hidden, and as a carousel button is more attractive to click. |
You can mitigate this by adding a one line event.preventDefault(), just like in Bootstrap 5's carousel.js. Free fix that doesn't require a subscription. Here's my fix in carousel.js - the method starts at line 542: static _dataApiClickHandler(event) {
const selector = Util.getSelectorFromElement(this)
event.preventDefault(); // this is the fix
if (!selector) {
return The vulnerability is way overblown. It's way too easy to submit CVE these days to scare people. |
As identified by our bundle audit job in the CI:
Text from the GitHub advisories:
"A vulnerability has been identified in Bootstrap that exposes users to Cross-Site Scripting (XSS) attacks. The issue is present in the carousel component, where the data-slide and data-slide-to attributes can be exploited through the href attribute of an tag due to inadequate sanitization. This vulnerability could potentially enable attackers to execute arbitrary JavaScript within the victim's browser."
The text was updated successfully, but these errors were encountered: