ghsa-2rxh-h6h9-qrqc
Vulnerability from github
Published
2020-05-13 23:18
Modified
2021-01-08 20:16
Severity ?
8.7 (High) - CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:H
Summary
Class destructors causing side-effects when being unserialized in TYPO3 CMS
Details

Calling unserialize() on malicious user-submitted content can result in the following scenarios: - trigger deletion of arbitrary directory in file system (if writable for web server) - trigger message submission via email using identity of web site (mail relay)

Another insecure deserialization vulnerability is required to actually exploit mentioned aspects.

Update to TYPO3 versions 9.5.17 or 10.4.2 that fix the problem described.

References

  • https://typo3.org/security/advisory/typo3-core-sa-2020-004
Show details on source website

To clipboard 

{
   affected: [
      {
         package: {
            ecosystem: "Packagist",
            name: "typo3/cms-core",
         },
         ranges: [
            {
               events: [
                  {
                     introduced: "9.0.0",
                  },
                  {
                     fixed: "9.5.17",
                  },
               ],
               type: "ECOSYSTEM",
            },
         ],
      },
      {
         package: {
            ecosystem: "Packagist",
            name: "typo3/cms-core",
         },
         ranges: [
            {
               events: [
                  {
                     introduced: "10.0.0",
                  },
                  {
                     fixed: "10.4.2",
                  },
               ],
               type: "ECOSYSTEM",
            },
         ],
      },
      {
         package: {
            ecosystem: "Packagist",
            name: "typo3/cms",
         },
         ranges: [
            {
               events: [
                  {
                     introduced: "10.0.0",
                  },
                  {
                     fixed: "10.4.2",
                  },
               ],
               type: "ECOSYSTEM",
            },
         ],
      },
      {
         package: {
            ecosystem: "Packagist",
            name: "typo3/cms",
         },
         ranges: [
            {
               events: [
                  {
                     introduced: "9.0.0",
                  },
                  {
                     fixed: "9.5.17",
                  },
               ],
               type: "ECOSYSTEM",
            },
         ],
      },
   ],
   aliases: [
      "CVE-2020-11066",
   ],
   database_specific: {
      cwe_ids: [
         "CWE-1321",
         "CWE-915",
      ],
      github_reviewed: true,
      github_reviewed_at: "2020-05-13T23:17:19Z",
      nvd_published_at: "2020-05-14T00:15:00Z",
      severity: "HIGH",
   },
   details: "Calling unserialize() on malicious user-submitted content can result in the following scenarios:\n- trigger deletion of arbitrary directory in file system (if writable for web server)\n- trigger message submission via email using identity of web site (mail relay)\n\nAnother insecure deserialization vulnerability is required to actually exploit mentioned aspects.\n\nUpdate to TYPO3 versions 9.5.17 or 10.4.2 that fix the problem described.\n\n### References\n* https://typo3.org/security/advisory/typo3-core-sa-2020-004",
   id: "GHSA-2rxh-h6h9-qrqc",
   modified: "2021-01-08T20:16:34Z",
   published: "2020-05-13T23:18:38Z",
   references: [
      {
         type: "WEB",
         url: "https://github.com/TYPO3/TYPO3.CMS/security/advisories/GHSA-2rxh-h6h9-qrqc",
      },
      {
         type: "ADVISORY",
         url: "https://nvd.nist.gov/vuln/detail/CVE-2020-11066",
      },
      {
         type: "WEB",
         url: "https://github.com/FriendsOfPHP/security-advisories/blob/master/typo3/cms-core/CVE-2020-11066.yaml",
      },
      {
         type: "WEB",
         url: "https://github.com/FriendsOfPHP/security-advisories/blob/master/typo3/cms/CVE-2020-11066.yaml",
      },
      {
         type: "WEB",
         url: "https://typo3.org/security/advisory/typo3-core-sa-2020-004",
      },
   ],
   schema_version: "1.4.0",
   severity: [
      {
         score: "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:H",
         type: "CVSS_V3",
      },
   ],
   summary: "Class destructors causing side-effects when being unserialized in TYPO3 CMS",
}


Log in or create an account to share your comment.

Security Advisory comment format.

This schema specifies the format of a comment related to a security advisory.

UUIDv4 of the comment
UUIDv4 of the Vulnerability-Lookup instance
When the comment was created originally
When the comment was last updated
Title of the comment
Description of the comment
The identifier of the vulnerability (CVE ID, GHSA-ID, PYSEC ID, etc.).



Tags
Taxonomy of the tags.




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.