ghsa-558x-2xjg-6232
Vulnerability from github
Published
2022-04-03 00:01
Modified
2023-03-28 22:26
Summary
Allocation of Resources Without Limits or Throttling in Spring Framework
Details

In Spring Framework versions 5.3.0 - 5.3.16, 5.2.0.RELEASE - 5.2.19.RELEASE, and older unsupported versions, it is possible for a user to provide a specially crafted SpEL expression that may cause a denial of service condition.

Show details on source website


{
   affected: [
      {
         package: {
            ecosystem: "Maven",
            name: "org.springframework:spring-expression",
         },
         ranges: [
            {
               events: [
                  {
                     introduced: "5.3.0",
                  },
                  {
                     fixed: "5.3.17",
                  },
               ],
               type: "ECOSYSTEM",
            },
         ],
      },
      {
         package: {
            ecosystem: "Maven",
            name: "org.springframework:spring-expression",
         },
         ranges: [
            {
               events: [
                  {
                     introduced: "0",
                  },
                  {
                     fixed: "5.2.20.RELEASE",
                  },
               ],
               type: "ECOSYSTEM",
            },
         ],
      },
   ],
   aliases: [
      "CVE-2022-22950",
   ],
   database_specific: {
      cwe_ids: [
         "CWE-770",
      ],
      github_reviewed: true,
      github_reviewed_at: "2022-04-05T18:46:34Z",
      nvd_published_at: "2022-04-01T23:15:00Z",
      severity: "MODERATE",
   },
   details: "In Spring Framework versions 5.3.0 - 5.3.16, 5.2.0.RELEASE - 5.2.19.RELEASE, and older unsupported versions, it is possible for a user to provide a specially crafted SpEL expression that may cause a denial of service condition.",
   id: "GHSA-558x-2xjg-6232",
   modified: "2023-03-28T22:26:10Z",
   published: "2022-04-03T00:01:00Z",
   references: [
      {
         type: "ADVISORY",
         url: "https://nvd.nist.gov/vuln/detail/CVE-2022-22950",
      },
      {
         type: "WEB",
         url: "https://github.com/spring-projects/spring-framework/issues/28145",
      },
      {
         type: "WEB",
         url: "https://github.com/spring-projects/spring-framework/issues/28257",
      },
      {
         type: "WEB",
         url: "https://github.com/spring-projects/spring-framework/commit/83ac65915871067c39a4fb255e0d484c785c0c11",
      },
      {
         type: "PACKAGE",
         url: "https://github.com/spring-projects/spring-framework",
      },
      {
         type: "WEB",
         url: "https://github.com/spring-projects/spring-framework/releases/tag/v5.2.20.RELEASE",
      },
      {
         type: "WEB",
         url: "https://github.com/spring-projects/spring-framework/releases/tag/v5.3.17",
      },
      {
         type: "WEB",
         url: "https://tanzu.vmware.com/security/cve-2022-22950",
      },
   ],
   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.