GHSA-c5mj-39cf-3pp5: Typo3/cms TYPO3 Security Misconfiguration For Backend Vulnerability

HIGH
CVSS 7.3
CWE-287
Published
Advisory Summary

GHSA-c5mj-39cf-3pp5 is a HIGH (CVSS 7.3) typo3 security misconfiguration for backend vulnerability (CWE-287: Improper Authentication) affecting Typo3/cms libraries in the Packagist ecosystem. The issue involves typo3 security misconfiguration for backend user accounts. Remediation is available by upgrading affected packages to version 8.7.23, 9.5.4.

GHSA-c5mj-39cf-3pp5 at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-c5mj-39cf-3pp5
Severity HIGH
CVSS v3.1 Base Score 7.3
CWE Classification CWE-287: Improper Authentication
Affected Product Typo3/cms
Package Ecosystem Packagist
Published Date
Last Updated

Security Impact

CVSS: 7.3

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction Required (UI:R)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity High (I:H)
Availability None (A:N)

How to Fix GHSA-c5mj-39cf-3pp5

To remediate this vulnerability, upgrade all affected Typo3/cms dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

typo3/cms fixed: 8.7.23
Upgrade typo3/cms to 8.7.23
typo3/cms fixed: 9.5.4
Upgrade typo3/cms to 9.5.4
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for typo3/cms

How to Check if You Are Affected

To determine whether your application is affected by GHSA-c5mj-39cf-3pp5, inspect your project dependencies for Typo3/cms:

inspect dependencies for typo3/cms

Analyze the terminal output to locate any version of Typo3/cms in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 8.7.23), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-287: Improper Authentication, where when an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. In Typo3/cms, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

When using the TYPO3 backend in order to create new backend user accounts, database records containing insecure or empty credentials might be persisted. When the type of user account is changed - which might be entity type or the admin flag for backend users - the backend form is reloaded in order to reflect changed configuration possibilities. However, this leads to persisting the current state as well, which can result into some of the following: - account contains empty login credentials (username and/or password) - account is incomplete and contains weak credentials (username and/or password) Albeit the functionality provided by the TYPO3 core cannot be used either with empty usernames or empty passwords, it still can be a severe vulnerability to custom authentication service implementations. This weakness cannot be directly exploited and requires interaction on purpose by some backend user having according privileges.

GHSA-c5mj-39cf-3pp5 Affected Typo3/cms Versions

2 component(s)
Fixed Versions:
8.7.239.5.4
Product / Package Ecosystem Affected Versions Fixed Version
typo3/cms
Packagist
≥ 8.0.0
< 8.7.23
8.7.23
typo3/cms
Packagist
≥ 9.0.0
< 9.5.4
9.5.4

References

Frequently Asked Questions

What is GHSA-c5mj-39cf-3pp5?
GHSA-c5mj-39cf-3pp5 is a security vulnerability in Typo3/cms involving TYPO3 Security Misconfiguration for Backend User Accounts under CWE-287: Improper Authentication.
Which Typo3/cms versions are affected?
Affected versions include releases prior to 8.7.23, 9.5.4 across affected packages: typo3/cms.
What version fixes GHSA-c5mj-39cf-3pp5?
Upgrading to 8.7.23, 9.5.4 (or the latest patched release for your respective branch) resolves the vulnerability.
Is typo3/cms affected?
Yes, typo3/cms is affected in releases prior to 8.7.23, 9.5.4. Upgrade your dependency to 8.7.23, 9.5.4 or later.
What is the CVSS score of GHSA-c5mj-39cf-3pp5?
GHSA-c5mj-39cf-3pp5 has a CVSS v3.1 base score of 7.3 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N.
What CWE is associated with GHSA-c5mj-39cf-3pp5?
GHSA-c5mj-39cf-3pp5 is classified under CWE-287: Improper Authentication (When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.).
How can I check Packagist dependencies for GHSA-c5mj-39cf-3pp5?
Run the dependency tree command: 'inspect dependencies for typo3/cms'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-c5mj-39cf-3pp5",
  "modified" : "2024-06-07T17:19:38Z",
  "published" : "2024-06-07T17:19:38Z",
  "aliases" : [ ],
  "summary" : "TYPO3 Security Misconfiguration for Backend User Accounts",
  "details" : "When using the TYPO3 backend in order to create new backend user accounts, database records containing insecure or empty credentials might be persisted. When the type of user account is changed - which might be entity type or the admin flag for backend users - the backend form is reloaded in order to reflect changed configuration possibilities. However, this leads to persisting the current state as well, which can result into some of the following:\n\n- account contains empty login credentials (username and/or password)\n- account is incomplete and contains weak credentials (username and/or password)\n\nAlbeit the functionality provided by the TYPO3 core cannot be used either with empty usernames or empty passwords, it still can be a severe vulnerability to custom authentication service implementations.\n\nThis weakness cannot be directly exploited and requires interaction on purpose by some backend user having according privileges.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "typo3/cms"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "8.0.0"
      }, {
        "fixed" : "8.7.23"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "typo3/cms"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "9.0.0"
      }, {
        "fixed" : "9.5.4"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/TYPO3/typo3/commit/b3608d14e1915030cde272000a247cb6d5f982b8"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/TYPO3/typo3/commit/e4d0cff40a4f8f597e52c20fff529e206bb62703"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/FriendsOfPHP/security-advisories/blob/master/typo3/cms/2019-01-22-2.yaml"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/TYPO3/typo3"
  }, {
    "type" : "WEB",
    "url" : "https://typo3.org/security/advisory/typo3-core-sa-2019-002"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-287" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2024-06-07T17:19:38Z",
    "nvd_published_at" : null
  }
}