MediumPublic exploit

UXSS via Sandboxing Bypass in Blink (Chrome <62.0.3202.62)

IdentifiersCVE-2017-5124CWE-264

CVE-2017-5124 is a universal cross-site scripting (UXSS) vulnerability in the Blink rendering engine used by Google Chrome prior to version 62.0.3202.62. The vulnerability arises from incorrect application of sandboxing when processing MHTML pages, allowing a remote attacker to inject arbitrary scripts or HTML into the context of another origin.

For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

Start free trial

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows a remote attacker to execute arbitrary scripts in the context of the victim's browser session, potentially leading to session hijacking, data theft, or further compromise of the user's system via browser-based attacks.

Mitigation

If you can’t patch tonight, do this now.

As a temporary mitigation, avoid opening MHTML files from untrusted sources and consider disabling MHTML handling in the browser until the patch is applied.

Remediation

Patch, then assume compromise.

Upgrade to Google Chrome version 62.0.3202.62 or later, where the sandboxing issue in Blink has been properly addressed.

PUBLIC EXPLOITS

Exploits

1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos (1 hidden).

VALID 1 / 2 TOTALView more in app

CVE-2017-5124MaturityPoCVerified exploit

This repository is a proof-of-concept (PoC) exploit for CVE-2017-5124, a Universal Cross-Site Scripting (UXSS) vulnerability in Google Chrome (tested on version 61.0.3163.100). The repository contains three files: a PHP script (PoC.php) that serves a specially crafted MHT file (PoC.mht), and a README.md with usage instructions and a demo URL. The MHT file contains an XSLT stylesheet that injects a hidden iframe loading 'https://google.com', and a script that alerts the current location origin, demonstrating the UXSS. The exploit is triggered by visiting the PoC.php endpoint, which serves the malicious MHT file to the browser. The main attack vector is browser-based, targeting Chrome's handling of MHTML and XSLT. The repository is a functional PoC and does not include weaponized or customizable payloads.

Bo0oMDisclosed Nov 13, 2017phpxmlbrowser

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType

DebianDebian Linuxoperating_system

GoogleChromeapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

ACTIVITY FEED

Recent activity

No public activity tracked yet. Mallory keeps watching.

0 SOURCESView more in app

No public activity observed for this vulnerability.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.

Start free trial

Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity