Google Chrome executes DOM calls in response to a javascript: URI in the target attribute of a submit element within a form contained in an inline PDF file, which might allow remote attackers to bypass intended Adobe Acrobat JavaScript restrictions on accessing the document object, as demonstrated by a web site that permits PDF uploads by untrusted users, and therefore has a shared document.domain between the web site and this javascript: URI. NOTE: the researcher reports that Adobe's position is "a PDF file is active content."
References
Link | Resource |
---|---|
http://secniche.org/papers/SNS_09_03_PDF_Silent_Form_Re_Purp_Attack.pdf | Exploit Third Party Advisory |
http://www.securityfocus.com/archive/1/503183/100/0/threaded | Third Party Advisory VDB Entry |
http://secniche.org/papers/SNS_09_03_PDF_Silent_Form_Re_Purp_Attack.pdf | Exploit Third Party Advisory |
http://www.securityfocus.com/archive/1/503183/100/0/threaded | Third Party Advisory VDB Entry |
Configurations
History
21 Nov 2024, 01:02
Type | Values Removed | Values Added |
---|---|---|
References | () http://secniche.org/papers/SNS_09_03_PDF_Silent_Form_Re_Purp_Attack.pdf - Exploit, Third Party Advisory | |
References | () http://www.securityfocus.com/archive/1/503183/100/0/threaded - Third Party Advisory, VDB Entry |
Information
Published : 2009-05-11 15:30
Updated : 2024-11-21 01:02
NVD link : CVE-2009-1598
Mitre link : CVE-2009-1598
CVE.ORG link : CVE-2009-1598
JSON object : View
Products Affected
- chrome
CWE