CVE-2005-2395 json
Mozilla Firefox 1.0.4 and 1.0.5 does not choose the challenge with the strongest authentication scheme available as required by RFC2617, wh…
published 2005-07-27 21 y ago modified 2026-06-16 4 mo ago also EUVD-2005-2396
- cvss
- 5.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.4%
- EPSS 2.4% chance of exploitation in 30 days, percentile 83%
- public exploits
- 0
- none known
Summary
Mozilla Firefox 1.0.4 and 1.0.5 does not choose the challenge with the strongest authentication scheme available as required by RFC2617, which might cause credentials to be sent in plaintext even if an encrypted channel is available.
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-2395 updated cvss 2.6
firefox: Does not choose the challenge with the strongest authentication scheme available as required by RFC2617
-
Red Hat Enterprise Linux 5 firefox Red Hat Enterprise Linux 6 firefoxaffected: no fix available
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
2.38% chance of exploitation in the next 30 days, higher than 83% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- securityfocus.com http://www.securityfocus.com/archive/1/405666 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
References
-
securityfocus.com
/archive/1/405666
mailing-list, exploit
-
osvdb.org
/19002
vdb-entry
- bugzilla.mozilla.org /show_bug.cgi?id=281851
-
securityreason.com
/securityalert/8
third-party-advisory
- securiteam.com /securitynews/5PP0L00GUQ.html
-
exchange.xforce.ibmcloud.com
/vulnerabilities/22272
vdb-entry
-
securityfocus.com
/bid/14325
vdb-entry
Sources
- CVE List CVE-2005-2395
- NVD CVE-2005-2395
Fencer Vulns 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.