CVE-2023-38499: Typo3/cms core Information Disclosure Due To Out-of-scope Vulnerability

LOW
Advisory Identifier: GHSA-jq6g-4v5m-wm9r
CVSS 3.7
CWE-200
Published
Advisory Summary

CVE-2023-38499 is a LOW (CVSS 3.7) information disclosure due to out-of-scope vulnerability (CWE-200: Exposure of Sensitive Information to an Unauthorized Actor) affecting Typo3/cms core libraries in the Packagist ecosystem. The issue involves information disclosure due to out-of-scope site resolution. Remediation is available by upgrading affected packages to version 9.5.42, 10.4.39, 11.5.30, 12.4.4.

CVE-2023-38499 at a Glance

CVE Identifier CVE-2023-38499
GHSA Identifier GHSA-jq6g-4v5m-wm9r
Severity LOW
CVSS v3.1 Base Score 3.7
CWE Classification CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
Affected Product Typo3/cms core
Package Ecosystem Packagist
Published Date
Last Updated

Security Impact

CVSS: 3.7

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

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

How to Fix CVE-2023-38499

To remediate this vulnerability, upgrade all affected Typo3/cms core 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-core fixed: 9.5.42
Upgrade typo3/cms-core to 9.5.42
typo3/cms-core fixed: 10.4.39
Upgrade typo3/cms-core to 10.4.39
typo3/cms-core fixed: 11.5.30
Upgrade typo3/cms-core to 11.5.30
typo3/cms-core fixed: 12.4.4
Upgrade typo3/cms-core to 12.4.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-core

How to Check if You Are Affected

To determine whether your application is affected by CVE-2023-38499, inspect your project dependencies for Typo3/cms core:

inspect dependencies for typo3/cms-core

Analyze the terminal output to locate any version of Typo3/cms core in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 9.5.42), 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-200: Exposure of Sensitive Information to an Unauthorized Actor, where the product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. In Typo3/cms core, 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

> ### 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 `id` and `L` HTTP 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 the `page-id 123` is in the scope of the site configured for the `base-url example.org`. > The new feature flag `security.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 * [TYPO3-CORE-SA-2023-003](https://typo3.org/security/advisory/typo3-core-sa-2023-003)

CVE-2023-38499 Affected Typo3/cms core Versions

4 component(s)
Fixed Versions:
9.5.4210.4.3911.5.3012.4.4
Product / Package Ecosystem Affected Versions Fixed Version
typo3/cms-core
Packagist
≥ 9.4.0
< 9.5.42
9.5.42
typo3/cms-core
Packagist
≥ 10.0.0
< 10.4.39
10.4.39
typo3/cms-core
Packagist
≥ 11.0.0
< 11.5.30
11.5.30
typo3/cms-core
Packagist
≥ 12.0.0
< 12.4.4
12.4.4

References

Frequently Asked Questions

What is CVE-2023-38499?
CVE-2023-38499 is a security vulnerability in Typo3/cms core involving Information Disclosure due to Out-of-scope Site Resolution under CWE-200: Exposure of Sensitive Information to an Unauthorized Actor.
Which Typo3/cms core versions are affected?
Affected versions include releases prior to 9.5.42, 10.4.39, 11.5.30, 12.4.4 across affected packages: typo3/cms-core.
What version fixes CVE-2023-38499?
Upgrading to 9.5.42, 10.4.39, 11.5.30, 12.4.4 (or the latest patched release for your respective branch) resolves the vulnerability.
Is typo3/cms-core affected?
Yes, typo3/cms-core is affected in releases prior to 9.5.42, 10.4.39, 11.5.30, 12.4.4. Upgrade your dependency to 9.5.42, 10.4.39, 11.5.30, 12.4.4 or later.
What is the CVSS score of CVE-2023-38499?
CVE-2023-38499 has a CVSS v3.1 base score of 3.7 (LOW) with vector string CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N.
What CWE is associated with CVE-2023-38499?
CVE-2023-38499 is classified under 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 can I check Packagist dependencies for CVE-2023-38499?
Run the dependency tree command: 'inspect dependencies for typo3/cms-core'. 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-jq6g-4v5m-wm9r",
  "modified" : "2023-08-03T17:57:05Z",
  "published" : "2023-07-25T18:25:52Z",
  "aliases" : [ "CVE-2023-38499" ],
  "summary" : "Information Disclosure due to Out-of-scope Site Resolution",
  "details" : "> ### 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)\n\n### Problem\nIn 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.\n\n### Solution\nUpdate to TYPO3 versions 9.5.42 ELTS, 10.4.39 ELTS, 11.5.30, 12.4.4 that fix the problem described above.\n\n> ℹ️ **Strong security defaults - Manual actions required**\n> Resolving sites by the `id` and `L` HTTP 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 the `page-id 123` is in the scope of the site configured for the `base-url example.org`.\n> The new feature flag `security.frontend.allowInsecureSiteResolutionByQueryParameters` - which is disabled per default - can be used to reactivate the previous behavior.\n\n### Credits\nThanks to Garvin Hicking who reported this issue, and to TYPO3 core & security team members Oliver Hader and Benjamin Franzke who fixed the issue.\n\n### References\n* [TYPO3-CORE-SA-2023-003](https://typo3.org/security/advisory/typo3-core-sa-2023-003)\n",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "typo3/cms-core"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "9.4.0"
      }, {
        "fixed" : "9.5.42"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "typo3/cms-core"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "10.0.0"
      }, {
        "fixed" : "10.4.39"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "typo3/cms-core"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "11.0.0"
      }, {
        "fixed" : "11.5.30"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "typo3/cms-core"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "12.0.0"
      }, {
        "fixed" : "12.4.4"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/TYPO3/typo3/security/advisories/GHSA-jq6g-4v5m-wm9r"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2023-38499"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/TYPO3/typo3/commit/702e2debd4b28f9cdb540544565fe6a8627ccb6a"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/TYPO3/typo3"
  }, {
    "type" : "WEB",
    "url" : "https://typo3.org/security/advisory/typo3-core-sa-2023-003"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-200" ],
    "severity" : "LOW",
    "github_reviewed" : true,
    "github_reviewed_at" : "2023-07-25T18:25:52Z",
    "nvd_published_at" : "2023-07-25T21:15:10Z"
  }
}