CVE-2012-0956
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 · uneditedubiquity-slideshow-ubuntu before 58.2, during installation, allows remote man-in-the-middle attackers to execute arbitrary web script or HTML and read arbitrary files via a crafted attribute in the <a> tag of a Twitter feed.
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 ubiquity-slideshow-ubuntu installer component before version 58.2 fails to properly sanitize input from a Twitter feed displayed during installation. A remote man-in-the-middle attacker positioned between the installer and Twitter's servers could inject malicious attributes into <a> tags, enabling cross-site scripting (XSS) attacks and potentially reading arbitrary files on the system through the vulnerable feed parser.
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<= 58.1= 49= 52= 53= 54= 55= 56= 57= 58CVSS 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 ubiquity-slideshow-ubuntu package is installedRun 'dpkg -l ubiquity-slideshow-ubuntu' or 'apt show ubiquity-slideshow-ubuntu' to list the installed package and versionAffected if The package version is 58.1 or earlier, or matches one of these versions: 49, 52, 53, 54, 55, 56, 57, or 58
-
Identify the installation media sourceExamine the ISO or installation medium being used. Check the file /usr/share/ubiquity-slideshow-ubuntu or the packaged version included in the installer environmentAffected if The ubiquity-slideshow-ubuntu component included in the installation medium matches an affected version listed above
-
Determine if the Twitter feed feature is activeInspect the slideshow configuration files in /usr/share/ubiquity-slideshow-ubuntu/ for Twitter feed integration code, or examine any configuration that references fetching content from Twitter during the installation processAffected if The installer is configured to fetch and display a Twitter feed during the slideshow presentation
You are affected if the ubiquity-slideshow-ubuntu version in your installation media is 58.1 or earlier (or one of the specific versions 49, 52-58) and the Twitter feed display feature is enabled during installation.
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 ubiquity-slideshow-ubuntu to version 58.2 or later, which implements proper input sanitization for the Twitter feed. If running older installation media, ensure network connections during installation are trusted or use offline installation methods.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-0956 — 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-2012-0956 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