ghsa-3vmm-7h4j-69rm
Vulnerability from github
Published
2023-11-14 18:30
Modified
2023-12-15 22:14
Summary
TYPO3 vulnerable to Weak Authentication in Session Handling
Details

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

Problem

Given that there are at least two different sites in the same TYPO3 installation - for instance first.example.org and second.example.com - then a session cookie generated for the first site can be reused on the second site without requiring additional authentication.

This vulnerability primarily affects the frontend of the website. It's important to note that exploiting this vulnerability requires a valid user account.

Solution

Update to TYPO3 versions 8.7.55 ELTS, 9.5.44 ELTS, 10.4.41 ELTS, 11.5.33, 12.4.8 that fix the problem described above.

Credits

Thanks to Rémy Daniel who reported this issue, and to TYPO3 core & security team member Benjamin Franzke who fixed the issue.

References

Show details on source website


{
   affected: [
      {
         database_specific: {
            last_known_affected_version_range: "<= 8.7.54",
         },
         package: {
            ecosystem: "Packagist",
            name: "typo3/cms-core",
         },
         ranges: [
            {
               events: [
                  {
                     introduced: "8.0.0",
                  },
                  {
                     fixed: "8.7.55",
                  },
               ],
               type: "ECOSYSTEM",
            },
         ],
      },
      {
         database_specific: {
            last_known_affected_version_range: "<= 9.5.43",
         },
         package: {
            ecosystem: "Packagist",
            name: "typo3/cms-core",
         },
         ranges: [
            {
               events: [
                  {
                     introduced: "9.0.0",
                  },
                  {
                     fixed: "9.5.44",
                  },
               ],
               type: "ECOSYSTEM",
            },
         ],
      },
      {
         database_specific: {
            last_known_affected_version_range: "<= 10.4.40",
         },
         package: {
            ecosystem: "Packagist",
            name: "typo3/cms-core",
         },
         ranges: [
            {
               events: [
                  {
                     introduced: "10.0.0",
                  },
                  {
                     fixed: "10.4.41",
                  },
               ],
               type: "ECOSYSTEM",
            },
         ],
      },
      {
         database_specific: {
            last_known_affected_version_range: "<= 11.5.32",
         },
         package: {
            ecosystem: "Packagist",
            name: "typo3/cms-core",
         },
         ranges: [
            {
               events: [
                  {
                     introduced: "11.0.0",
                  },
                  {
                     fixed: "11.5.33",
                  },
               ],
               type: "ECOSYSTEM",
            },
         ],
      },
      {
         database_specific: {
            last_known_affected_version_range: "<= 12.4.7",
         },
         package: {
            ecosystem: "Packagist",
            name: "typo3/cms-core",
         },
         ranges: [
            {
               events: [
                  {
                     introduced: "12.0.0",
                  },
                  {
                     fixed: "12.4.8",
                  },
               ],
               type: "ECOSYSTEM",
            },
         ],
      },
   ],
   aliases: [
      "CVE-2023-47127",
   ],
   database_specific: {
      cwe_ids: [
         "CWE-287",
         "CWE-302",
      ],
      github_reviewed: true,
      github_reviewed_at: "2023-11-14T18:30:21Z",
      nvd_published_at: "2023-11-14T20:15:08Z",
      severity: "MODERATE",
   },
   details: "> ### CVSS: `CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N/E:X/RL:O/RC:C` (4.0)\n\n### Problem\nGiven that there are at least two different sites in the same TYPO3 installation - for instance _first.example.org_ and _second.example.com_ - then a session cookie generated for the first site can be reused on the second site without requiring additional authentication.\n\nThis vulnerability primarily affects the frontend of the website. It's important to note that exploiting this vulnerability requires a valid user account.\n\n### Solution\nUpdate to TYPO3 versions 8.7.55 ELTS, 9.5.44 ELTS, 10.4.41 ELTS, 11.5.33, 12.4.8 that fix the problem described above.\n\n### Credits\nThanks to Rémy Daniel who reported this issue, and to TYPO3 core & security team member Benjamin Franzke who fixed the issue.\n\n### References\n* [TYPO3-CORE-SA-2023-006](https://typo3.org/security/advisory/typo3-core-sa-2023-006)\n",
   id: "GHSA-3vmm-7h4j-69rm",
   modified: "2023-12-15T22:14:29Z",
   published: "2023-11-14T18:30:21Z",
   references: [
      {
         type: "WEB",
         url: "https://github.com/TYPO3/typo3/security/advisories/GHSA-3vmm-7h4j-69rm",
      },
      {
         type: "ADVISORY",
         url: "https://nvd.nist.gov/vuln/detail/CVE-2023-47127",
      },
      {
         type: "WEB",
         url: "https://github.com/TYPO3/typo3/commit/535dfbdc54fd5362e0bc08d911db44eac7f64019",
      },
      {
         type: "WEB",
         url: "https://github.com/FriendsOfPHP/security-advisories/blob/master/typo3/cms-core/CVE-2023-47127.yaml",
      },
      {
         type: "PACKAGE",
         url: "https://github.com/TYPO3/typo3",
      },
      {
         type: "WEB",
         url: "https://typo3.org/security/advisory/typo3-core-sa-2023-006",
      },
   ],
   schema_version: "1.4.0",
   severity: [
      {
         score: "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N",
         type: "CVSS_V3",
      },
   ],
   summary: "TYPO3 vulnerable to Weak Authentication in Session Handling",
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.