First published: Fri Apr 10 2015(Updated: )
The private-browsing implementation in WebKit in Apple Safari before 6.2.5, 7.x before 7.1.5, and 8.x before 8.0.5 places browsing history into an index, which might allow local users to obtain sensitive information by reading index entries.
Credit: product-security@apple.com
Affected Software | Affected Version | How to fix |
---|---|---|
Apple Safari | <=6.2.4 | |
Apple Safari | =7.0 | |
Apple Safari | =7.0.1 | |
Apple Safari | =7.0.2 | |
Apple Safari | =7.0.3 | |
Apple Safari | =7.0.4 | |
Apple Safari | =7.0.5 | |
Apple Safari | =7.0.6 | |
Apple Safari | =7.1.0 | |
Apple Safari | =7.1.1 | |
Apple Safari | =7.1.2 | |
Apple Safari | =7.1.3 | |
Apple Safari | =7.1.4 | |
Apple Safari | =8.0.0 | |
Apple Safari | =8.0.1 | |
Apple Safari | =8.0.2 | |
Apple Safari | =8.0.3 | |
Apple Safari | =8.0.4 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2015-1127 has been rated as a medium severity vulnerability due to the potential exposure of sensitive browsing history.
To fix CVE-2015-1127, upgrade your Apple Safari to version 6.2.5, 7.1.5, or 8.0.5 or later.
CVE-2015-1127 affects Apple Safari versions before 6.2.5, all 7.x versions before 7.1.5, and all 8.x versions before 8.0.5.
CVE-2015-1127 may allow local users to read sensitive information by accessing the browsing history stored in the index.
Yes, CVE-2015-1127 is specifically associated with Apple Safari running on macOS and iOS.