Ubuntu LinuxOperating system · Canonical
CVE-2015-1332
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 · uneditedThe oxide::JavaScriptDialogManager function in oxide-qt before 1.9.1 as packaged in Ubuntu 15.04 and Ubuntu 14.04 allows remote attackers to cause a denial of service (application crash) or execute arbitrary code via a crafted website.
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 · high confidenceThe oxide::JavaScriptDialogManager function in oxide-qt before version 1.9.1 contains a vulnerability that allows remote attackers to trigger application crashes or achieve arbitrary code execution through malicious JavaScript dialog interactions. This affects the Qt-based browser engine component packaged with Ubuntu 14.04 and 15.04.
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
= 14.04= 15.10<= 1.9.0CVSS 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
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Verify oxide-qt package installationOn Ubuntu systems, run: dpkg -l | grep oxide-qt or apt list --installed 2>/dev/null | grep oxide-qtAffected if The package is not installed or not found, the system is not affected by this specific vulnerability in oxide-qt
-
Determine installed oxide-qt versionRun: dpkg -s oxide-qt 2>/dev/null | grep Version, or check the package details in your system package managerAffected if The installed version is 1.9.0 or lower, indicating the vulnerable JavaScriptDialogManager function is present
-
Identify applications using the oxide Qt browser engineCheck for applications that bundle or depend on oxide-qt, such as Ubuntu web browser or custom Qt applications with embedded webviews. Review installed software lists or application dependenciesAffected if Applications using the oxide Qt browser engine component are present and process untrusted JavaScript content
-
Assess exposure to untrusted JavaScriptDetermine if the oxide-based browser or webview component can be triggered to load JavaScript from untrusted or remote sources, such as browsing untrusted websites or rendering remote HTML contentAffected if The oxide browser engine can execute JavaScript from untrusted sources, enabling the malicious dialog interaction attack vector to function
A system is affected if oxide-qt version 1.9.0 or lower is installed AND an application using the oxide Qt browser engine can execute untrusted JavaScript content, allowing exploitation of the vulnerable JavaScriptDialogManager function.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade oxide-qt to version 1.9.1 or later to patch the vulnerable JavaScriptDialogManager function. If patching is not immediately feasible, restrict access to untrusted websites and disable JavaScript in contexts handling sensitive data.
Fix this in Ubuntu Linux
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2015-1332 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2015-1332 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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