fkie_cve-2025-24970
Vulnerability from fkie_nvd
Published
2025-02-10 22:15
Modified
2025-02-21 18:15
Severity ?
7.5 (High) - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Summary
Netty, an asynchronous, event-driven network application framework, has a vulnerability starting in version 4.1.91.Final and prior to version 4.1.118.Final. When a special crafted packet is received via SslHandler it doesn't correctly handle validation of such a packet in all cases which can lead to a native crash. Version 4.1.118.Final contains a patch. As workaround its possible to either disable the usage of the native SSLEngine or change the code manually.
References
security-advisories@github.comhttps://github.com/netty/netty/commit/87f40725155b2f89adfde68c7732f97c153676c4
security-advisories@github.comhttps://github.com/netty/netty/security/advisories/GHSA-4g8c-wm8x-jfhw
af854a3a-2127-422b-91ae-364da2661108https://security.netapp.com/advisory/ntap-20250221-0005/
134c704f-9b21-4f2e-91b3-4a467353bcc0https://github.com/netty/netty/security/advisories/GHSA-4g8c-wm8x-jfhw
Impacted products
Vendor Product Version


To clipboard 

{
   cveTags: [],
   descriptions: [
      {
         lang: "en",
         value: "Netty, an asynchronous, event-driven network application framework, has a vulnerability starting in version 4.1.91.Final and prior to version 4.1.118.Final. When a special crafted packet is received via SslHandler it doesn't correctly handle validation of such a packet in all cases which can lead to a native crash. Version 4.1.118.Final contains a patch. As workaround its possible to either disable the usage of the native SSLEngine or change the code manually.",
      },
      {
         lang: "es",
         value: "Netty, un framework de aplicación de red asincrónico y controlado por eventos, tiene una vulnerabilidad a partir de la versión 4.1.91.Final y anteriores a la versión 4.1.118.Final. Cuando se recibe un paquete especialmente manipulado a través de SslHandler, no se gestiona correctamente la validación de dicho paquete en todos los casos, lo que puede provocar un bloqueo nativo. La versión 4.1.118.Final contiene un parche. Como workaround, es posible deshabilitar el uso de SSLEngine nativo o cambiar el código manualmente. ",
      },
   ],
   id: "CVE-2025-24970",
   lastModified: "2025-02-21T18:15:36.383",
   metrics: {
      cvssMetricV31: [
         {
            cvssData: {
               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,
            source: "security-advisories@github.com",
            type: "Secondary",
         },
      ],
   },
   published: "2025-02-10T22:15:38.057",
   references: [
      {
         source: "security-advisories@github.com",
         url: "https://github.com/netty/netty/commit/87f40725155b2f89adfde68c7732f97c153676c4",
      },
      {
         source: "security-advisories@github.com",
         url: "https://github.com/netty/netty/security/advisories/GHSA-4g8c-wm8x-jfhw",
      },
      {
         source: "af854a3a-2127-422b-91ae-364da2661108",
         url: "https://security.netapp.com/advisory/ntap-20250221-0005/",
      },
      {
         source: "134c704f-9b21-4f2e-91b3-4a467353bcc0",
         url: "https://github.com/netty/netty/security/advisories/GHSA-4g8c-wm8x-jfhw",
      },
   ],
   sourceIdentifier: "security-advisories@github.com",
   vulnStatus: "Awaiting Analysis",
   weaknesses: [
      {
         description: [
            {
               lang: "en",
               value: "CWE-20",
            },
         ],
         source: "security-advisories@github.com",
         type: "Secondary",
      },
   ],
}


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.