Facebook Hermes Bytecode Optimization 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.
8.3$0-$5k0.00

Summaryinfo

A vulnerability marked as problematic has been reported in Facebook Hermes. This issue affects some unknown processing of the component Bytecode Optimization. This manipulation causes use after free. This vulnerability is tracked as CVE-2023-28081. No exploit exists. To fix this issue, it is recommended to deploy a patch.

Detailsinfo

A vulnerability has been found in Facebook Hermes (Social Network Software) (the affected version is unknown) and classified as problematic. Affected by this vulnerability is an unknown code of the component Bytecode Optimization. The manipulation with an unknown input leads to a use after free vulnerability. The CWE definition for the vulnerability is CWE-416. Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

A bytecode optimization bug in Hermes prior to commit e6ed9c1a4b02dc219de1648f44cd808a56171b81 could be used to cause an use-after-free and obtain arbitrary code execution via a carefully crafted payload. Note that this is only exploitable in cases where Hermes is used to execute untrusted JavaScript. Hence, most React Native applications are not affected.

The weakness was disclosed 05/19/2023. It is possible to read the advisory at facebook.com. This vulnerability is known as CVE-2023-28081 since 03/10/2023. The technical details are unknown and an exploit is not publicly available.

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

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Type

Vendor

Name

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 8.4
VulDB Meta Temp Score: 8.3

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

NVD Base Score: 9.8
NVD Vector: 🔍

CNA Base Score: 9.8
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: e6ed9c1a4b02dc219de1648f44cd808a56171b81

Timelineinfo

03/10/2023 🔍
05/19/2023 +69 days 🔍
05/19/2023 +0 days 🔍
01/21/2025 +613 days 🔍

Sourcesinfo

Product: github.com

Advisory: e6ed9c1a4b02dc219de1648f44cd808a56171b81
Status: Confirmed

CVE: CVE-2023-28081 (🔍)
GCVE (CVE): GCVE-0-2023-28081
GCVE (VulDB): GCVE-100-229387

Entryinfo

Created: 05/19/2023 07:02
Updated: 01/21/2025 23:57
Changes: 05/19/2023 07:02 (40), 06/14/2023 08:10 (1), 06/14/2023 08:12 (11), 01/21/2025 23:57 (26)
Complete: 🔍
Cache ID: 216::103

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!