ghsa-3xpj-jgv5-q4vv
Vulnerability from github
Published
2022-05-14 02:55
Modified
2024-02-21 21:26
Summary
Access restriction bypass in Apache Tomcat
Details

Apache Tomcat 7.0.12 and 7.0.13 processes the first request to a servlet without following security constraints that have been configured through annotations, which allows remote attackers to bypass intended access restrictions via HTTP requests. NOTE: this vulnerability exists because of an incomplete fix for CVE-2011-1088, CVE-2011-1183, and CVE-2011-1419.

Show details on source website

To clipboard 

{
   affected: [
      {
         package: {
            ecosystem: "Maven",
            name: "org.apache.tomcat:tomcat",
         },
         ranges: [
            {
               events: [
                  {
                     introduced: "7.0.12",
                  },
                  {
                     fixed: "7.0.14",
                  },
               ],
               type: "ECOSYSTEM",
            },
         ],
      },
   ],
   aliases: [
      "CVE-2011-1582",
   ],
   database_specific: {
      cwe_ids: [],
      github_reviewed: true,
      github_reviewed_at: "2023-02-14T01:01:49Z",
      nvd_published_at: "2011-05-20T22:55:00Z",
      severity: "MODERATE",
   },
   details: "Apache Tomcat 7.0.12 and 7.0.13 processes the first request to a servlet without following security constraints that have been configured through annotations, which allows remote attackers to bypass intended access restrictions via HTTP requests.  NOTE: this vulnerability exists because of an incomplete fix for CVE-2011-1088, CVE-2011-1183, and CVE-2011-1419.",
   id: "GHSA-3xpj-jgv5-q4vv",
   modified: "2024-02-21T21:26:08Z",
   published: "2022-05-14T02:55:47Z",
   references: [
      {
         type: "ADVISORY",
         url: "https://nvd.nist.gov/vuln/detail/CVE-2011-1582",
      },
      {
         type: "WEB",
         url: "https://github.com/apache/tomcat/commit/299b26af66793438c323ea6b18462fa44683080f",
      },
      {
         type: "WEB",
         url: "https://exchange.xforce.ibmcloud.com/vulnerabilities/67515",
      },
      {
         type: "PACKAGE",
         url: "https://github.com/apache/tomcat",
      },
      {
         type: "WEB",
         url: "https://web.archive.org/web/20111110135226/http://www.securityfocus.com/archive/1/518032/100/0/threaded",
      },
      {
         type: "WEB",
         url: "https://web.archive.org/web/20170202135510/http://www.securityfocus.com/bid/47886",
      },
      {
         type: "WEB",
         url: "http://mail-archives.apache.org/mod_mbox/www-announce/201105.mbox/%3C4DD26E30.2060103@apache.org%3E",
      },
      {
         type: "WEB",
         url: "http://securityreason.com/securityalert/8256",
      },
      {
         type: "WEB",
         url: "http://svn.apache.org/viewvc?view=revision&revision=1100832",
      },
      {
         type: "WEB",
         url: "http://tomcat.apache.org/security-7.html#Fixed_in_Apache_Tomcat_7.0.14_%28released_12_May_2011%29",
      },
   ],
   schema_version: "1.4.0",
   severity: [],
   summary: "Access restriction bypass in Apache Tomcat",
}


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.