DoS caused due to wrong hash length returned for SHA2/224 algorithm

published 2025-01-07 last yr. modified 2026-06-17 4mo ago also EUVD-2024-49626

cvss: 7.5; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.4%; EPSS 0.4% chance of exploitation in 30 days, percentile 38%
public exploits: 0; none known

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

Is CVE-2024-8361 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation: none
Automatable: yes
Technical impact: partial
Assessed: last yr. (2025-01-07)

Exploit prediction

0.44% chance of exploitation in the next 30 days, higher than 38% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by	version	score	vector
CNA	3.1	7.5	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected products

silabs.com WiSeConnect SDK

Classification

Weakness

CWE-131 Incorrect Calculation of Buffer Size
CWE-617 Reachable Assertion

References

community.silabs.com /068Vm00000I7zqo
vendor-advisory, permissions-required

Sources

CVE List CVE-2024-8361
NVD CVE-2024-8361

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.