zephyrproject-rtos Zephyr up to 3.6 zephyr/lib/utils/utf8.c utf8_trunc last_byte_p out-of-bounds

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
6.4$0-$5k0.00

Summaryinfo

A vulnerability has been found in zephyrproject-rtos Zephyr up to 3.6 and classified as critical. This vulnerability affects the function utf8_trunc in the library zephyr/lib/utils/utf8.c. This manipulation of the argument last_byte_p causes out-of-bounds. This vulnerability is registered as CVE-2024-6443. The attack requires access to the local network. No exploit is available.

Detailsinfo

A vulnerability was found in zephyrproject-rtos Zephyr up to 3.6. It has been declared as critical. Affected by this vulnerability is the function utf8_trunc in the library zephyr/lib/utils/utf8.c. The manipulation of the argument last_byte_p with an unknown input leads to a out-of-bounds vulnerability. The CWE definition for the vulnerability is CWE-125. The product reads 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 summary by CVE is:

In utf8_trunc in zephyr/lib/utils/utf8.c, last_byte_p can point to one byte before the string pointer if the string is empty.

The advisory is shared at github.com. This vulnerability is known as CVE-2024-6443 since 07/02/2024. The exploitation appears to be easy. The attack needs to be done within the local network. The exploitation doesn't need any form of authentication. 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.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.4
VulDB Meta Temp Score: 6.4

VulDB Base Score: 6.3
VulDB Temp Score: 6.3
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 6.5
NVD Vector: 🔍

CNA Base Score: 6.3
CNA Vector (zephyr): 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

Exploitinginfo

Class: Out-of-bounds
CWE: CWE-125 / CWE-119
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Partially

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

07/02/2024 🔍
10/04/2024 +94 days 🔍
10/04/2024 +0 days 🔍
11/13/2024 +40 days 🔍

Sourcesinfo

Product: github.com

Advisory: GHSA-gg46-3rh2-v765
Status: Confirmed

CVE: CVE-2024-6443 (🔍)
GCVE (CVE): GCVE-0-2024-6443
GCVE (VulDB): GCVE-100-279205

Entryinfo

Created: 10/04/2024 08:31
Updated: 11/13/2024 07:47
Changes: 10/04/2024 08:31 (66), 10/05/2024 14:14 (1), 11/13/2024 07:47 (11)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to know what is going to be exploited?

We predict KEV entries!