CVE-2008-0593: Infoleak

Published Feb 9, 2008
·
Updated

Gecko-based browsers, including Mozilla Firefox before 2.0.0.12 and SeaMonkey before 1.1.8, modify the .href property of stylesheet DOM nodes to the final URI of a 302 redirect, which might allow remote attackers to bypass the Same Origin Policy and read sensitive information from the original URL, such as with Single-Signon systems.

Affected Software

38 affected components
Mozilla Firefox=1.5.2
Mozilla Firefox=1.0.2
Mozilla Firefox=0.2
Mozilla Firefox=2.0
Mozilla Firefox=1.5.0.12
Mozilla Firefox=1.5.0.2
Mozilla Firefox<=2.0.0.11
Mozilla Firefox=2.0.0.1
Mozilla Firefox=0.9.2
Mozilla Firefox=2.0.0.10
Mozilla SeaMonkey=1.1.10
Mozilla SeaMonkey
Mozilla SeaMonkey=1.0.3
Mozilla SeaMonkey=1.0.1
Mozilla SeaMonkey=1.0.6
Mozilla SeaMonkey=1.0.9
Mozilla SeaMonkey=1.0
Mozilla SeaMonkey=1.0.99
Mozilla SeaMonkey=1.0.7
Mozilla SeaMonkey=1.0-beta
Mozilla SeaMonkey<=1.1.17
Mozilla SeaMonkey=1.0-alpha
Mozilla SeaMonkey=1.1.12
Mozilla SeaMonkey=1.1
Mozilla SeaMonkey=1.1.14
Mozilla SeaMonkey=1.1.2
Mozilla SeaMonkey=1.0
Mozilla SeaMonkey=1.0.2
Mozilla SeaMonkey=1.0.8
Mozilla SeaMonkey=1.1.11
Mozilla SeaMonkey=1.1.1
Mozilla SeaMonkey=1.0.5
Mozilla SeaMonkey=1.1.15
Mozilla SeaMonkey=1.1.16
Mozilla SeaMonkey=1.0
Mozilla SeaMonkey=1.0
Mozilla SeaMonkey=1.0.4
Mozilla SeaMonkey=1.1.13

Event History

Feb 9, 2008
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
Description

Frequently Asked Questions

1

What is the severity of CVE-2008-0593?

CVE-2008-0593 is classified as a medium severity vulnerability due to its potential to bypass the Same Origin Policy.

2

How do I fix CVE-2008-0593?

To mitigate CVE-2008-0593, users should update their Mozilla Firefox to version 2.0.0.12 or higher or SeaMonkey to version 1.1.8 or higher.

3

What systems are affected by CVE-2008-0593?

CVE-2008-0593 affects Gecko-based browsers, specifically Mozilla Firefox versions before 2.0.0.12 and SeaMonkey versions before 1.1.8.

4

What does CVE-2008-0593 exploit?

CVE-2008-0593 exploits the mishandling of the .href property of stylesheet DOM nodes to allow cross-origin information leakage.

5

Is there a workaround for CVE-2008-0593?

A reliable workaround for CVE-2008-0593 is to disable certain browser features or use alternative browsers that are not affected.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203