bk2k/bootstrap-package
Affected
- introduced
7.1.0, fixed7.1.2(ecosystem)
Fixed versions
7.1.2
Fix
The export has no generic command for this ecosystem.
Advisory
Also known as: BIT-typo3-2021-21365, CVE-2021-21365
Cross-Site Scripting in Bootstrap Package
Problem
It has been discovered that rendering content in the website frontend is vulnerable to cross-site scripting. A valid backend user account is needed to exploit this vulnerability.
The following templates are affected by the vulnerability:
Resources/Private/Partials/ContentElements/Carousel/Item/CallToAction.htmlResources/Private/Partials/ContentElements/Carousel/Item/Header.htmlResources/Private/Partials/ContentElements/Carousel/Item/Text.htmlResources/Private/Partials/ContentElements/Carousel/Item/TextAndImage.htmlResources/Private/Partials/ContentElements/Header/SubHeader.htmlUsers of the extension, who have overwritten the affected templates with custom code must manually apply the security fix as shown in this Git commit.
Solution
Update to version 7.1.2, 8.0.8, 9.0.4, 9.1.3, 10.0.10 or 11.0.3 of the Bootstrap Package that fix the problem described.
Updated version are available from the TYPO3 extension manager, Packagist and at https://extensions.typo3.org/extension/download/bootstrap_package/.
Credits
Thanks to TYPO3 security team member Oliver Hader who reported and fixed the issue.
Medium Basis: The source's own band: MODERATE
7.1.0, fixed 7.1.2 (ecosystem)7.1.2
The export has no generic command for this ecosystem.
8.0.0, fixed 8.0.8 (ecosystem)8.0.8
The export has no generic command for this ecosystem.
9.0.0, fixed 9.0.4 (ecosystem)9.0.4
The export has no generic command for this ecosystem.
9.1.0, fixed 9.1.3 (ecosystem)9.1.3
The export has no generic command for this ecosystem.
10.0.0, fixed 10.0.10 (ecosystem)10.0.10
The export has no generic command for this ecosystem.
11.0.0, fixed 11.0.3 (ecosystem)11.0.3
The export has no generic command for this ecosystem.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0