fkie_cve-2024-8447
Vulnerability from fkie_nvd
Published
2025-01-02 21:15
Modified
2025-03-27 23:15
Severity ?
5.9 (Medium) - CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
Summary
A security issue was discovered in the LRA Coordinator component of Narayana. When Cancel is called in LRA, an execution time of approximately 2 seconds occurs. If Join is called with the same LRA ID within that timeframe, the application may crash or hang indefinitely, leading to a denial of service.
References
secalert@redhat.comhttps://access.redhat.com/errata/RHSA-2025:3357
secalert@redhat.comhttps://access.redhat.com/errata/RHSA-2025:3358
secalert@redhat.comhttps://access.redhat.com/security/cve/CVE-2024-8447
secalert@redhat.comhttps://bugzilla.redhat.com/show_bug.cgi?id=2335206
secalert@redhat.comhttps://github.com/jbosstm/narayana/pull/2293
Impacted products
Vendor Product Version


To clipboard 

{
   cveTags: [],
   descriptions: [
      {
         lang: "en",
         value: "A security issue was discovered in the LRA Coordinator component of Narayana. When Cancel is called in LRA, an execution time of approximately 2 seconds occurs. If Join is called with the same LRA ID within that timeframe, the application may crash or hang indefinitely, leading to a denial of service.",
      },
      {
         lang: "es",
         value: "Se descubrió un problema de seguridad en LRA Coordinator component de Narayana. Cuando se llama a Cancel en LRA, se produce un tiempo de ejecución de aproximadamente 2 segundos. Si se llama a Join con el mismo ID de LRA dentro de ese período de tiempo, la aplicación puede bloquearse o bloquearse indefinidamente, lo que genera una denegación de servicio.",
      },
   ],
   id: "CVE-2024-8447",
   lastModified: "2025-03-27T23:15:33.947",
   metrics: {
      cvssMetricV31: [
         {
            cvssData: {
               attackComplexity: "HIGH",
               attackVector: "NETWORK",
               availabilityImpact: "HIGH",
               baseScore: 5.9,
               baseSeverity: "MEDIUM",
               confidentialityImpact: "NONE",
               integrityImpact: "NONE",
               privilegesRequired: "NONE",
               scope: "UNCHANGED",
               userInteraction: "NONE",
               vectorString: "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H",
               version: "3.1",
            },
            exploitabilityScore: 2.2,
            impactScore: 3.6,
            source: "secalert@redhat.com",
            type: "Secondary",
         },
      ],
   },
   published: "2025-01-02T21:15:10.303",
   references: [
      {
         source: "secalert@redhat.com",
         url: "https://access.redhat.com/errata/RHSA-2025:3357",
      },
      {
         source: "secalert@redhat.com",
         url: "https://access.redhat.com/errata/RHSA-2025:3358",
      },
      {
         source: "secalert@redhat.com",
         url: "https://access.redhat.com/security/cve/CVE-2024-8447",
      },
      {
         source: "secalert@redhat.com",
         url: "https://bugzilla.redhat.com/show_bug.cgi?id=2335206",
      },
      {
         source: "secalert@redhat.com",
         url: "https://github.com/jbosstm/narayana/pull/2293",
      },
   ],
   sourceIdentifier: "secalert@redhat.com",
   vulnStatus: "Awaiting Analysis",
   weaknesses: [
      {
         description: [
            {
               lang: "en",
               value: "CWE-833",
            },
         ],
         source: "secalert@redhat.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.