Security readout for executives and security teams
Plain-English summary
This flaw affects very old Mozilla Firefox and SeaMonkey versions. Their JavaScript random-number setup used the current time as the seed, making random values easier for a remote attacker to guess. Modern environments are unlikely to be exposed unless legacy browsers remain in use.
Executive priority
Treat as a legacy hygiene issue. It is not flagged as actively exploited in the provided sources, but any remaining affected browsers should be retired or upgraded because they are obsolete and likely carry many additional risks.
Technical view
Mozilla’s JavaScript js_InitRandom function seeded its RNG from current time in Firefox 3.5.x before 3.5.10, Firefox 3.6.x before 3.6.4, and SeaMonkey before 2.0.5. The issue could make seed guessing easier through brute force. Sources identify it as separate from CVE-2008-5913.
Likely exposure
Exposure is limited to systems still running the named legacy Firefox or SeaMonkey versions. The source bundle does not identify server-side products, plugins, or modern browser branches as affected.
Exploitation context
The CVE states remote attackers could more easily guess the RNG seed via brute force. The source bundle does not show KEV listing, confirmed active exploitation, public exploit status, or real-world incident evidence.
Researcher notes
Evidence is concise: CVE description, OVAL entry, and Mozilla Bugzilla reference. No CVSS, CWE, or detailed exploitability data is provided in the bundle. Avoid extrapolating beyond predictable RNG seeding in the named browser versions.
Mitigation direction
- Upgrade Firefox to 3.5.10, 3.6.4, or later supported versions.
- Upgrade SeaMonkey to 2.0.5 or later supported versions.
- Remove unsupported legacy browsers from managed endpoints.
- Check Mozilla guidance before relying on compensating controls.
Validation and detection
- Inventory endpoints for Firefox 3.5.x, Firefox 3.6.x, and SeaMonkey versions.
- Confirm Firefox versions are at least 3.5.10 or 3.6.4 where applicable.
- Confirm SeaMonkey versions are at least 2.0.5 where applicable.
- Use the referenced OVAL definition if your scanner supports it.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2010-3400 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- oval:org.mitre.oval:def:7339CVE reference · vdb-entry, signature
- https://bugzilla.mozilla.org/show_bug.cgi?id=475585CVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.