Moderate
CVE-2021-37976
CVE ID
AttackerKB requires a CVE ID in order to pull vulnerability data and references from the CVE list and the National Vulnerability Database. If available, please supply below:
Add References:
CVE-2021-37976
MITRE ATT&CK
Collection
Command and Control
Credential Access
Defense Evasion
Discovery
Execution
Exfiltration
Impact
Initial Access
Lateral Movement
Persistence
Privilege Escalation
Topic Tags
Description
Inappropriate implementation in Memory in Google Chrome prior to 94.0.4606.71 allowed a remote attacker to obtain potentially sensitive information from process memory via a crafted HTML page.
Add Assessment
Ratings
-
Attacker ValueMedium
-
ExploitabilityMedium
Technical Analysis
More info will be available at https://bugs.chromium.org/p/chromium/issues/detail?id=1251787 when this bug gets declassified however for now https://chromereleases.googleblog.com/2021/09/stable-channel-update-for-desktop_30.html indicates that this is a Medium severity bug caused by an information leak within Core itself. It was discovered by Clément Lecigne from Google TAG, with technical assistance from Sergei Glazunov and Mark Brand from Google Project Zero and was first discovered on 2021-09-21.
The fact that Google TAG discovered this combined with the fact this was exploited in the wild means that its likely Google found this exploit via in the wild exploitation and TAG noticed these exploitation attempts, verified it was a 0day vulnerability, and then notified Google so that they could issue a fix. What is interesting though is that there is no mention of a related 0day exploit that was combined with this vulnerability, which I imagine would be needed in order to make a full exploit.
Most likely this vulnerability would be used to leak information needed for form a full exploit, and would likely be useful for bypassing certain security mitigations that may otherwise prevent the exploit from working normally.
On its own this vulnerability is therefore of Medium to Medium-Low severity, however given its use in exploits in the wild I’d recommend still patching this to make sure that you are protecting your organization against threats that have been proven to have been successfully exploited in real world scenarios. Just be aware that this might sit lower on your priority list than vulnerabilities that can get RCE on their own.
Would you also like to delete your Exploited in the Wild Report?
Delete Assessment Only Delete Assessment and Exploited in the Wild ReportCVSS V3 Severity and Metrics
General Information
Vendors
- debian,
- fedoraproject,
Products
- chrome,
- debian linux 10.0,
- debian linux 11.0,
- fedora 33,
- fedora 34,
- fedora 35
Exploited in the Wild
Would you like to delete this Exploited in the Wild Report?
Yes, delete this reportWould you like to delete this Exploited in the Wild Report?
Yes, delete this reportWould you like to delete this Exploited in the Wild Report?
Yes, delete this reportReferences
Advisory
Additional Info
Technical Analysis
Report as Emergent Threat Response
Report as Exploited in the Wild
CVE ID
AttackerKB requires a CVE ID in order to pull vulnerability data and references from the CVE list and the National Vulnerability Database. If available, please supply below: