fkie_cve-2024-8361
Vulnerability from fkie_nvd
Published
2025-01-07 17:15
Modified
2025-09-16 17: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
In SiWx91x devices, the SHA2/224 algorithm returns a hash of 256 bits instead of 224 bits. This incorrect hash length triggers a software assertion, which subsequently causes a Denial of Service (DoS). If a watchdog is implemented, device will restart after watch dog expires. If watchdog is not implemented, device can be recovered only after a hard reset
References
product-security@silabs.comhttps://community.silabs.com/068Vm00000I7zqo
Impacted products
Vendor Product Version


To clipboard 

{
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "In SiWx91x devices, the SHA2/224 algorithm returns a hash of 256 bits instead of 224 bits. This incorrect hash length triggers a software assertion, which subsequently causes a Denial of Service (DoS).\nIf a watchdog is implemented, device will restart after watch dog expires. If watchdog is not implemented, device can be recovered only after a hard reset"
    },
    {
      "lang": "es",
      "value": "En los dispositivos SiWx91x, el algoritmo SHA2/224 devuelve un hash de 256 bits en lugar de 224 bits. Esta longitud de hash incorrecta activa una aserci\u00f3n de software, que posteriormente provoca una denegaci\u00f3n de servicio (DoS). Si se implementa un watchdog, el dispositivo se reiniciar\u00e1 despu\u00e9s de que expire el watchdog. Si no se implementa un watchdog, el dispositivo solo se puede recuperar despu\u00e9s de un reinicio completo."
    }
  ],
  "id": "CVE-2024-8361",
  "lastModified": "2025-09-16T17:15:40.367",
  "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": "product-security@silabs.com",
        "type": "Secondary"
      }
    ]
  },
  "published": "2025-01-07T17:15:31.420",
  "references": [
    {
      "source": "product-security@silabs.com",
      "url": "https://community.silabs.com/068Vm00000I7zqo"
    }
  ],
  "sourceIdentifier": "product-security@silabs.com",
  "vulnStatus": "Awaiting Analysis",
  "weaknesses": [
    {
      "description": [
        {
          "lang": "en",
          "value": "CWE-131"
        },
        {
          "lang": "en",
          "value": "CWE-617"
        }
      ],
      "source": "product-security@silabs.com",
      "type": "Secondary"
    }
  ]
}


Log in or create an account to share your comment.




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.