CVE-2021-22319

HIGHNVD 7.57.5—

7.5

There is an improper verification vulnerability in smartphones. Successful exploitation of this vulnerability may cause integer overflows.

CVSS v3: 7.5
EG Score: 7.5(medium)
EPSS: 40.7%
KEV: Not listed

Published

February 25, 2022

Last Modified

November 21, 2024

References (4)

psirt@huaweihttps://consumer.huawei.com/en/support/bulletin/2021/10/
psirt@huaweihttps://device.harmonyos.com/en/docs/security/update/security-bulletins-phones-202109-0000001150310956
af854a3a-2127-422b-91ae-364da2661108https://consumer.huawei.com/en/support/bulletin/2021/10/
af854a3a-2127-422b-91ae-364da2661108https://device.harmonyos.com/en/docs/security/update/security-bulletins-phones-202109-0000001150310956

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

CWE-190Integer Overflow or Wraparound

Data Freshness Timeline

(refreshed 12× in last 7d / 20× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-06-05 06:09 UTCepss_batch
2026-06-05 06:09 UTCepss_batch
2026-06-05 06:08 UTCepss_batch
2026-06-02 20:11 UTCepss_batch
2026-06-02 20:11 UTCepss_batch
2026-06-01 13:50 UTCepss_batch
2026-06-01 13:50 UTCepss_batch
2026-05-31 22:29 UTCepss_batch
2026-05-31 22:29 UTCepss_batch
2026-05-31 00:15 UTCepss_batch
2026-05-31 00:15 UTCepss_batch
2026-05-29 13:42 UTCepss_batch
2026-05-28 13:43 UTCepss_batch
2026-05-28 13:43 UTCepss_batch
2026-05-27 13:39 UTCepss_batch
2026-05-26 13:42 UTCepss_batch
2026-05-26 13:42 UTCepss_batch
2026-05-26 07:17 UTCepss_batch
2026-05-26 07:17 UTCepss_batch
2026-05-26 02:27 UTCEG score recompute

Frequently asked(5)

What is CVE-2021-22319?

CVE-2021-22319 is a high vulnerability published on February 25, 2022. There is an improper verification vulnerability in smartphones. Successful exploitation of this vulnerability may cause integer overflows.

When was CVE-2021-22319 disclosed?

CVE-2021-22319 was first published in the National Vulnerability Database on February 25, 2022, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2021-22319 actively exploited?

CVE-2021-22319 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 40.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

What is the CVSS score of CVE-2021-22319?

CVE-2021-22319 has a CVSS v3 base score of 7.5 (NVD).

How do I remediate CVE-2021-22319?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2021-22319, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2021-22319

Explore →

Is Your Infrastructure Affected by CVE-2021-22319?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs

CVE-2021-22319

📅 Published

🔄 Last Modified

🔗 References (4)

Weakness Classification(1)

Data Freshness Timeline

❓ Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2021-22319?

🔗 Related CVEs(same CWE)

Same CWE

Published

Last Modified

References (4)

Frequently asked(5)

Related CVEs(same CWE)