Exynos 9820 Firmware: Stack-based Buffer Overflow
CVE-2024-52924 is a high-severity stack-based buffer overflow vulnerability in Exynos 9820 Firmware from Samsung, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. There is no confirmed exploitation so far. EPSS estimates a 0.41% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Check which version of Exynos 9820 Firmware you run against the affected versions below, and install the vendor's latest release.
- Read the advisory on semiconductor.samsung.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Samsung | Exynos 9820 Firmware | Not specified in the record | Not stated |
| Samsung | Exynos 9825 Firmware | Not specified in the record | Not stated |
| Samsung | Exynos 980 Firmware | Not specified in the record | Not stated |
| Samsung | Exynos 990 Firmware | Not specified in the record | Not stated |
| Samsung | Exynos 850 Firmware | Not specified in the record | Not stated |
| Samsung | Exynos 1080 Firmware | Not specified in the record | Not stated |
| Samsung | Exynos 2100 Firmware | Not specified in the record | Not stated |
| Samsung | Exynos 1280 Firmware | Not specified in the record | Not stated |
| Samsung | Exynos 2200 Firmware | Not specified in the record | Not stated |
| Samsung | Exynos 1330 Firmware | Not specified in the record | Not stated |
| Samsung | Exynos 1380 Firmware | Not specified in the record | Not stated |
| Samsung | Exynos 1480 Firmware | Not specified in the record | Not stated |
| Samsung | Exynos 2400 Firmware | Not specified in the record | Not stated |
| Samsung | Exynos 9110 Firmware | Not specified in the record | Not stated |
| Samsung | Exynos W920 Firmware | Not specified in the record | Not stated |
| Samsung | Exynos W930 Firmware | Not specified in the record | Not stated |
| Samsung | Exynos W1000 Firmware | Not specified in the record | Not stated |
| Samsung | Exynos Modem 5123 Firmware | Not specified in the record | Not stated |
| Samsung | Exynos Modem 5300 Firmware | Not specified in the record | Not stated |
| Samsung | Exynos Modem 5400 Firmware | Not specified in the record | Not stated |
Version data comes from NVD's product matching. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- NoneNo data is disclosed.
- Integrity
- NoneNothing can be modified.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. Scored by CISA (ADP).
Official description
An issue was discovered in NRMM in Samsung Mobile Processor, Wearable Processor, and Modem Exynos 9820, 9825, 980, 990, 850, 1080, 2100, 1280, 2200, 1330, 1380, 1480, 2400, 9110, W920, W930, W1000, Modem 5123, Modem 5300, and Modem 5400. Lack of boundary check during the decoding of Registration Accept messages can lead to out-of-bounds writes on the stack
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Stack-based Buffer Overflow
The product writes past the end of a buffer that was allocated on the stack.
How developers prevent this class of flaw
- Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking. D3-SFCV (Stack Frame Canary Validation) from D3FEND discusses canary-based detection in detail.
- Use an abstraction library to abstract away risky APIs. Not a complete solution.
- Implement and perform bounds checking on input.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Other vulnerabilities in Exynos 9820 Firmware
- 7.5 High severity
- 8.1 High severity
- 8.1 High severity
- 8.1 High severity
- 8.4 High severity
- 8.1 High severity
Recent Stack-based Buffer Overflow vulnerabilities
- 9.8 Critical severity
- 7.7 High severity
- 9.8 Critical severity
- 9.8 Critical severity
- 8.8 High severity
- 8.1 High severity
Spotted an error? Tell us.