zephyrproject-rtos Zephyr up to 3.5 remove_rx_filter out-of-bounds write
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.5 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in zephyrproject-rtos Zephyr up to 3.5 and classified as critical. Affected by this vulnerability is the function remove_rx_filter. This manipulation causes out-of-bounds write.
The identification of this vulnerability is CVE-2023-5779. The attack can only be executed locally. There is no exploit available.
Details
A vulnerability classified as critical was found in zephyrproject-rtos Zephyr up to 3.5 (Project Management Software). Affected by this vulnerability is the function remove_rx_filter. The manipulation with an unknown input leads to a out-of-bounds write vulnerability. The CWE definition for the vulnerability is CWE-787. The product writes data past the end, or before the beginning, of the intended buffer. As an impact it is known to affect confidentiality, integrity, and availability.
The weakness was shared 02/18/2024 as GHSA-7cmj-963q-jj47. The advisory is shared at github.com. This vulnerability is known as CVE-2023-5779 since 10/26/2023. Technical details are known, but no exploit is available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.5VulDB Meta Temp Score: 6.5
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔍
CNA Base Score: 4.4
CNA Vector (Zephyr Project): 🔍
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: Out-of-bounds writeCWE: CWE-787 / CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
10/26/2023 🔍02/18/2024 🔍
02/18/2024 🔍
01/23/2025 🔍
Sources
Product: github.comAdvisory: GHSA-7cmj-963q-jj47
Status: Confirmed
CVE: CVE-2023-5779 (🔍)
GCVE (CVE): GCVE-0-2023-5779
GCVE (VulDB): GCVE-100-254089
Entry
Created: 02/18/2024 17:06Updated: 01/23/2025 00:13
Changes: 02/18/2024 17:06 (49), 01/23/2025 00:13 (26)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.