Skip to content
CTI Academy Sponsor CTI Academy
HIGH · CVSS 8.8 CISA Known Exploited Vulnerability

CVE-2022-3038

Google Chromium Network Service Use-After-Free Vulnerability

Google Chromium Network Service

Use after free in Network Service in Google Chrome prior to 105.0.5195.52 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.

CVSS
8.8
HIGH
EPSS
24.9%
30-day exploitation
Ransomware groups
0
recorded exploiting
Published
26 Sep 2022
CWE-416

Exploitation status

CISA Known Exploited Vulnerabilities

Listed by CISA on 30 March 2023. US federal agencies were required to remediate it by 20 April 2023.

EPSS — exploitation probability

FIRST puts the probability of exploitation activity in the next 30 days at 24.9%, which is higher than 97.9% of all scored vulnerabilities. EPSS is a forecast of activity, not a measure of severity, and it is rescored daily.

CVSS vector

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

Frequently asked questions

Is CVE-2022-3038 being exploited by ransomware groups?

No ransomware group in this database is currently recorded as exploiting CVE-2022-3038.

What does CVE-2022-3038 affect?

CVE-2022-3038 affects Google Chromium Network Service. Use after free in Network Service in Google Chrome prior to 105.0.5195.52 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.

How severe is CVE-2022-3038?

CVE-2022-3038 is rated HIGH with a CVSS base score of 8.8. EPSS puts the probability of exploitation in the next 30 days at 24.9%, higher than 97.9% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 20 April 2023.

How should organisations respond to CVE-2022-3038?

Apply the vendor patch for Google Chromium Network Service as the first priority, and treat any internet-facing instance as the most urgent. Because this vulnerability is associated with ransomware activity, also review whether the affected systems were reachable before patching, rather than assuming that patching alone closes the incident.