CVE-2015-1321
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 · uneditedUse-after-free vulnerability in the file picker implementation in Oxide before 1.6.5 allows remote attackers to cause a denial of service (crash) or possibly execute arbitrary code via a crafted webpage.
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 confidenceUse-after-free vulnerability in the file picker implementation in Oxide (Qt WebEngine wrapper used by Ubuntu's web-based click-to-run applications) before version 1.6.5 allows remote attackers to cause a denial of service (crash) or potentially execute arbitrary code via a crafted webpage.
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= 14.04= 14.10= 15.1<= 1.6.4CVSS 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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:N/C:P/I:P/A:P
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.
-
Check if Oxide packages are installedRun 'dpkg -l | grep oxide' or 'apt list --installed 2>/dev/null | grep -i oxide' to list installed Oxide-related packagesAffected if Any Oxide package is installed on Ubuntu 14.04, 14.10, or 15.04/15.10
-
Determine installed Oxide versionRun 'dpkg -l | grep oxide' and examine the version column, or use 'apt-cache policy oxide-qt' if the package is known to be installedAffected if The displayed version number is 1.6.4 or lower
-
Verify Ubuntu release versionRun 'lsb_release -r' or check '/etc/lsb-release' to confirm the Ubuntu releaseAffected if The system runs Ubuntu 14.04, 14.10, or 15.04/15.10 and has Oxide installed
-
Check for click-to-run application usageInspect installed snap packages or click packages related to web apps: run 'snap list' or check for packages in /var/lib/clickAffected if The system has web-based click-to-run applications installed that rely on Oxide WebEngine
The system is affected if it runs Ubuntu 14.04, 14.10, or 15.x with Oxide version 1.6.4 or lower installed, particularly if click-to-run web applications are in use.
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 to version 1.6.5 or later to patch the use-after-free vulnerability in the file picker component.
- Consultation2.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-1321 — 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-1321 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