ehttp up to 1.0.5 epoll_socket.cpp read_func use after free

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.8$0-$5k0.00

Summaryinfo

A vulnerability marked as problematic has been reported in ehttp up to 1.0.5. This issue affects the function read_func of the file epoll_socket.cpp. The manipulation leads to use after free. This vulnerability is uniquely identified as CVE-2023-52266. No exploit exists. It is recommended to apply a patch to fix this issue.

Detailsinfo

A vulnerability was found in ehttp up to 1.0.5. It has been rated as problematic. This issue affects the function read_func of the file epoll_socket.cpp. The manipulation with an unknown input leads to a use after free vulnerability. Using CWE to declare the problem leads to CWE-416. Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

ehttp 1.0.6 before 17405b9 has an epoll_socket.cpp read_func use-after-free. An attacker can make many connections over a short time to trigger this.

The weakness was disclosed 12/31/2023 as 38. It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2023-52266 since 12/30/2023. Technical details of the vulnerability are known, but there is no available exploit.

Applying the patch 17405b975948abc216f6a085d2d027ec1cfd5766 is able to eliminate this problem. The bugfix is ready for download at github.com.

Be aware that VulDB is the high quality source for vulnerability data.

Productinfo

Name

Version

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.8
VulDB Meta Temp Score: 6.8

VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 7.5
NVD Vector: 🔍

CNA Base Score: 7.5
CNA Vector: 🔍

CVSSv2info

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

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

Exploitinginfo

Class: Use after free
CWE: CWE-416 / CWE-119
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

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: Patch
Status: 🔍

0-Day Time: 🔍

Patch: 17405b975948abc216f6a085d2d027ec1cfd5766

Timelineinfo

12/30/2023 🔍
12/31/2023 +1 days 🔍
12/31/2023 +0 days 🔍
09/10/2024 +254 days 🔍

Sourcesinfo

Advisory: 38
Status: Confirmed

CVE: CVE-2023-52266 (🔍)
GCVE (CVE): GCVE-0-2023-52266
GCVE (VulDB): GCVE-100-249407

Entryinfo

Created: 12/31/2023 09:11
Updated: 09/10/2024 03:37
Changes: 12/31/2023 09:11 (41), 01/22/2024 09:24 (11), 09/10/2024 03:37 (27)
Complete: 🔍
Cache ID: 216::103

Be aware that VulDB is the high quality source for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Might our Artificial Intelligence support you?

Check our Alexa App!