MediumGHSA-8gmv-9hwg-w89gBIT-typo3-2022-31046CVE-2022-31046

Information Disclosure via Export Module

Published 17 Jun 2022 · Updated 6 Dec 2023

Affected packages

Affected
>=7.0.0 <7.6.57
Fixed in
7.6.57
Update to the fixed version for your release line, for example:composer require typo3/cms-core:^7.6.57
Affected
>=8.0.0 <8.7.47
Fixed in
8.7.47
Update to the fixed version for your release line, for example:composer require typo3/cms-core:^8.7.47
Affected
>=9.0.0 <9.5.35
Fixed in
9.5.35
Update to the fixed version for your release line, for example:composer require typo3/cms-core:^9.5.35
Affected
>=10.0.0 <10.4.29
Fixed in
10.4.29
Update to the fixed version for your release line, for example:composer require typo3/cms-core:^10.4.29
Affected
>=11.0.0 <11.5.11
Fixed in
11.5.11
Update to the fixed version for your release line, for example:composer require typo3/cms-core:^11.5.11
typo3/cmsComposer
Affected
>=10.0.0 <10.4.29
Fixed in
10.4.29
Update to the fixed version for your release line, for example:composer require typo3/cms:^10.4.29
typo3/cmsComposer
Affected
>=11.0.0 <11.5.11
Fixed in
11.5.11
Update to the fixed version for your release line, for example:composer require typo3/cms:^11.5.11

Details

> ### Meta > * CVSS: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N/E:F/RL:O/RC:C (4.0)

Problem

The export functionality fails to limit the result set to allowed columns of a particular database table. This allows authenticated users to export internal details of database tables to which they already have access.

Solution

Update to TYPO3 versions 7.6.57 ELTS, 8.7.47 ELTS, 9.5.35 ELTS, 10.4.29, 11.5.11 that fix the problem described above.

In order to address this issue, access to mentioned export functionality is completely denied for regular backend users.

ℹ️ Strong security defaults - Manual actions required Following User TSconfig setting would allow using the export functionality for particular users:

options.impexp.enableExportForNonAdminUser = 1

Credits

Thanks to TYPO3 core merger Lina Wolf who reported this issue and to TYPO3 security member Torben Hansen who fixed the issue.

References

Is GHSA-8gmv-9hwg-w89g in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected typo3/cms-core, and gives you the command that fixes it.

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.