Skip to content
Log inStart free trial

GHSA-8gmv-9hwg-w89g BIT-typo3-2022-31046 CVE-2022-31046

Information Disclosure via Export Module

Medium Packagist
Severity
4.3 / 10
Medium · CVSS 3.1
Exploit chance (EPSS)
0.63%
Chance of exploitation in the next 30 days. Higher than 50.22% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
CWE-319 Cleartext Transmission of Sensitive Information
Fix
Available
2 packages have a fixed version

Description

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

Affected versions

Packagist

PackageVulnerableFixed in
typo3/cms
>= 10.0.0, < 10.4.29
10.4.29
typo3/cms
>= 11.0.0, < 11.5.11
11.5.11
typo3/cms-core
>= 7.0.0, < 7.6.57
7.6.57
typo3/cms-core
>= 8.0.0, < 8.7.47
8.7.47
typo3/cms-core
>= 9.0.0, < 9.5.35
9.5.35
typo3/cms-core
>= 10.0.0, < 10.4.29
10.4.29
typo3/cms-core
>= 11.0.0, < 11.5.11
11.5.11

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

typo3/cms Packagist → 10.4.29

composer
composer require typo3/cms:^10.4.29

typo3/cms-core Packagist → 7.6.57

composer
composer require typo3/cms-core:^7.6.57

Severity breakdown

CVSS 3.1 4.3

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

Weakness

CWE-200: Exposure of Sensitive Information to an Unauthorized Actor

The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.

How to prevent it
  • Architecture and Design: Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.

CWE-319: Cleartext Transmission of Sensitive Information

The product transmits sensitive or security-critical data in cleartext in a communication channel that can be sniffed by unauthorized actors.

How to prevent it
  • Architecture and Design: Before transmitting, encrypt the data using reliable, confidentiality-protecting cryptographic protocols.
  • Implementation: When using web applications with SSL, use SSL for the entire session from login to logout, not just for the initial login page.
  • Implementation: When designing hardware platforms, ensure that approved encryption algorithms (such as those recommended by NIST) protect paths from security critical data to trusted user applications.
  • Testing: Use tools and techniques that require manual (human) analysis, such as penetration testing, threat modeling, and interactive tools that allow the tester to record and modify an active session. These may be more effective than strictly automated techniques. This is especially the case with weaknesses that are related to design and business rules.
  • Operation: Configure servers to use encrypted channels for communication, which may include SSL or other secure protocols.

References

Advisories

Packages

Other links

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-68jx-f42c-7599
TYPO3 CMS - Broken Access Control in Backend and Install Tool
High Also affects typo3/cms-core
GHSA-chm7-4vch-h8vr
TYPO3 CMS has Broken Access Control in its Media Module
High Also affects typo3/cms-core
GHSA-jh32-v29g-68pq
TYPO3 CMS has Privilege Escalation & SQL Injection in its Form Framework
High Also affects typo3/cms-core
GHSA-c78m-c52x-jgwp
TYPO3 CMS has Insecure Deserialization via Core API
Medium Also affects typo3/cms-core
GHSA-jf56-v8jc-jcc5
TYPO3 CMS has Broken Access Control in its File Abstraction Layer
Low Also affects typo3/cms-core
GHSA-2j54-93q2-3hjq
TYPO3 CMS has Broken Access Control in Backend API
Medium Also affects typo3/cms-core
GHSA-q93m-25xv-94hh
TYPO3 CMS: Broken Access Control in Media Module
Medium Also affects typo3/cms-core
GHSA-qcmw-6rm2-5x78
TYPO3 CMS has Broken Access Control in its DataHandler
Medium Also affects typo3/cms-core
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor