ghsa-rqph-vqwm-22vc
Vulnerability from github
Published
2022-05-13 00:00
Modified
2024-03-14 20:54
Summary
Allocation of Resources Without Limits or Throttling in Spring Framework
Details

In spring framework versions prior to 5.3.20+ , 5.2.22+ and old unsupported versions, application with a STOMP over WebSocket endpoint is vulnerable to a denial of service attack by an authenticated user.

Show details on source website


{
   affected: [
      {
         package: {
            ecosystem: "Maven",
            name: "org.springframework:spring-messaging",
         },
         ranges: [
            {
               events: [
                  {
                     introduced: "5.3.0",
                  },
                  {
                     fixed: "5.3.20",
                  },
               ],
               type: "ECOSYSTEM",
            },
         ],
      },
      {
         database_specific: {
            last_known_affected_version_range: "<= 5.2.21.RELEASE",
         },
         package: {
            ecosystem: "Maven",
            name: "org.springframework:spring-messaging",
         },
         ranges: [
            {
               events: [
                  {
                     introduced: "0",
                  },
                  {
                     fixed: "5.2.22.RELEASE",
                  },
               ],
               type: "ECOSYSTEM",
            },
         ],
      },
   ],
   aliases: [
      "CVE-2022-22971",
   ],
   database_specific: {
      cwe_ids: [
         "CWE-770",
      ],
      github_reviewed: true,
      github_reviewed_at: "2022-05-24T22:24:29Z",
      nvd_published_at: "2022-05-12T20:15:00Z",
      severity: "MODERATE",
   },
   details: "In spring framework versions prior to 5.3.20+ , 5.2.22+ and old unsupported versions, application with a STOMP over WebSocket endpoint is vulnerable to a denial of service attack by an authenticated user.",
   id: "GHSA-rqph-vqwm-22vc",
   modified: "2024-03-14T20:54:19Z",
   published: "2022-05-13T00:00:29Z",
   references: [
      {
         type: "ADVISORY",
         url: "https://nvd.nist.gov/vuln/detail/CVE-2022-22971",
      },
      {
         type: "WEB",
         url: "https://github.com/spring-projects/spring-framework/commit/159a99bbafdd6c01871228113d7042c3f83f360f",
      },
      {
         type: "WEB",
         url: "https://github.com/spring-projects/spring-framework/commit/dc2947c52df18d5e99cad03383f7d6ba13d031fd",
      },
      {
         type: "PACKAGE",
         url: "https://github.com/spring-projects/spring-framework",
      },
      {
         type: "WEB",
         url: "https://security.netapp.com/advisory/ntap-20220616-0003",
      },
      {
         type: "WEB",
         url: "https://tanzu.vmware.com/security/cve-2022-22971",
      },
      {
         type: "WEB",
         url: "https://www.oracle.com/security-alerts/cpujul2022.html",
      },
   ],
   schema_version: "1.4.0",
   severity: [
      {
         score: "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
         type: "CVSS_V3",
      },
   ],
   summary: "Allocation of Resources Without Limits or Throttling in Spring Framework",
}


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.


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.