The remote host is affected by the vulnerability described in GLSA-202208-35 (Chromium, Google Chrome, Microsoft Edge:
Multiple Vulnerabilities)

  - Use after free in Cast UI and Toolbar in Google Chrome prior to 103.0.5060.134 allowed an attacker who     convinced a user to install a malicious extension to potentially exploit heap corruption via UI     interaction. (CVE-2022-2163)

  - Heap buffer overflow in WebRTC in Google Chrome prior to 103.0.5060.114 allowed a remote attacker to     potentially exploit heap corruption via a crafted HTML page. (CVE-2022-2294)

  - Type confusion in V8 in Google Chrome prior to 103.0.5060.114 allowed a remote attacker to potentially     exploit heap corruption via a crafted HTML page. (CVE-2022-2295)

  - Use after free in Chrome OS Shell in Google Chrome on Chrome OS prior to 103.0.5060.114 allowed a remote     attacker who convinced a user to engage in specific user interactions to potentially exploit heap     corruption via direct UI interactions. (CVE-2022-2296)

  - Use after free in Guest View in Google Chrome prior to 103.0.5060.134 allowed an attacker who convinced a     user to install a malicious extension to potentially exploit heap corruption via a crafted HTML page.
    (CVE-2022-2477)

  - Use after free in PDF in Google Chrome prior to 103.0.5060.134 allowed a remote attacker to potentially     exploit heap corruption via a crafted HTML page. (CVE-2022-2478)

  - Insufficient validation of untrusted input in File in Google Chrome on Android prior to 103.0.5060.134     allowed an attacker who convinced a user to install a malicious app to obtain potentially sensitive     information from internal file directories via a crafted HTML page. (CVE-2022-2479)

  - Use after free in Service Worker API in Google Chrome prior to 103.0.5060.134 allowed a remote attacker to     potentially exploit heap corruption via a crafted HTML page. (CVE-2022-2480)

  - Use after free in Views in Google Chrome prior to 103.0.5060.134 allowed a remote attacker who convinced a     user to engage in specific user interactions to potentially exploit heap corruption via UI interaction.
    (CVE-2022-2481)

  - Use after free in Omnibox in Google Chrome prior to 104.0.5112.79 allowed a remote attacker to potentially     exploit heap corruption via a crafted HTML page. (CVE-2022-2603)

  - Use after free in Safe Browsing in Google Chrome prior to 104.0.5112.79 allowed a remote attacker to     potentially exploit heap corruption via a crafted HTML page. (CVE-2022-2604)

  - Out of bounds read in Dawn in Google Chrome prior to 104.0.5112.79 allowed a remote attacker to     potentially exploit heap corruption via a crafted HTML page. (CVE-2022-2605)

  - Use after free in Managed devices API in Google Chrome prior to 104.0.5112.79 allowed a remote attacker     who convinced a user to enable a specific Enterprise policy to potentially exploit heap corruption via a     crafted HTML page. (CVE-2022-2606)

  - Use after free in Tab Strip in Google Chrome on Chrome OS prior to 104.0.5112.79 allowed a remote attacker     who convinced a user to engage in specific user interactions to potentially exploit heap corruption via     specific UI interactions. (CVE-2022-2607)

  - Use after free in Overview Mode in Google Chrome on Chrome OS prior to 104.0.5112.79 allowed a remote     attacker who convinced a user to engage in specific user interactions to potentially exploit heap     corruption via specific UI interactions. (CVE-2022-2608)

  - Use after free in Nearby Share in Google Chrome on Chrome OS prior to 104.0.5112.79 allowed a remote     attacker who convinced a user to engage in specific user interactions to potentially exploit heap     corruption via specific UI interactions. (CVE-2022-2609)

  - Insufficient policy enforcement in Background Fetch in Google Chrome prior to 104.0.5112.79 allowed a     remote attacker to leak cross-origin data via a crafted HTML page. (CVE-2022-2610)

  - Inappropriate implementation in Fullscreen API in Google Chrome on Android prior to 104.0.5112.79 allowed     a remote attacker to spoof the contents of the Omnibox (URL bar) via a crafted HTML page. (CVE-2022-2611)

  - Side-channel information leakage in Keyboard input in Google Chrome prior to 104.0.5112.79 allowed a     remote attacker who had compromised the renderer process to obtain potentially sensitive information from     process memory via a crafted HTML page. (CVE-2022-2612)

  - Use after free in Input in Google Chrome on Chrome OS prior to 104.0.5112.79 allowed a remote attacker who     convinced a user to enage in specific user interactions to potentially exploit heap corruption via     specific UI interactions. (CVE-2022-2613)

  - Use after free in Sign-In Flow in Google Chrome prior to 104.0.5112.79 allowed a remote attacker to     potentially exploit heap corruption via a crafted HTML page. (CVE-2022-2614)

  - Insufficient policy enforcement in Cookies in Google Chrome prior to 104.0.5112.79 allowed a remote     attacker to leak cross-origin data via a crafted HTML page. (CVE-2022-2615)

  - Inappropriate implementation in Extensions API in Google Chrome prior to 104.0.5112.79 allowed an attacker     who convinced a user to install a malicious extension to spoof the contents of the Omnibox (URL bar) via a     crafted Chrome Extension. (CVE-2022-2616)

  - Use after free in Extensions API in Google Chrome prior to 104.0.5112.79 allowed an attacker who convinced     a user to install a malicious extension to potentially exploit heap corruption via specific UI     interactions. (CVE-2022-2617)

  - Insufficient validation of untrusted input in Internals in Google Chrome prior to 104.0.5112.79 allowed a     remote attacker to bypass download restrictions via a malicious file . (CVE-2022-2618)

  - Insufficient validation of untrusted input in Settings in Google Chrome prior to 104.0.5112.79 allowed an     attacker who convinced a user to install a malicious extension to inject scripts or HTML into a privileged     page via a crafted HTML page. (CVE-2022-2619)

  - Use after free in WebUI in Google Chrome on Chrome OS prior to 104.0.5112.79 allowed a remote attacker who     convinced a user to engage in specific user interactions to potentially exploit heap corruption via     specific UI interactions. (CVE-2022-2620)

  - Use after free in Extensions in Google Chrome prior to 104.0.5112.79 allowed an attacker who convinced a     user to install a malicious extension to potentially exploit heap corruption via specific UI interactions.
    (CVE-2022-2621)

  - Insufficient validation of untrusted input in Safe Browsing in Google Chrome on Windows prior to     104.0.5112.79 allowed a remote attacker to bypass download restrictions via a crafted file.
    (CVE-2022-2622)

  - Use after free in Offline in Google Chrome on Android prior to 104.0.5112.79 allowed a remote attacker who     convinced a user to engage in specific user interactions to potentially exploit heap corruption via     specific UI interactions. (CVE-2022-2623)

  - Heap buffer overflow in PDF in Google Chrome prior to 104.0.5112.79 allowed a remote attacker who     convinced a user to engage in specific user interactions to potentially exploit heap corruption via a     crafted PDF file. (CVE-2022-2624)

  - Microsoft Edge (Chromium-based) Remote Code Execution Vulnerability. (CVE-2022-33636)

  - Microsoft Edge (Chromium-based) Security Feature Bypass Vulnerability. (CVE-2022-33649)

  - Microsoft Edge (Chromium-based) Elevation of Privilege Vulnerability. (CVE-2022-35796)

  - Use after free in FedCM. (CVE-2022-2852)

  - Heap buffer overflow in Downloads. (CVE-2022-2853)

  - Use after free in SwiftShader. (CVE-2022-2854)

  - Use after free in ANGLE. (CVE-2022-2855)

  - Insufficient validation of untrusted input in Intents. (CVE-2022-2856)

  - Use after free in Blink. (CVE-2022-2857)

  - Use after free in Sign-In Flow. (CVE-2022-2858)

  - Use after free in Chrome OS Shell. (CVE-2022-2859)

  - Insufficient policy enforcement in Cookies. (CVE-2022-2860)

  - Inappropriate implementation in Extensions API. (CVE-2022-2861)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The version of Microsoft Edge installed on the remote Windows host is prior to 104.0.1293.47. It is, therefore, affected by multiple vulnerabilities as referenced in the August 5, 2022 advisory.

  - Use after free in Omnibox. (CVE-2022-2603)

  - Use after free in Safe Browsing. (CVE-2022-2604)

  - Out of bounds read in Dawn. (CVE-2022-2605)

  - Use after free in Managed devices API. (CVE-2022-2606)

  - Insufficient policy enforcement in Background Fetch. (CVE-2022-2610)

  - Inappropriate implementation in Fullscreen API. (CVE-2022-2611)

  - Side-channel information leakage in Keyboard input. (CVE-2022-2612)

  - Use after free in Sign-In Flow. (CVE-2022-2614)

  - Insufficient policy enforcement in Cookies. (CVE-2022-2615)

  - Inappropriate implementation in Extensions API. (CVE-2022-2616)

  - Use after free in Extensions API. (CVE-2022-2617)

  - Insufficient validation of untrusted input in Internals. (CVE-2022-2618)

  - Insufficient validation of untrusted input in Settings. (CVE-2022-2619)

  - Use after free in Extensions. (CVE-2022-2621)

  - Insufficient validation of untrusted input in Safe Browsing. (CVE-2022-2622)

  - Use after free in Offline. (CVE-2022-2623)

  - Heap buffer overflow in PDF. (CVE-2022-2624)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

ID	Name	Product	Family	Published	Updated	Severity
164320	GLSA-202208-35 : Chromium, Google Chrome, Microsoft Edge: Multiple Vulnerabilities	Nessus	Gentoo Local Security Checks	8/21/2022	10/25/2023	critical
163893	Microsoft Edge (Chromium) < 104.0.1293.47 Multiple Vulnerabilities	Nessus	Windows	8/6/2022	2/5/2024	critical

Detections

Analytics

Plugins Search

critical

critical