OpenHarmony up to 5.0.2 buffer overflow

Summaryinfo

A vulnerability, which was classified as critical, has been found in OpenHarmony up to 5.0.2. The impacted element is an unknown function. The manipulation leads to buffer overflow. This vulnerability is documented as CVE-2025-22897. The attack needs to be performed locally. There is not any exploit available.

Detailsinfo

A vulnerability was found in OpenHarmony up to 5.0.2 and classified as critical. This issue affects an unknown functionality. The manipulation with an unknown input leads to a buffer overflow vulnerability. Using CWE to declare the problem leads to CWE-120. The product copies an input buffer to an output buffer without verifying that the size of the input buffer is less than the size of the output buffer, leading to a buffer overflow. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

in OpenHarmony v5.0.2 and prior versions allow a local attacker cause DOS through buffer overflow.

The advisory is shared at gitee.com. The identification of this vulnerability is CVE-2025-22897 since 01/20/2025. The exploitation is known to be easy. An attack has to be approached locally. Neither technical details nor an exploit are publicly 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.

Productinfo

Type

• Smartphone Operating System

Name

• OpenHarmony

Version

• 5.0.0
• 5.0.1
• 5.0.2

License

• open-source

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion