gsd-2019-12521
Vulnerability from gsd
Modified
2023-12-13 01:23
Details
An issue was discovered in Squid through 4.7. When Squid is parsing ESI, it keeps the ESI elements in ESIContext. ESIContext contains a buffer for holding a stack of ESIElements. When a new ESIElement is parsed, it is added via addStackElement. addStackElement has a check for the number of elements in this buffer, but it's off by 1, leading to a Heap Overflow of 1 element. The overflow is within the same structure so it can't affect adjacent memory blocks, and thus just leads to a crash while processing.
Aliases
Aliases
CVE-2019-12521


To clipboard 

{
   GSD: {
      alias: "CVE-2019-12521",
      description: "An issue was discovered in Squid through 4.7. When Squid is parsing ESI, it keeps the ESI elements in ESIContext. ESIContext contains a buffer for holding a stack of ESIElements. When a new ESIElement is parsed, it is added via addStackElement. addStackElement has a check for the number of elements in this buffer, but it's off by 1, leading to a Heap Overflow of 1 element. The overflow is within the same structure so it can't affect adjacent memory blocks, and thus just leads to a crash while processing.",
      id: "GSD-2019-12521",
      references: [
         "https://www.suse.com/security/cve/CVE-2019-12521.html",
         "https://www.debian.org/security/2020/dsa-4682",
         "https://access.redhat.com/errata/RHSA-2020:4743",
         "https://ubuntu.com/security/CVE-2019-12521",
         "https://security.archlinux.org/CVE-2019-12521",
         "https://alas.aws.amazon.com/cve/html/CVE-2019-12521.html",
         "https://linux.oracle.com/cve/CVE-2019-12521.html",
      ],
   },
   gsd: {
      metadata: {
         exploitCode: "unknown",
         remediation: "unknown",
         reportConfidence: "confirmed",
         type: "vulnerability",
      },
      osvSchema: {
         aliases: [
            "CVE-2019-12521",
         ],
         details: "An issue was discovered in Squid through 4.7. When Squid is parsing ESI, it keeps the ESI elements in ESIContext. ESIContext contains a buffer for holding a stack of ESIElements. When a new ESIElement is parsed, it is added via addStackElement. addStackElement has a check for the number of elements in this buffer, but it's off by 1, leading to a Heap Overflow of 1 element. The overflow is within the same structure so it can't affect adjacent memory blocks, and thus just leads to a crash while processing.",
         id: "GSD-2019-12521",
         modified: "2023-12-13T01:23:43.727833Z",
         schema_version: "1.4.0",
      },
   },
   namespaces: {
      "cve.org": {
         CVE_data_meta: {
            ASSIGNER: "cve@mitre.org",
            ID: "CVE-2019-12521",
            STATE: "PUBLIC",
         },
         affects: {
            vendor: {
               vendor_data: [
                  {
                     product: {
                        product_data: [
                           {
                              product_name: "n/a",
                              version: {
                                 version_data: [
                                    {
                                       version_value: "n/a",
                                    },
                                 ],
                              },
                           },
                        ],
                     },
                     vendor_name: "n/a",
                  },
               ],
            },
         },
         data_format: "MITRE",
         data_type: "CVE",
         data_version: "4.0",
         description: {
            description_data: [
               {
                  lang: "eng",
                  value: "An issue was discovered in Squid through 4.7. When Squid is parsing ESI, it keeps the ESI elements in ESIContext. ESIContext contains a buffer for holding a stack of ESIElements. When a new ESIElement is parsed, it is added via addStackElement. addStackElement has a check for the number of elements in this buffer, but it's off by 1, leading to a Heap Overflow of 1 element. The overflow is within the same structure so it can't affect adjacent memory blocks, and thus just leads to a crash while processing.",
               },
            ],
         },
         problemtype: {
            problemtype_data: [
               {
                  description: [
                     {
                        lang: "eng",
                        value: "n/a",
                     },
                  ],
               },
            ],
         },
         references: {
            reference_data: [
               {
                  name: "https://gitlab.com/jeriko.one/security/-/blob/master/squid/CVEs/CVE-2019-12521.txt",
                  refsource: "MISC",
                  url: "https://gitlab.com/jeriko.one/security/-/blob/master/squid/CVEs/CVE-2019-12521.txt",
               },
               {
                  name: "[oss-security] 20200423 [ADVISORY] SQUID-2019:12 Multiple issues in ESI Response processing",
                  refsource: "MLIST",
                  url: "http://www.openwall.com/lists/oss-security/2020/04/23/1",
               },
               {
                  name: "DSA-4682",
                  refsource: "DEBIAN",
                  url: "https://www.debian.org/security/2020/dsa-4682",
               },
               {
                  name: "openSUSE-SU-2020:0623",
                  refsource: "SUSE",
                  url: "http://lists.opensuse.org/opensuse-security-announce/2020-05/msg00018.html",
               },
               {
                  name: "GLSA-202005-05",
                  refsource: "GENTOO",
                  url: "https://security.gentoo.org/glsa/202005-05",
               },
               {
                  name: "USN-4356-1",
                  refsource: "UBUNTU",
                  url: "https://usn.ubuntu.com/4356-1/",
               },
               {
                  name: "[debian-lts-announce] 20200710 [SECURITY] [DLA 2278-1] squid3 security update",
                  refsource: "MLIST",
                  url: "https://lists.debian.org/debian-lts-announce/2020/07/msg00009.html",
               },
               {
                  name: "https://security.netapp.com/advisory/ntap-20210205-0006/",
                  refsource: "CONFIRM",
                  url: "https://security.netapp.com/advisory/ntap-20210205-0006/",
               },
            ],
         },
      },
      "nvd.nist.gov": {
         configurations: {
            CVE_data_version: "4.0",
            nodes: [
               {
                  children: [],
                  cpe_match: [
                     {
                        cpe23Uri: "cpe:2.3:a:squid-cache:squid:*:*:*:*:*:*:*:*",
                        cpe_name: [],
                        versionEndIncluding: "3.5.28",
                        versionStartIncluding: "3.0",
                        vulnerable: true,
                     },
                     {
                        cpe23Uri: "cpe:2.3:a:squid-cache:squid:*:*:*:*:*:*:*:*",
                        cpe_name: [],
                        versionEndIncluding: "4.7",
                        versionStartIncluding: "4.0",
                        vulnerable: true,
                     },
                     {
                        cpe23Uri: "cpe:2.3:a:squid-cache:squid:*:*:*:*:*:*:*:*",
                        cpe_name: [],
                        versionEndIncluding: "5.0.1",
                        versionStartIncluding: "5.0",
                        vulnerable: true,
                     },
                  ],
                  operator: "OR",
               },
               {
                  children: [],
                  cpe_match: [
                     {
                        cpe23Uri: "cpe:2.3:o:canonical:ubuntu_linux:16.04:*:*:*:lts:*:*:*",
                        cpe_name: [],
                        vulnerable: true,
                     },
                     {
                        cpe23Uri: "cpe:2.3:o:canonical:ubuntu_linux:18.04:*:*:*:lts:*:*:*",
                        cpe_name: [],
                        vulnerable: true,
                     },
                     {
                        cpe23Uri: "cpe:2.3:o:canonical:ubuntu_linux:19.10:*:*:*:*:*:*:*",
                        cpe_name: [],
                        vulnerable: true,
                     },
                     {
                        cpe23Uri: "cpe:2.3:o:canonical:ubuntu_linux:20.04:*:*:*:lts:*:*:*",
                        cpe_name: [],
                        vulnerable: true,
                     },
                  ],
                  operator: "OR",
               },
               {
                  children: [],
                  cpe_match: [
                     {
                        cpe23Uri: "cpe:2.3:o:debian:debian_linux:9.0:*:*:*:*:*:*:*",
                        cpe_name: [],
                        vulnerable: true,
                     },
                     {
                        cpe23Uri: "cpe:2.3:o:debian:debian_linux:10.0:*:*:*:*:*:*:*",
                        cpe_name: [],
                        vulnerable: true,
                     },
                  ],
                  operator: "OR",
               },
               {
                  children: [],
                  cpe_match: [
                     {
                        cpe23Uri: "cpe:2.3:o:opensuse:leap:15.1:*:*:*:*:*:*:*",
                        cpe_name: [],
                        vulnerable: true,
                     },
                  ],
                  operator: "OR",
               },
            ],
         },
         cve: {
            CVE_data_meta: {
               ASSIGNER: "cve@mitre.org",
               ID: "CVE-2019-12521",
            },
            data_format: "MITRE",
            data_type: "CVE",
            data_version: "4.0",
            description: {
               description_data: [
                  {
                     lang: "en",
                     value: "An issue was discovered in Squid through 4.7. When Squid is parsing ESI, it keeps the ESI elements in ESIContext. ESIContext contains a buffer for holding a stack of ESIElements. When a new ESIElement is parsed, it is added via addStackElement. addStackElement has a check for the number of elements in this buffer, but it's off by 1, leading to a Heap Overflow of 1 element. The overflow is within the same structure so it can't affect adjacent memory blocks, and thus just leads to a crash while processing.",
                  },
               ],
            },
            problemtype: {
               problemtype_data: [
                  {
                     description: [
                        {
                           lang: "en",
                           value: "CWE-787",
                        },
                        {
                           lang: "en",
                           value: "CWE-193",
                        },
                     ],
                  },
               ],
            },
            references: {
               reference_data: [
                  {
                     name: "https://gitlab.com/jeriko.one/security/-/blob/master/squid/CVEs/CVE-2019-12521.txt",
                     refsource: "MISC",
                     tags: [
                        "Third Party Advisory",
                     ],
                     url: "https://gitlab.com/jeriko.one/security/-/blob/master/squid/CVEs/CVE-2019-12521.txt",
                  },
                  {
                     name: "[oss-security] 20200423 [ADVISORY] SQUID-2019:12 Multiple issues in ESI Response processing",
                     refsource: "MLIST",
                     tags: [
                        "Mailing List",
                        "Patch",
                        "Third Party Advisory",
                     ],
                     url: "http://www.openwall.com/lists/oss-security/2020/04/23/1",
                  },
                  {
                     name: "DSA-4682",
                     refsource: "DEBIAN",
                     tags: [
                        "Third Party Advisory",
                     ],
                     url: "https://www.debian.org/security/2020/dsa-4682",
                  },
                  {
                     name: "openSUSE-SU-2020:0623",
                     refsource: "SUSE",
                     tags: [
                        "Mailing List",
                        "Third Party Advisory",
                     ],
                     url: "http://lists.opensuse.org/opensuse-security-announce/2020-05/msg00018.html",
                  },
                  {
                     name: "GLSA-202005-05",
                     refsource: "GENTOO",
                     tags: [
                        "Third Party Advisory",
                     ],
                     url: "https://security.gentoo.org/glsa/202005-05",
                  },
                  {
                     name: "USN-4356-1",
                     refsource: "UBUNTU",
                     tags: [
                        "Third Party Advisory",
                     ],
                     url: "https://usn.ubuntu.com/4356-1/",
                  },
                  {
                     name: "[debian-lts-announce] 20200710 [SECURITY] [DLA 2278-1] squid3 security update",
                     refsource: "MLIST",
                     tags: [
                        "Mailing List",
                        "Third Party Advisory",
                     ],
                     url: "https://lists.debian.org/debian-lts-announce/2020/07/msg00009.html",
                  },
                  {
                     name: "https://security.netapp.com/advisory/ntap-20210205-0006/",
                     refsource: "CONFIRM",
                     tags: [
                        "Third Party Advisory",
                     ],
                     url: "https://security.netapp.com/advisory/ntap-20210205-0006/",
                  },
               ],
            },
         },
         impact: {
            baseMetricV2: {
               acInsufInfo: false,
               cvssV2: {
                  accessComplexity: "MEDIUM",
                  accessVector: "NETWORK",
                  authentication: "NONE",
                  availabilityImpact: "PARTIAL",
                  baseScore: 4.3,
                  confidentialityImpact: "NONE",
                  integrityImpact: "NONE",
                  vectorString: "AV:N/AC:M/Au:N/C:N/I:N/A:P",
                  version: "2.0",
               },
               exploitabilityScore: 8.6,
               impactScore: 2.9,
               obtainAllPrivilege: false,
               obtainOtherPrivilege: false,
               obtainUserPrivilege: false,
               severity: "MEDIUM",
               userInteractionRequired: false,
            },
            baseMetricV3: {
               cvssV3: {
                  attackComplexity: "HIGH",
                  attackVector: "NETWORK",
                  availabilityImpact: "HIGH",
                  baseScore: 5.9,
                  baseSeverity: "MEDIUM",
                  confidentialityImpact: "NONE",
                  integrityImpact: "NONE",
                  privilegesRequired: "NONE",
                  scope: "UNCHANGED",
                  userInteraction: "NONE",
                  vectorString: "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H",
                  version: "3.1",
               },
               exploitabilityScore: 2.2,
               impactScore: 3.6,
            },
         },
         lastModifiedDate: "2021-07-21T11:39Z",
         publishedDate: "2020-04-15T19:15Z",
      },
   },
}


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.