CVE-2025-34092 Details
Description
Rejected reason: Neither filed by Chrome nor a valid security vulnerability.
A vulnerability allowing cookie encryption bypass has been identified in Google Chrome's AppBound mechanism. This issue arises from weak path validation logic in the elevation service, which is responsible for decrypting cookies. When Chrome encrypts a cookie key, it includes the executable path of the Chrome process as validation metadata. However, due to inconsistencies in path canonicalization, an attacker can impersonate Chrome by naming a binary 'chrome.exe' and placing it in a similar directory. This exploitation allows retrieval of the encrypted cookie key, enabling access to cookies meant to be restricted to the Chrome process. This vulnerability has been confirmed in Google Chrome versions 127 to 129 with AppBound Encryption enabled. Other Chromium-based browsers may also be affected if they use similar COM-based encryption methods.
Google has acknowledged the vulnerability and is working on a fix. A partial solution is available but disabled by default. Users can monitor for future updates.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No CVSS 3.x data is available for this CVE.
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
No references are available for this CVE.
Weakness Enumeration
No weakness enumeration is available for this CVE.
Affected Products
No affected product data is available for this CVE.
Change History
3 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jul 24, 2025 | CVE Rejected | [email protected] |
| Jul 24, 2025 | CVE Modified | [email protected] |
| Jul 2, 2025 | New CVE Received | [email protected] |