CVE-2008-3644: Infoleak
Published Nov 17, 2008
·Updated
Apple Safari before 3.2 does not properly prevent caching of form data for form fields that have autocomplete disabled, which allows local users to obtain sensitive information by reading the browser's page cache.
Affected Software
42 affected components
Safari=1.3.2
Safari=2
Safari=1.1.1
Safari=3.0.4
Safari=1.2.2
Safari=2.0.1
Safari=3.0.1
Safari=2.0.3
Safari=1.0.3
Safari=2.0.2
Safari=3.0.1
Safari=3.0.2
Safari=1.0
Safari=2.0.4_419.3
Safari=3.1.1
Safari=1.3
Safari=3.0.3
Safari=3.0.2
Safari=3.1
Safari=1.2.5
Safari=3.0.3
Safari=3.0
Safari=2.0
Safari=1.2.4
Safari=1.2.1
Safari=1.0-beta
Safari=0.8
Safari=2.0.4
Safari=1.0-beta2
Safari=1.1
Safari=1.3.1
Safari=1.2
Safari
Safari<=3.1.2
Safari=2.0_pre
Safari=3.0
Safari=3.0.4_beta
Safari=2.0.3_417.9.3
Safari=1.2.3
Safari=3.0.4_beta
Safari=3
Safari=0.9
Event History
Nov 17, 2008
CVE Published
via MITRE·06:00 PM
Data Sourced
via MITRE·06:00 PM
Description
Frequently Asked Questions
1
What is the severity of CVE-2008-3644?
CVE-2008-3644 is classified as a moderate severity vulnerability that allows local users to access sensitive information.
2
How do I fix CVE-2008-3644?
The fix for CVE-2008-3644 is to update Apple Safari to version 3.2 or later.
3
What type of vulnerability is CVE-2008-3644?
CVE-2008-3644 is a vulnerability related to improper caching of form data in Apple Safari.
4
Who is affected by CVE-2008-3644?
Users of Apple Safari versions prior to 3.2 are affected by CVE-2008-3644.
5
What does CVE-2008-3644 allow attackers to do?
CVE-2008-3644 allows local users to read the browser's page cache and obtain sensitive information.