Skip to content
Fencer Intel
low 2.6

CVE-2005-0593 json

Firefox before 1.0.1 and Mozilla before 1.7.6 allows remote attackers to spoof the SSL "secure site" lock icon via (1) a web site that does…

published 21y ago modified 5mo ago also EUVD-2005-0594

cvss
2.6
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.7%
EPSS 1.7% chance of exploitation in 30 days, percentile 77%
public exploits
0
none known

Summary

Firefox before 1.0.1 and Mozilla before 1.7.6 allows remote attackers to spoof the SSL "secure site" lock icon via (1) a web site that does not finish loading, which shows the lock of the previous site, (2) a non-HTTP server that uses SSL, which causes the lock to be displayed when the SSL handshake is completed, or (3) a URL that generates an HTTP 204 error, which updates the icon and location information but does not change the display of the original site.

Patch / fix

  • firefox RHEL 4 1.0.1-1.4.3

red hat advisories RHSA-2005:176

Is CVE-2005-0593 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2005-0593 updated

security flaw

  • Red Hat Enterprise Linux AS version 4 firefox 1.0.1-1.4.3 Red Hat Enterprise Linux Desktop version 4 firefox 1.0.1-1.4.3 Red Hat Enterprise Linux ES version 4 firefox 1.0.1-1.4.3 Red Hat Enterprise Linux WS version 4 firefox 1.0.1-1.4.3
    fixed: vendor fix RHSA-2005:176

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.66% chance of exploitation in the next 30 days, higher than 77% of all scored CVEs (FIRST EPSS, 2026-11-18).

CVSS scores

assigned by version score vector
NVD 2.0 2.6 AV:N/AC:H/Au:N/C:N/I:P/A:N

Classification

Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.