6.5 Medium
CVSS3
Attack Vector
NETWORK
Attack Complexity
LOW
Privileges Required
NONE
User Interaction
REQUIRED
Scope
UNCHANGED
Confidentiality Impact
HIGH
Integrity Impact
NONE
Availability Impact
NONE
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
4.3 Medium
CVSS2
Access Vector
NETWORK
Access Complexity
MEDIUM
Authentication
NONE
Confidentiality Impact
PARTIAL
Integrity Impact
NONE
Availability Impact
NONE
AV:N/AC:M/Au:N/C:P/I:N/A:N
0.03 Low
EPSS
Percentile
89.8%
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.
Recent assessments:
gwillcox-r7 at October 02, 2021 7:27pm UTC reported:
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.
Assessed Attacker Value: 3
Assessed Attacker Value: 3Assessed Attacker Value: 3
chromereleases.googleblog.com/2021/09/stable-channel-update-for-desktop_30.html
crbug.com/1251787
cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-37976
lists.fedoraproject.org/archives/list/[email protected]/message/D63JZ3ROXCUHP4CFWDHCPZNTGET7T34R/
lists.fedoraproject.org/archives/list/[email protected]/message/FRFXUDH46PFVE75VQVWY6PYY5DK3S2XT/
lists.fedoraproject.org/archives/list/[email protected]/message/RNARCF5HEZK7GJXZRN5TQ45AQDCRM2WO/
www.debian.org/security/2022/dsa-5046
6.5 Medium
CVSS3
Attack Vector
NETWORK
Attack Complexity
LOW
Privileges Required
NONE
User Interaction
REQUIRED
Scope
UNCHANGED
Confidentiality Impact
HIGH
Integrity Impact
NONE
Availability Impact
NONE
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
4.3 Medium
CVSS2
Access Vector
NETWORK
Access Complexity
MEDIUM
Authentication
NONE
Confidentiality Impact
PARTIAL
Integrity Impact
NONE
Availability Impact
NONE
AV:N/AC:M/Au:N/C:P/I:N/A:N
0.03 Low
EPSS
Percentile
89.8%