Skip to content
Log inStart free trial

GHSA-fh99-4pgr-8j99 BIT-typo3-2022-31047 CVE-2022-31047

Insertion of Sensitive Information into Log File in typo3/cms-core

Medium Packagist
Severity
5.3 / 10
Medium · CVSS 3.1
Exploit chance (EPSS)
1.13%
Chance of exploitation in the next 30 days. Higher than 66.36% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-209 Generation of Error Message Containing Sensitive Information
CWE-532 Insertion of Sensitive Information into Log File
Fix
Available
2 packages have a fixed version

Description

Meta

  • CVSS: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N/E:F/RL:O/RC:C (4.9)

Problem

It has been discovered that system internal credentials or keys (e.g. database credentials) have been logged as plaintext in exception handlers, when logging the complete exception stack trace.

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.

Credits

Thanks to Marco Huber 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 5.3

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

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

Weakness

CWE-209: Generation of Error Message Containing Sensitive Information

The product generates an error message that includes sensitive information about its environment, users, or associated data.

How to prevent it
  • Implementation: Ensure that error messages only contain minimal details that are useful to the intended audience and no one else. The messages need to strike the balance between being too cryptic (which can confuse users) or being too detailed (which may reveal more than intended). The messages should not reveal the methods that were used to determine the error. Attackers can use detailed information to refine or optimize their original attack, thereby increasing their chances of success. If errors must be captured in some detail, record them in log messages, but consider what could occur if the log messages can be viewed by attackers. Highly sensitive information such as passwords should never be saved to log files. Avoid inconsistent messaging that might accidentally tip off an attacker about internal state, such as whether a user account exists or not.
  • Implementation: Handle exceptions internally and do not display errors containing potentially sensitive information to a user.
  • Implementation: Use naming conventions and strong types to make it easier to spot when sensitive data is being used. When creating structures, objects, or other complex entities, separate the sensitive and non-sensitive data as much as possible.
  • Implementation, Build and Compilation: Debugging information should not make its way into a production release.
  • Implementation, Build and Compilation: Debugging information should not make its way into a production release.
  • System Configuration: Where available, configure the environment to use less verbose error messages. For example, in PHP, disable the display_errors setting during configuration, or at runtime using the error_reporting() function.
  • System Configuration: Create default error pages or messages that do not leak any information.

CWE-532: Insertion of Sensitive Information into Log File

The product writes sensitive information to a log file.

How to prevent it
  • Architecture and Design, Implementation: Consider seriously the sensitivity of the information written into log files. Do not write secrets into the log files.
  • Distribution: Remove debug log files before deploying the application into production.
  • Operation: Protect log files against unauthorized read/write.
  • Implementation: Adjust configurations appropriately when software is transitioned from a debug state to production.

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