gsd-2022-2576
Vulnerability from gsd
Modified
2023-12-13 01:19
Details
In Eclipse Californium version 2.0.0 to 2.7.2 and 3.0.0-3.5.0 a DTLS resumption handshake falls back to a DTLS full handshake on a parameter mismatch without using a HelloVerifyRequest. Especially, if used with certificate based cipher suites, that results in message amplification (DDoS other peers) and high CPU load (DoS own peer). The misbehavior occurs only with DTLS_VERIFY_PEERS_ON_RESUMPTION_THRESHOLD values larger than 0.
Aliases
Aliases
CVE-2022-2576


To clipboard 

{
   GSD: {
      alias: "CVE-2022-2576",
      description: "In Eclipse Californium version 2.0.0 to 2.7.2 and 3.0.0-3.5.0 a DTLS resumption handshake falls back to a DTLS full handshake on a parameter mismatch without using a HelloVerifyRequest. Especially, if used with certificate based cipher suites, that results in message amplification (DDoS other peers) and high CPU load (DoS own peer). The misbehavior occurs only with DTLS_VERIFY_PEERS_ON_RESUMPTION_THRESHOLD values larger than 0.",
      id: "GSD-2022-2576",
   },
   gsd: {
      metadata: {
         exploitCode: "unknown",
         remediation: "unknown",
         reportConfidence: "confirmed",
         type: "vulnerability",
      },
      osvSchema: {
         aliases: [
            "CVE-2022-2576",
         ],
         details: "In Eclipse Californium version 2.0.0 to 2.7.2 and 3.0.0-3.5.0 a DTLS resumption handshake falls back to a DTLS full handshake on a parameter mismatch without using a HelloVerifyRequest. Especially, if used with certificate based cipher suites, that results in message amplification (DDoS other peers) and high CPU load (DoS own peer). The misbehavior occurs only with DTLS_VERIFY_PEERS_ON_RESUMPTION_THRESHOLD values larger than 0.",
         id: "GSD-2022-2576",
         modified: "2023-12-13T01:19:19.785744Z",
         schema_version: "1.4.0",
      },
   },
   namespaces: {
      "cve.org": {
         CVE_data_meta: {
            ASSIGNER: "security@eclipse.org",
            ID: "CVE-2022-2576",
            STATE: "PUBLIC",
         },
         affects: {
            vendor: {
               vendor_data: [
                  {
                     product: {
                        product_data: [
                           {
                              product_name: "Eclipse Californium",
                              version: {
                                 version_data: [
                                    {
                                       version_affected: ">=",
                                       version_value: "2.0.0",
                                    },
                                    {
                                       version_affected: "<=",
                                       version_value: "2.7.2",
                                    },
                                    {
                                       version_affected: ">=",
                                       version_value: "3.0.0",
                                    },
                                    {
                                       version_affected: "<=",
                                       version_value: "3.5.0",
                                    },
                                 ],
                              },
                           },
                        ],
                     },
                     vendor_name: "The Eclipse Foundation",
                  },
               ],
            },
         },
         data_format: "MITRE",
         data_type: "CVE",
         data_version: "4.0",
         description: {
            description_data: [
               {
                  lang: "eng",
                  value: "In Eclipse Californium version 2.0.0 to 2.7.2 and 3.0.0-3.5.0 a DTLS resumption handshake falls back to a DTLS full handshake on a parameter mismatch without using a HelloVerifyRequest. Especially, if used with certificate based cipher suites, that results in message amplification (DDoS other peers) and high CPU load (DoS own peer). The misbehavior occurs only with DTLS_VERIFY_PEERS_ON_RESUMPTION_THRESHOLD values larger than 0.",
               },
            ],
         },
         problemtype: {
            problemtype_data: [
               {
                  description: [
                     {
                        lang: "eng",
                        value: "CWE-408: Incorrect Behavior Order: Early Amplification",
                     },
                  ],
               },
            ],
         },
         references: {
            reference_data: [
               {
                  name: "https://bugs.eclipse.org/580018",
                  refsource: "CONFIRM",
                  url: "https://bugs.eclipse.org/580018",
               },
            ],
         },
      },
      "gitlab.com": {
         advisories: [
            {
               affected_range: "[2.0.0,2.7.2],[3.0.0,3.5.0]",
               affected_versions: "All versions starting from 2.0.0 up to 2.7.2, all versions starting from 3.0.0 up to 3.5.0",
               cvss_v3: "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
               cwe_ids: [
                  "CWE-1035",
                  "CWE-937",
               ],
               date: "2022-08-05",
               description: "In Eclipse Californium version 2.0.0 to 2.7.2 and 3.0.0-3.5.0 a DTLS resumption handshake falls back to a DTLS full handshake on a parameter mismatch without using a HelloVerifyRequest. Especially, if used with certificate based cipher suites, that results in message amplification (DDoS other peers) and high CPU load (DoS own peer). The misbehavior occurs only with DTLS_VERIFY_PEERS_ON_RESUMPTION_THRESHOLD values larger than 0.",
               fixed_versions: [
                  "2.7.3",
                  "3.6.0",
               ],
               identifier: "CVE-2022-2576",
               identifiers: [
                  "CVE-2022-2576",
               ],
               not_impacted: "All versions before 2.0.0, all versions after 2.7.2 before 3.0.0, all versions after 3.5.0",
               package_slug: "maven/org.eclipse.californium/californium-core",
               pubdate: "2022-07-29",
               solution: "Upgrade to versions 2.7.3, 3.6.0 or above.",
               title: "Uncontrolled Resource Consumption",
               urls: [
                  "https://nvd.nist.gov/vuln/detail/CVE-2022-2576",
                  "https://bugs.eclipse.org/580018",
               ],
               uuid: "c1f7b201-2b10-4ca4-8a88-edfdbbb1c459",
            },
         ],
      },
      "nvd.nist.gov": {
         configurations: {
            CVE_data_version: "4.0",
            nodes: [
               {
                  children: [],
                  cpe_match: [
                     {
                        cpe23Uri: "cpe:2.3:a:eclipse:californium:*:*:*:*:*:*:*:*",
                        cpe_name: [],
                        versionEndIncluding: "2.7.2",
                        versionStartIncluding: "2.0.0",
                        vulnerable: true,
                     },
                     {
                        cpe23Uri: "cpe:2.3:a:eclipse:californium:*:*:*:*:*:*:*:*",
                        cpe_name: [],
                        versionEndIncluding: "3.5.0",
                        versionStartIncluding: "3.0.0",
                        vulnerable: true,
                     },
                  ],
                  operator: "OR",
               },
            ],
         },
         cve: {
            CVE_data_meta: {
               ASSIGNER: "security@eclipse.org",
               ID: "CVE-2022-2576",
            },
            data_format: "MITRE",
            data_type: "CVE",
            data_version: "4.0",
            description: {
               description_data: [
                  {
                     lang: "en",
                     value: "In Eclipse Californium version 2.0.0 to 2.7.2 and 3.0.0-3.5.0 a DTLS resumption handshake falls back to a DTLS full handshake on a parameter mismatch without using a HelloVerifyRequest. Especially, if used with certificate based cipher suites, that results in message amplification (DDoS other peers) and high CPU load (DoS own peer). The misbehavior occurs only with DTLS_VERIFY_PEERS_ON_RESUMPTION_THRESHOLD values larger than 0.",
                  },
               ],
            },
            problemtype: {
               problemtype_data: [
                  {
                     description: [
                        {
                           lang: "en",
                           value: "NVD-CWE-noinfo",
                        },
                     ],
                  },
               ],
            },
            references: {
               reference_data: [
                  {
                     name: "https://bugs.eclipse.org/580018",
                     refsource: "CONFIRM",
                     tags: [
                        "Exploit",
                        "Issue Tracking",
                        "Vendor Advisory",
                     ],
                     url: "https://bugs.eclipse.org/580018",
                  },
               ],
            },
         },
         impact: {
            baseMetricV3: {
               cvssV3: {
                  attackComplexity: "LOW",
                  attackVector: "NETWORK",
                  availabilityImpact: "HIGH",
                  baseScore: 7.5,
                  baseSeverity: "HIGH",
                  confidentialityImpact: "NONE",
                  integrityImpact: "NONE",
                  privilegesRequired: "NONE",
                  scope: "UNCHANGED",
                  userInteraction: "NONE",
                  vectorString: "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
                  version: "3.1",
               },
               exploitabilityScore: 3.9,
               impactScore: 3.6,
            },
         },
         lastModifiedDate: "2022-08-05T16:13Z",
         publishedDate: "2022-07-29T14: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.