First published: Tue Jan 04 2011(Updated: )
Common Vulnerabilities and Exposures assigned an identifier <a href="https://access.redhat.com/security/cve/CVE-2010-3813">CVE-2010-3813</a> to the following vulnerability: Name: <a href="https://access.redhat.com/security/cve/CVE-2010-3813">CVE-2010-3813</a> Status: Candidate URL: <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-3813">http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-3813</a> Assigned: 20101007 Reference: CONFIRM:<a href="http://support.apple.com/kb/HT4455">http://support.apple.com/kb/HT4455</a> Reference: CONFIRM:<a href="http://support.apple.com/kb/HT4456">http://support.apple.com/kb/HT4456</a> WebKit in Apple Safari before 5.0.3 on Mac OS X 10.5 through 10.6 and Windows, and before 4.1.3 on Mac OS X 10.4, allows remote attackers to bypass the DNS prefetching setting via an HTML LINK element, as demonstrated by an HTML e-mail message that uses a LINK element for X-Confirm-Reading-To functionality. Upstream: Bugzilla: <a href="https://bugs.webkit.org/show_bug.cgi?id=42500">https://bugs.webkit.org/show_bug.cgi?id=42500</a> Trac: <a href="http://trac.webkit.org/changeset/63622">http://trac.webkit.org/changeset/63622</a> This is fixed in webkitgtk 1.2.6
Affected Software | Affected Version | How to fix |
---|---|---|
Safari | <5.0.3 | |
Safari | <4.1.3 | |
WebKitGTK | >1.2.6 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of REDHAT-BUG-667024 has not been explicitly rated but is associated with vulnerabilities in affected versions of Apple Safari and WebKitGTK.
To mitigate REDHAT-BUG-667024, users should upgrade to the latest versions of Apple Safari and WebKitGTK that resolve this vulnerability.
The affected software versions in REDHAT-BUG-667024 include Apple Safari versions prior to 5.0.3 and 4.1.3, as well as WebKitGTK versions prior to 1.2.6.
REDHAT-BUG-667024 is categorized under a vulnerability identified by CVE-2010-3813, which typically pertains to security flaws in web browsers.
While specific workarounds for REDHAT-BUG-667024 may exist, the most effective solution is to promptly update the affected software to the latest secure version.