| Gói / sản phẩm | Phiên bản bị ảnh hưởng | Phiên bản đã vá |
|---|---|---|
| typo3/cms-core | ≥ 10.0.0, < 10.4.39≥ 11.0.0, < 11.5.30≥ 12.0.0, < 12.4.4≥ 9.4.0, < 9.5.42 | 10.4.3911.5.3012.4.49.5.42 |
| typo3 | ≥ 10.0.0, < 10.4.39≥ 11.0.0, < 11.5.30≥ 12.0.0, < 12.4.4≥ 9.4.0, < 9.5.42 | 10.4.3911.5.3012.4.49.5.42 |
CVSS:
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N/E:F/RL:O/RC:C(3.5)
In multi-site scenarios, enumerating the HTTP query parameters id and L allowed out-of-scope access to rendered content in the website frontend. For instance, this allowed visitors to access content of an internal site by adding handcrafted query parameters to the URL of a site that was publicly available.
Update to TYPO3 versions 9.5.42 ELTS, 10.4.39 ELTS, 11.5.30, 12.4.4 that fix the problem described above.
ℹ️ Strong security defaults - Manual actions required Resolving sites by the
idandLHTTP query parameters is now denied per default. However, it is still allowed to resolve a particular page by e.g.https://example.org/?id=123&L=0- as long as thepage-id 123is in the scope of the site configured for thebase-url example.org. The new feature flagsecurity.frontend.allowInsecureSiteResolutionByQueryParameters- which is disabled per default - can be used to reactivate the previous behavior.
Thanks to Garvin Hicking who reported this issue, and to TYPO3 core & security team members Oliver Hader and Benjamin Franzke who fixed the issue.
Bạn đang dùng một trong các sản phẩm này? Quét site để biết có đang lộ phiên bản có lỗ hổng không.
Quét site miễn phí