Astra Linux – Vulnerability in Chromium

Before version 101.0.4951.41, using free after in the Ozone browser extension in Google Chrome allowed a remote attacker to potentially exploit heap corruption by running a Wayland test...

EUVD-2022-24788

Malicious code in bioql PyPI...

SUSE CVE-2022-1487

Use after free in Ozone in Google Chrome prior to 101.0.4951.41 allowed a remote attacker to potentially exploit heap corruption via running a Wayland test...

CVE-2022-1487

Use after free in Ozone in Google Chrome prior to 101.0.4951.41 allowed a remote attacker to potentially exploit heap corruption via running a Wayland test...

CVE-2022-1487

Use after free in Ozone in Google Chrome prior to 101.0.4951.41 allowed a remote attacker to potentially exploit heap corruption via running a Wayland test...

Design/Logic Flaw

Use after free in Ozone in Google Chrome prior to 101.0.4951.41 allowed a remote attacker to potentially exploit heap corruption via running a Wayland test...

CVE-2022-1487

Use after free in Ozone in Google Chrome prior to 101.0.4951.41 allowed a remote attacker to potentially exploit heap corruption via running a Wayland test...

CVE-2022-1487

CVE-2022-1487 describes a use-after-free in Ozone within Google Chrome/Chromium, allowing potential remote heap corruption when running a Wayland test. Affected product/portion: Ozone in Chrome/Chromium prior to version 101.0.4951.41. Root cause: use-after-free vulnerability in Ozone components. ...

CVE-2022-1487: Use After Free

Use after free in Ozone in Google Chrome prior to 101.0.4951.41 allowed a remote attacker to potentially exploit heap corruption via running a Wayland test...

Use-After-Free

chromium is vulnerable to use after free. The vulnerability exists due to heap corruption which allows an attacker to potentially exploit heap corruption via running a Wayland test...

PT-2022-2399

Name of the Vulnerable Software and Affected Versions Google Chrome versions prior to 101.0.4951.41 Microsoft Edge affected versions not specified Description The issue is related to a use after free in the Ozone component, which could allow a remote attacker to potentially exploit heap corruptio...