What is the CVSS score of CVE-2023-52266?

CVE-2023-52266 has a CVSS 3.1 base score of 7.5 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. EPSS exploitation probability: 0.7%.

Is there a public PoC exploit available for CVE-2023-52266?

Yes, a public proof-of-concept exploit is available for CVE-2023-52266. Prioritise patching immediately. EPSS: 0.7%.

Is there a patch available for CVE-2023-52266?

Yes, a patch is available for CVE-2023-52266. Update the affected software to the latest version immediately.

Ehttp CVE-2023-52266

HIGH

Use After Free (CWE-416)

2023-12-31 cve@mitre.org

Use After Free Information Disclosure Memory Corruption Ehttp

7.5

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

7.5 HIGH

AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

None

Availability

High

Lifecycle Timeline

CVE Published

Dec 31, 2023 - 00:15 nvd

HIGH 7.5

DescriptionNVD

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.

AnalysisAI

ehttp 1.0.6 before 17405b9 has an epoll_socket.cpp read_func use-after-free. Rated high severity (CVSS 7.5), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available.

Technical ContextAI

This vulnerability is classified as Use After Free (CWE-416), which allows attackers to access freed memory to execute arbitrary code or crash the application. 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. Affected products include: Hongliuliao Ehttp. Version information: before 17405.

RemediationAI

A vendor patch is available. Apply the latest security update as soon as possible. Use smart pointers or garbage-collected languages. Set pointers to NULL after freeing. Enable memory sanitizers.