CVE-2023-1813

Inappropriate implementation in Extensions in Google Chrome prior to 112.0.5615.49 allowed an attacker who convinced a user to install a malicious extension to bypass file access restrictions via a crafted HTML page. (Chromium security severity: Medium)

This update for chromium fixes the following issues:

• Chromium 112.0.5615.121:

  • CVE-2023-2033: Type Confusion in V8 (boo#1210478)

• Chromium 112.0.5615.49

  • CSS now supports nesting rules.
  • The algorithm to set the initial focus on <dialog> elements was updated.
  • No-op fetch() handlers on service workers are skipped from now on to make navigations faster
  • The setter for document.domain is now deprecated.
  • The recorder in devtools can now record with pierce selectors.
  • Security fixes (boo#1210126):
  • CVE-2023-1810: Heap buffer overflow in Visuals
  • CVE-2023-1811: Use after free in Frames
  • CVE-2023-1812: Out of bounds memory access in DOM Bindings
  • CVE-2023-1813: Inappropriate implementation in Extensions
  • CVE-2023-1814: Insufficient validation of untrusted input in Safe Browsing
  • CVE-2023-1815: Use after free in Networking APIs
  • CVE-2023-1816: Incorrect security UI in Picture In Picture
  • CVE-2023-1817: Insufficient policy enforcement in Intents
  • CVE-2023-1818: Use after free in Vulkan
  • CVE-2023-1819: Out of bounds read in Accessibility
  • CVE-2023-1820: Heap buffer overflow in Browser History
  • CVE-2023-1821: Inappropriate implementation in WebShare
  • CVE-2023-1822: Incorrect security UI in Navigation
  • CVE-2023-1823: Inappropriate implementation in FedCM

• Chromium 111.0.5563.147:

  • nth-child() validation performance regression for SAP apps

These are all security issues fixed in the chromedriver-112.0.5615.49-1.1 package on the GA media of openSUSE Tumbleweed.

These are all security issues fixed in the ungoogled-chromium-113.0.5672.92-1.1 package on the GA media of openSUSE Tumbleweed.

It was discovered that Chromium did not properly manage memory in several components. A remote attacker could possibly use this issue to corrupt memory via a crafted HTML page, resulting in a denial of service, or possibly execute arbitrary code. (CVE-2023-1528, CVE-2023-1530, CVE-2023-1531, CVE-2023-1533, CVE-2023-1811, CVE-2023-1815, CVE-2023-1818)

It was discovered that Chromium could be made to access memory out of bounds in WebHID. A remote attacker could possibly use this issue to corrupt memory via a malicious HID device, resulting in a denial of service, or possibly execute arbitrary code. (CVE-2023-1529)

It was discovered that Chromium could be made to access memory out of bounds in several components. A remote attacker could possibly use this issue to corrupt memory via a crafted HTML page, resulting in a denial of service, or possibly execute arbitrary code. (CVE-2023-1532, CVE-2023-1534, CVE-2023-1810, CVE-2023-1812, CVE-2023-1819, CVE-2023-1820)

It was discovered that Chromium contained an inappropriate implementation in the Extensions component. A remote attacker who convinced a user to install a malicious extension could possibly use this issue to bypass file access restrictions via a crafted HTML page. (CVE-2023-1813)

It was discovered that Chromium did not properly validate untrusted input in the Safe Browsing component. A remote attacker could possibly use this issue to bypass download checking via a crafted HTML page. (CVE-2023-1814)

It was discovered that Chromium contained an inappropriate implementation in the Picture In Picture component. A remote attacker could possibly use this issue to perform navigation spoofing via a crafted HTML page. (CVE-2023-1816)

It was discovered that Chromium contained an inappropriate implementation in the WebShare component. A remote attacker could possibly use this issue to hide the contents of the Omnibox (URL bar) via a crafted HTML page. (CVE-2023-1821)

It was discovered that Chromium contained an inappropriate implementation in the Navigation component. A remote attacker could possibly use this issue to perform domain spoofing via a crafted HTML page. (CVE-2023-1822)

It was discovered that Chromium contained an inappropriate implementation in the FedCM component. A remote attacker could possibly use this issue to bypass navigation restrictions via a crafted HTML page. (CVE-2023-1823)