The nsDocShell::OnRedirectStateChange function in docshell/base/nsDocShell.cpp in Mozilla Firefox 3.5.x before 3.5.11 and 3.6.x before 3.6.7
Noroxi assessment
Priority: Monitor (action score 11/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 1.8% (FIRST EPSS); higher than 78.7% of all records.
- Special conditions such as timing or configuration are required.
- Fixed version: xulrunner (Debian:5.0) 1.9.0.19-3; seamonkey (Red Hat:enterprise_linux:3::as) 0:1.0.9-0.57.el3; seamonkey-chat (Red Hat:enterprise_linux:3::as) 0:1.0.9-0.57.el3.
Low priority for now. Upgrade to xulrunner (Debian:5.0) 1.9.0.19-3; seamonkey (Red Hat:enterprise_linux:3::as) 0:1.0.9-0.57.el3; seamonkey-chat (Red Hat:enterprise_linux:3::as) 0:1.0.9-0.57.el3 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
The nsDocShell::OnRedirectStateChange function in docshell/base/nsDocShell.cpp in Mozilla Firefox 3.5.x before 3.5.11 and 3.6.x before 3.6.7, and SeaMonkey before 2.0.6, allows remote attackers to spoof the SSL security status of a document via vectors involving multiple requests, a redirect, and the history.back and history.forward JavaScript functions.
- Published
- Jul 30, 2010
- Updated
- Jun 16, 2026
- EPSS
- 1.9% · 79th percentile
- CWE
- CWE-264
Report tools
Action score
11
Monitor
Low priority for now.
- CVSS
- 10 / 40 · 2.6 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 1.9%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- mozilla firefox3.5.1
- mozilla firefox3.5.10
- mozilla firefox3.5.2
- mozilla firefox3.5.3
- mozilla firefox3.5.4
- mozilla firefox3.5.5
- mozilla firefox3.5.6
- mozilla firefox3.5.7
- mozilla firefox3.5.9
- mozilla firefox3.6.1
- mozilla firefox3.6.2
- mozilla firefox3.6.3
- mozilla firefox3.6.4
- mozilla firefox3.6.6
- mozilla seamonkeyup to 2.0.5 inclusive
- mozilla seamonkey1.0
- mozilla seamonkey1.0.1
- mozilla seamonkey1.0.2
- mozilla seamonkey1.0.3
- mozilla seamonkey1.0.4
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:5.0 | xulrunner | before 1.9.0.19-3 | 1.9.0.19-3 |
| Red Hat:enterprise_linux:3::as | seamonkey | before 0:1.0.9-0.57.el3 | 0:1.0.9-0.57.el3 |
| Red Hat:enterprise_linux:3::as | seamonkey-chat | before 0:1.0.9-0.57.el3 | 0:1.0.9-0.57.el3 |
| Red Hat:enterprise_linux:3::as | seamonkey-debuginfo | before 0:1.0.9-0.57.el3 | 0:1.0.9-0.57.el3 |
| Red Hat:enterprise_linux:3::as | seamonkey-devel | before 0:1.0.9-0.57.el3 | 0:1.0.9-0.57.el3 |
| Red Hat:enterprise_linux:3::as | seamonkey-dom-inspector | before 0:1.0.9-0.57.el3 | 0:1.0.9-0.57.el3 |
| Red Hat:enterprise_linux:3::as | seamonkey-js-debugger | before 0:1.0.9-0.57.el3 | 0:1.0.9-0.57.el3 |
| Red Hat:enterprise_linux:3::as | seamonkey-mail | before 0:1.0.9-0.57.el3 | 0:1.0.9-0.57.el3 |
| Red Hat:enterprise_linux:3::as | seamonkey-nspr | before 0:1.0.9-0.57.el3 | 0:1.0.9-0.57.el3 |
| Red Hat:enterprise_linux:3::as | seamonkey-nspr-devel | before 0:1.0.9-0.57.el3 | 0:1.0.9-0.57.el3 |
| Red Hat:enterprise_linux:3::as | seamonkey-nss | before 0:1.0.9-0.57.el3 | 0:1.0.9-0.57.el3 |
| Red Hat:enterprise_linux:3::as | seamonkey-nss-devel | before 0:1.0.9-0.57.el3 | 0:1.0.9-0.57.el3 |
| Red Hat:enterprise_linux:4::as | firefox | before 0:3.6.7-2.el4 | 0:3.6.7-2.el4 |
| Red Hat:enterprise_linux:4::as | firefox-debuginfo | before 0:3.6.7-2.el4 | 0:3.6.7-2.el4 |
| Red Hat:enterprise_linux:4::as | seamonkey | before 0:1.0.9-60.el4 | 0:1.0.9-60.el4 |
| Red Hat:enterprise_linux:4::as | seamonkey-chat | before 0:1.0.9-60.el4 | 0:1.0.9-60.el4 |
| Red Hat:enterprise_linux:4::as | seamonkey-debuginfo | before 0:1.0.9-60.el4 | 0:1.0.9-60.el4 |
| Red Hat:enterprise_linux:4::as | seamonkey-devel | before 0:1.0.9-60.el4 | 0:1.0.9-60.el4 |
| Red Hat:enterprise_linux:4::as | seamonkey-dom-inspector | before 0:1.0.9-60.el4 | 0:1.0.9-60.el4 |
| Red Hat:enterprise_linux:4::as | seamonkey-js-debugger | before 0:1.0.9-60.el4 | 0:1.0.9-60.el4 |
| Red Hat:enterprise_linux:4::as | seamonkey-mail | before 0:1.0.9-60.el4 | 0:1.0.9-60.el4 |
| Red Hat:enterprise_linux:5::client | firefox | before 0:3.6.7-2.el5 | 0:3.6.7-2.el5 |
| Red Hat:enterprise_linux:5::client | firefox-debuginfo | before 0:3.6.7-2.el5 | 0:3.6.7-2.el5 |
| Red Hat:enterprise_linux:5::client_workstation | xulrunner | before 0:1.9.2.7-2.el5 | 0:1.9.2.7-2.el5 |
+2
Same product
mozilla: all recordsOther highest-scoring records for the same primary product.
- CVE-2010-3765Mozilla Firefox 3.5.x through 3.5.14 and 3.6.x through 3.6.11, Thunderbird 3.1.6 before 3.1.6 and 3.0.x before 3.0.10, and SeaMonkey 2.x befKEV94Now
- CVE-2019-11708Insufficient vetting of parameters passed with the Prompt:Open IPC message between child and parent processes can result in the non-sandboxeKEV87Now
- CVE-2015-4495The PDF reader in Mozilla Firefox before 39.0.3, Firefox ESR 38.x before 38.1.1, and Firefox OS before 2.2 allows remote attackers to bypassKEV86Now
- CVE-2013-1690Mozilla Firefox before 22.0, Firefox ESR 17.x before 17.0.7, Thunderbird before 17.0.7, and Thunderbird ESR 17.x before 17.0.7 do not properKEV86Now
- CVE-2019-17026Incorrect alias information in IonMonkey JIT compiler for setting array elements could lead to a type confusion.KEV79This week
- CVE-2024-9680An attacker was able to achieve code execution in the content process by exploiting a use-after-free in Animation timelines.KEV76This week
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:xulrunner | 1.9.0.19-3 · Debian:5.0 | Package registry (OSV) |
| red hat:firefox | 0:3.6.7-2.el4 · Red Hat:enterprise_linux:4::as | Package registry (OSV) |
| red hat:seamonkey | 0:1.0.9-0.57.el3 · Red Hat:enterprise_linux:3::as | Package registry (OSV) |
| red hat:seamonkey-chat | 0:1.0.9-0.57.el3 · Red Hat:enterprise_linux:3::as | Package registry (OSV) |
| red hat:seamonkey-debuginfo | 0:1.0.9-0.57.el3 · Red Hat:enterprise_linux:3::as | Package registry (OSV) |
| red hat:seamonkey-devel | 0:1.0.9-0.57.el3 · Red Hat:enterprise_linux:3::as | Package registry (OSV) |
| red hat:seamonkey-dom-inspector | 0:1.0.9-0.57.el3 · Red Hat:enterprise_linux:3::as | Package registry (OSV) |
| red hat:seamonkey-js-debugger | 0:1.0.9-0.57.el3 · Red Hat:enterprise_linux:3::as | Package registry (OSV) |
| red hat:seamonkey-mail | 0:1.0.9-0.57.el3 · Red Hat:enterprise_linux:3::as | Package registry (OSV) |
| red hat:seamonkey-nspr | 0:1.0.9-0.57.el3 · Red Hat:enterprise_linux:3::as | Package registry (OSV) |
| red hat:seamonkey-nspr-devel | 0:1.0.9-0.57.el3 · Red Hat:enterprise_linux:3::as | Package registry (OSV) |
| red hat:seamonkey-nss | 0:1.0.9-0.57.el3 · Red Hat:enterprise_linux:3::as | Package registry (OSV) |
| red hat:seamonkey-nss-devel | 0:1.0.9-0.57.el3 · Red Hat:enterprise_linux:3::as | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- none
- Integrity
- P · data or configuration can be modified
- Availability
- none
- Attack complexity
- High
- Confidentiality impact
- None
- Integrity impact
- P
- Availability impact
- None
Weakness class (CWE)
CWE-264 · Permissions, Privileges, and Access ControlsCVSS vector
AV:N/AC:H/Au:N/C:N/I:P/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.