dbcve.org
Ubuntu LinuxOperating system · Canonical

CVE-2014-1483

MEDIUM · 5.0 CVSS v2.0 Published 2014-02-06
Fix available
A fix is available. Upgrade to 2.24 / 27.0 or later.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Mozilla Firefox before 27.0 and SeaMonkey before 2.24 allow remote attackers to bypass the Same Origin Policy and obtain sensitive information by using an IFRAME element in conjunction with certain timing measurements involving the document.caretPositionFromPoint and document.elementFromPoint functions.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is a Same Origin Policy (SOP) bypass vulnerability in Mozilla Firefox before 27.0 and SeaMonkey before 2.24. Attackers can exploit timing measurements using document.caretPositionFromPoint and document.elementFromPoint functions within an IFRAME element to infer sensitive information from cross-origin content, violating the browser's security boundary.

MitigationUpgrade Firefox to version 27.0 or later, and SeaMonkey to version 2.24 or later, to obtain the security patch that addresses this SOP bypass.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Ubuntu LinuxOperating system
Affected:= 12.04= 12.10= 13.10
FirefoxWeb browser
Affected:< 27.0
SolarisOperating system
Affected:= 11.3
SeamonkeyApplication
Affected:< 2.24
Suse Linux Enterprise Software Development KitApplication
Affected:= 11.0
OpensuseOperating system
Affected:= 11.4= 12.3= 13.1
Linux Enterprise DesktopOperating system
Affected:= 11
Linux Enterprise ServerOperating system
Affected:= 11

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Authentication
None
Confidentiality
Partial
Integrity
None
Availability
None

AV:N/AC:L/Au:N/C:P/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed browser
    Check the browser name and version. In Firefox, go to Help > About Firefox. In SeaMonkey, go to Help > About SeaMonkey.
    Affected if The browser is Mozilla Firefox or Mozilla SeaMonkey
  2. Check Firefox version
    For Firefox, run 'firefox --version' or check Help > About Firefox. Compare the version number to 27.0.
    Affected if Firefox version is lower than 27.0 (e.g., 26.x, 25.x, etc.)
  3. Check SeaMonkey version
    For SeaMonkey, run 'seamonkey --version' or check Help > About SeaMonkey. Compare the version number to 2.24.
    Affected if SeaMonkey version is lower than 2.24 (e.g., 2.23, 2.22, etc.)

You are affected if you are running Mozilla Firefox below version 27.0 or Mozilla SeaMonkey below version 2.24 on the listed platforms.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to 2.24 / 27.0 or later
Fixed in 2.2427.0
Interim mitigation

Upgrade Firefox to version 27.0 or later, and SeaMonkey to version 2.24 or later, to obtain the security patch that addresses this SOP bypass.

Fix this in Ubuntu Linux Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-1483 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2014-1483 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data