ghsa-mppv-79ch-vw6q
Vulnerability from github
Published
2023-06-21 12:30
Modified
2024-04-24 19:44
Severity ?
7.5 (High) - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Summary
Apache Tomcat vulnerable to information leak
Details

A regression in the fix for bug 66512 in Apache Tomcat 11.0.0-M5, 10.1.8, 9.0.74 and 8.5.88 meant that, if a response did not include any HTTP headers no AJP SEND_HEADERS message would be sent for the response which in turn meant that at least one AJP proxy (mod_proxy_ajp) would use the response headers from the previous request leading to an information leak.

Show details on source website

To clipboard 

{
   affected: [
      {
         package: {
            ecosystem: "Maven",
            name: "org.apache.tomcat.embed:tomcat-embed-core",
         },
         ranges: [
            {
               events: [
                  {
                     introduced: "11.0.0-M5",
                  },
                  {
                     fixed: "11.0.0-M6",
                  },
               ],
               type: "ECOSYSTEM",
            },
         ],
         versions: [
            "11.0.0-M5",
         ],
      },
      {
         package: {
            ecosystem: "Maven",
            name: "org.apache.tomcat.embed:tomcat-embed-core",
         },
         ranges: [
            {
               events: [
                  {
                     introduced: "10.1.8",
                  },
                  {
                     fixed: "10.1.9",
                  },
               ],
               type: "ECOSYSTEM",
            },
         ],
         versions: [
            "10.1.8",
         ],
      },
      {
         package: {
            ecosystem: "Maven",
            name: "org.apache.tomcat.embed:tomcat-embed-core",
         },
         ranges: [
            {
               events: [
                  {
                     introduced: "9.0.74",
                  },
                  {
                     fixed: "9.0.75",
                  },
               ],
               type: "ECOSYSTEM",
            },
         ],
         versions: [
            "9.0.74",
         ],
      },
      {
         package: {
            ecosystem: "Maven",
            name: "org.apache.tomcat:tomcat-coyote",
         },
         ranges: [
            {
               events: [
                  {
                     introduced: "8.5.88",
                  },
                  {
                     fixed: "8.5.89",
                  },
               ],
               type: "ECOSYSTEM",
            },
         ],
         versions: [
            "8.5.88",
         ],
      },
   ],
   aliases: [
      "CVE-2023-34981",
   ],
   database_specific: {
      cwe_ids: [
         "CWE-732",
      ],
      github_reviewed: true,
      github_reviewed_at: "2023-06-21T22:06:39Z",
      nvd_published_at: "2023-06-21T11:15:09Z",
      severity: "HIGH",
   },
   details: "A regression in the fix for bug 66512 in Apache Tomcat 11.0.0-M5, 10.1.8, 9.0.74 and 8.5.88 meant that, if a response did not include any HTTP headers no AJP SEND_HEADERS message would be sent for the response which in turn meant that at least one AJP proxy (mod_proxy_ajp) would use the response headers from the previous request leading to an information leak.",
   id: "GHSA-mppv-79ch-vw6q",
   modified: "2024-04-24T19:44:03Z",
   published: "2023-06-21T12:30:19Z",
   references: [
      {
         type: "ADVISORY",
         url: "https://nvd.nist.gov/vuln/detail/CVE-2023-34981",
      },
      {
         type: "WEB",
         url: "https://github.com/apache/tomcat/commit/2214c8030522aa9b2a367dfa5d9acff1a03666ae",
      },
      {
         type: "WEB",
         url: "https://github.com/apache/tomcat/commit/2f0ca2378415f4cf0748f4bc8fa955f41f803fa5",
      },
      {
         type: "WEB",
         url: "https://github.com/apache/tomcat/commit/739c7381aed22b7636351caf885ddc519ab6b442",
      },
      {
         type: "WEB",
         url: "https://github.com/apache/tomcat/commit/f0742f47b98aca943097f7f88e0d1163f57527e3",
      },
      {
         type: "WEB",
         url: "https://bz.apache.org/bugzilla/show_bug.cgi?id=66512",
      },
      {
         type: "WEB",
         url: "https://bz.apache.org/bugzilla/show_bug.cgi?id=66591",
      },
      {
         type: "PACKAGE",
         url: "https://github.com/apache/tomcat",
      },
      {
         type: "WEB",
         url: "https://lists.apache.org/thread/j1ksjh9m9gx1q60rtk1sbzmxhvj5h5qz",
      },
      {
         type: "WEB",
         url: "https://security.netapp.com/advisory/ntap-20230714-0003",
      },
      {
         type: "WEB",
         url: "https://tomcat.apache.org/security-10.html",
      },
      {
         type: "WEB",
         url: "https://tomcat.apache.org/security-11.html",
      },
      {
         type: "WEB",
         url: "https://tomcat.apache.org/security-8.html",
      },
      {
         type: "WEB",
         url: "https://tomcat.apache.org/security-9.html",
      },
   ],
   schema_version: "1.4.0",
   severity: [
      {
         score: "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
         type: "CVSS_V3",
      },
   ],
   summary: "Apache Tomcat vulnerable to information leak",
}


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.