Samsung Devices up to SMR Feb-2021 Release 1 RTCP SDES Packet librtp.so improper validation of consistency within input
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.2 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Samsung Devices. It has been classified as problematic. Affected by this issue is some unknown functionality in the library librtp.so of the component RTCP SDES Packet Handler. This manipulation causes improper validation of consistency within input. This vulnerability is registered as CVE-2024-34591. Remote exploitation of the attack is possible. No exploit is available. Upgrading the affected component is recommended.
Details
A vulnerability was found in Samsung Devices. It has been declared as problematic. Affected by this vulnerability is an unknown code block in the library librtp.so of the component RTCP SDES Packet Handler. The manipulation with an unknown input leads to a improper validation of consistency within input vulnerability. The CWE definition for the vulnerability is CWE-1288. The product receives a complex input with multiple elements or fields that must be consistent with each other, but it does not validate or incorrectly validates that the input is actually consistent. As an impact it is known to affect availability. The summary by CVE is:
Improper input validation in parsing an item data from RTCP SDES packet in librtp.so prior to SMR Jul-2024 Release 1 allows remote attackers to trigger temporary denial of service. User interaction is required for triggering this vulnerability.
The advisory is shared at security.samsungmobile.com. This vulnerability is known as CVE-2024-34591 since 05/07/2024. The exploitation appears to be difficult. The attack can be launched remotely. The exploitation doesn't need any form of authentication. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available.
Upgrading to version SMR Jul-2024 Release 1 eliminates this vulnerability.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
- 7
- 8
- 9.0
- 10.0
- 11.0
- <=2017-11-03
- <=2020-04-02
- Go(8.1)
- Go(9.0)
- L
- L(5.1)
- L(5.x)
- M
- M(6.0)
- M(6.x)
- N
- N(7.0)
- N(7.1)
- N(7.x)
- O(8.0)
- O(8.1)
- O(8.X)
- O(8.x)
- P(9.0)
- P(9.x)
- Q(10.0)
- Q(10.x)
- R(11.0)
- SMR Feb-2021 Release 1
License
Website
- Vendor: https://www.samsung.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.2
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 5.3
CNA Vector (Samsung Mobile): 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Improper validation of consistency within inputCWE: CWE-1288 / CWE-20
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Devices SMR Jul-2024 Release 1
Timeline
05/07/2024 🔍07/02/2024 🔍
07/02/2024 🔍
03/21/2025 🔍
Sources
Vendor: samsung.comAdvisory: security.samsungmobile.com
Status: Confirmed
CVE: CVE-2024-34591 (🔍)
GCVE (CVE): GCVE-0-2024-34591
GCVE (VulDB): GCVE-100-270205
Entry
Created: 07/02/2024 13:53Updated: 03/21/2025 06:16
Changes: 07/02/2024 13:53 (64), 03/21/2025 06:16 (4)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.