CVE-2022-0100 Heap buffer overflow in Media streams API in Chrome prior to 97.0.4692.71 could allow a remote attacker to exploit heap corruption.

CVE-2022-0100 Heap buffer overflow in Media streams API in Chrome prior to 97.0.4692.71 could allow a remote attacker to exploit heap corruption.

Note that this issue was fixed in later releases of Google Chrome. Google Chrome prior to 75.0.3770.80 did not properly handle objects in memory when parsing Media streams. This could lead to objects being created in one process but then being read by another process, potentially resulting in a process crash. Google Chrome prior to 75.0.3770.80 did not properly handle objects in memory when parsing HTML media tags. This could lead to objects being created in one process but then being read by another process, potentially resulting in a process crash. Google Chrome prior to 75.0.3770.80 did not properly handle objects in memory when parsing an audio tag. This could lead to objects being created in one process but then being read by another process, potentially resulting in a process crash. Google Chrome prior to 75.0.3770.80 did not properly handle objects in memory when parsing a video tag. This could lead to objects being created in one process but then being read by another process, potentially resulting in a process crash. Google Chrome prior to 75.0.3770.80 did not properly handle objects in memory when parsing a canvas tag. This could lead to objects being created in one process but then being read by another process, potentially resulting in a process crash. Google Chrome prior to 75.0.3770.80 did not properly handle objects in memory when parsing an audio tag. This could lead to objects being created in one process but then being

Google Chrome Vulnerability Reference CVE-2022-0100

Note that this issue was fixed in later releases of Google Chrome. Google Chrome prior to 75.0.3770.80 did not properly handle objects in memory when parsing Media streams. This could lead to objects being created in one process but then being read by another process, potentially resulting in a process crash. Google Chrome prior to 75.0.3770.80 did not properly handle objects in memory when parsing HTML media tags. This could lead to objects being created in one process but then being read by another process, potentially resulting in a process crash. Google Chrome prior to 75.0.3770.80 did not properly handle objects in memory when parsing an audio tag. This could lead to objects being created in one process but then being read by another process, potentially resulting in a process crash. Google Chrome prior to 75.0.3770.80 did not properly handle objects in memory when parsing a video tag. This could lead to objects being created in one process but then being read by another process, potentially resulting in a process crash.[1]
[1] https://bugsplat-sapiencloudsolutions-comcastcorpcomwc2-dhscomwc2-usa/view

How dangerous is this vulnerability?

This vulnerability is considered to be high severity.

References

Subscribe to CVE.news
Don’t miss out on the latest issues. Sign up now to get access to the library of members-only issues.
jamie@example.com
Subscribe