A cookie encryption bypass flaw was found in Google Chrome. When Chrome encrypts a cookie key, it records its executable path as validation metadata. Later, when decrypting, the elevation service compares the requesting process’s path to this stored path. However, due to path canonicalization inconsistencies, an attacker can impersonate Chrome and successfully retrieve the encrypted cookie key.

Rejected reason: Neither filed by Chrome nor a valid security vulnerability.

A cookie encryption bypass vulnerability exists in Google Chrome’s AppBound mechanism due to weak path validation logic within the elevation service. When Chrome encrypts a cookie key, it records its own executable path as validation metadata. Later, when decrypting, the elevation service compares the requesting process’s path to this stored path. However, due to path canonicalization inconsistencies, an attacker can impersonate Chrome (e.g., by naming their binary chrome.exe and placing it in a similar path) and successfully retrieve the encrypted cookie key. This allows malicious processes to retrieve cookies intended to be restricted to the Chrome process only. Confirmed in Google Chrome with AppBound Encryption enabled. Other Chromium-based browsers may be affected if they implement similar COM-based encryption mechanisms.

Уязвимость механизма обработки файлов cookie веб-браузера Google Chrome, связанная с недостатками процедуры аутентификации, позволяющая нарушителю повысить свои привилегии и получить cookie-файлы