Cross-domain vulnerability in the WorkerPool API in Google Gears before 0.5.4.2 allows remote attackers to bypass the Same Origin Policy and the intended access restrictions of the allowCrossOrigin function by hosting an assumed-safe file type containing Google Gear commands on the target domain, then accessing that file from the attacking domain, whose response headers are not checked and cause the worker code to run in the target domain.
References
Configurations
Configuration 1 (hide)
|
History
21 Nov 2024, 00:56
Type | Values Removed | Values Added |
---|---|---|
References | () http://blog.watchfire.com/wfblog/2008/12/breaking-google-gears-cross-origin-communication-model.html - Exploit | |
References | () http://code.google.com/apis/gears/upcoming/api_workerpool.html#cross_origin - Vendor Advisory | |
References | () http://lists.grok.org.uk/pipermail/full-disclosure/2008-December/066291.html - | |
References | () http://secunia.com/advisories/33062 - Vendor Advisory | |
References | () http://www.securityfocus.com/bid/32698 - | |
References | () https://exchange.xforce.ibmcloud.com/vulnerabilities/47173 - |
Information
Published : 2009-03-24 14:30
Updated : 2025-04-09 00:30
NVD link : CVE-2008-6512
Mitre link : CVE-2008-6512
CVE.ORG link : CVE-2008-6512
JSON object : View
Products Affected
- gears
CWE