Information Disclosure due to Out-of-scope Site Resolution
🔗 CVE IDs covered (1)
📋 Description
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)
Problem
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.
Solution
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.
Credits
Thanks to Garvin Hicking who reported this issue, and to TYPO3 core & security team members Oliver Hader and Benjamin Franzke who fixed the issue.
References
🎯 Affected products4
- composer/typo3/cms-core:>= 9.4.0, < 9.5.42
- composer/typo3/cms-core:>= 10.0.0, < 10.4.39
- composer/typo3/cms-core:>= 11.0.0, < 11.5.30
- composer/typo3/cms-core:>= 12.0.0, < 12.4.4
🔗 References (5)
- https://github.com/TYPO3/typo3/security/advisories/GHSA-jq6g-4v5m-wm9r
- https://nvd.nist.gov/vuln/detail/CVE-2023-38499
- https://github.com/TYPO3/typo3/commit/702e2debd4b28f9cdb540544565fe6a8627ccb6a
- https://typo3.org/security/advisory/typo3-core-sa-2023-003
- https://github.com/advisories/GHSA-jq6g-4v5m-wm9r