Outdated Web Browsers

Hosts run web browser versions that are missing security fixes, leaving users open to compromise from malicious or compromised websites.

SeverityHigh
CVSS 3.18.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H Open in the calculator
CVSS 4.08.7 CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N Open in the calculator
CWECWE-1395: Dependency on Vulnerable Third-Party Component
OWASP Top 10A03:2025 Software Supply Chain Failures
MITRE ATT&CKT1189 Drive-by Compromise, T1203 Exploitation for Client Execution
CategoryOutdated Components

Description

One or more hosts run versions of Google Chrome, Microsoft Edge, Mozilla Firefox or other browsers that are missing security fixes. Browser vendors release security updates very frequently, weekly in Chrome's case, and many fix memory corruption in the rendering and JavaScript engines that can be triggered simply by visiting a web page. Browsers update themselves by default, but an update takes effect only when the browser restarts, and updating can be blocked by policy, by a broken update service, or by installations that the user cannot update.

An attacker can compromise a user of an affected browser by luring them to a malicious page, or by placing malicious content on a legitimate site or advertisement, with no further action needed from the user. Exploiting the renderer gives code execution inside the browser's sandbox, and combining it with a sandbox escape or an operating system flaw gives control of the host with the user's privileges, from which the attacker can steal session cookies and saved credentials and move further into the network. Several such flaws are exploited in the wild each year before or shortly after a fix is released, and browser flaws exploited in the wild include the WebP image vulnerability CVE-2023-4863; many are listed in CISA's Known Exploited Vulnerabilities (KEV) catalogue.

The finding is identified by authenticated scans that read installed browser versions, by management tool inventories, or from the browser's About page, and scanners report one result per missing release. Common variants are browsers left open for weeks so that a downloaded update waits for a restart, per-user installations in user profiles that central tools do not manage, unsupported browsers still installed on older hosts, and desktop applications built on frameworks such as Electron that embed their own copy of a browser engine.

Remediation

Keep browsers current and make sure updates take effect:

  • Leave automatic updates enabled and enforce them with enterprise policies for Chrome, Edge and Firefox, including a relaunch policy that requires a restart within a few days of an update being downloaded.
  • Manage browsers centrally with the organisation's deployment tool, remove per-user installations that bypass it, and remove browsers that are not needed.
  • Remove unsupported browsers, using Microsoft Edge's Internet Explorer mode for legacy sites that still need it.
  • Update desktop applications that embed browser engines, such as those built on Electron, when their vendors release fixes.
  • Limit the impact of future flaws with browser and endpoint protections, such as site isolation and exploit protection, and by not giving users local administrator rights.

Confirm the fix by checking the browser versions reported by the management tool or the browser's About page, and repeating the scan.

References


Add This Finding to Your Library

In Pental this write-up is in Settings, Library. Add to my library copies it into your own, rated in your firm's CVSS version, ready to put in your own words.

Free trial  ·  No card required

Only need the reporting? Our reporting tool is free and open source, with the same library.


More Patching and Outdated Software Findings

Every Patching and Outdated Software finding