Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2022-38701: OpenHarmony-v3.1.2 and prior versions have a heap overflow vulnerability

24
Routine
MEDIUM 6.2UPGRADEUPGRADE

CVE-2022-38701 is a medium-severity flaw (CVSS 6.2) affecting openharmony, openharmony. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

OpenHarmony-v3.1.2 and prior versions have a heap overflow vulnerability. Local attackers can trigger a heap overflow and get network sensitive information.

Why this priority

  • No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score6.2 (Medium)
Attack vectorLocal
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance0.2% (top 91%)
CISA exploited listNo
WeaknessCWE-122, CWE-787
Published2022-09-09
Last modified2026-06-17
Publisher (CNA): OpenHarmony · Vendor: openatom · openharmony

Share: LinkedIn · X · Reddit

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

openharmony openharmony UPGRADE
Affected: >= 3.0 and <= 3.0.5
Fixed in: newer than 3.0.5
Safe to downgrade to: a release before 3.0
1. Check installed version
apt-cache policy openharmony || rpm -q openharmony || openharmony --version
2. UPGRADE to newer than 3.0.5 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade openharmony
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade openharmony
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 3.0 (Debian / Ubuntu)
apt-cache madison openharmony sudo apt install openharmony=<VERSION_BEFORE_3.0> sudo apt-mark hold openharmony
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list openharmony sudo dnf downgrade openharmony-<VERSION_BEFORE_3.0> sudo dnf versionlock add openharmony
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
openatom openharmony UPGRADE
Affected: >= 3.1 and <= 3.1.2
Fixed in: newer than 3.1.2
Safe to downgrade to: a release before 3.1
Check your OS release
cat /etc/os-release; uname -r
Debian / Ubuntu
sudo apt update && sudo apt full-upgrade
RHEL / Amazon Linux / Fedora
sudo dnf upgrade --refresh
Windows
Install the latest cumulative update from Windows Update
If no patch exists yet
OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2022-38701?

openharmony: upgrade to newer than 3.0.5; openharmony: upgrade to newer than 3.1.2. Exact commands for each OS are on this page.

Is CVE-2022-38701 being exploited?

CVE-2022-38701 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2022-38701 affect?

CVE-2022-38701 affects openharmony, openharmony. Severity is medium (CVSS 6.2). OpenHarmony-v3.1.2 and prior versions have a heap overflow vulnerability. Local attackers can trigger a heap overflow and get network sensitive information.

How urgent is CVE-2022-38701?

Priority 24/100. No elevated risk signals yet.

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.