CVE-2016-0293
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 · uneditedCross-site scripting (XSS) vulnerability in IBM BigFix Platform (formerly Tivoli Endpoint Manager) 9.x before 9.1.8 and 9.2.x before 9.2.8 allows remote attackers to inject arbitrary web script or HTML via a modified .beswrpt file.
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 confidenceCross-site scripting (XSS) vulnerability in IBM BigFix Platform versions 9.x before 9.1.8 and 9.2.x before 9.2.8 allows remote attackers to inject arbitrary web script or HTML via modified .beswrpt files. This is a stored XSS vector where malicious content is embedded in the .beswrpt report file format processed by the platform.
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= 9.2.0= 9.2.1= 9.2.2= 9.2.3= 9.2.4= 9.2.5= 9.2.6= 9.2.7= 9.0.5= 9.0.6= 9.0.7= 9.0.8CVSS 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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify IBM BigFix Platform versionLocate the installed version of the BigFix Platform software. This is typically accessible through the BigFix console under the Help or About section, or via command line tools provided by the platform.Affected if The installed version is 9.0.5, 9.0.6, 9.0.7, 9.0.8, 9.2.0, 9.2.1, 9.2.2, 9.2.3, 9.2.4, 9.2.5, 9.2.6, or 9.2.7.
-
Compare version against fixed releasesCompare your installed version number against the fixed releases. The vulnerability is patched in versions 9.1.8 and later for the 9.x branch, and 9.2.8 and later for the 9.2.x branch.Affected if Your version is earlier than 9.1.8 (for 9.x branches) or earlier than 9.2.8 (for 9.2.x branches).
-
Determine if .beswrpt file processing is in useIdentify whether your environment processes .beswrpt report files. This file format is used by BigFix for generating and displaying reports within the platform.Affected if The .beswrpt report file processing feature is active or accessible in your deployment, as this is the attack vector for the stored XSS.
-
Inspect report file handlingExamine how .beswrpt files are processed and rendered within the BigFix interface. The vulnerability allows malicious script injection when modified .beswrpt files are processed.Affected if Users can import or submit .beswrpt files into the platform without sanitization, enabling the stored XSS attack.
You are affected if your IBM BigFix Platform version is 9.0.5 through 9.0.8, or 9.2.0 through 9.2.7, and the .beswrpt report file processing feature is enabled or accessible in your environment.
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 IBM BigFix Platform to version 9.1.8 or later for 9.x branches, or 9.2.8 or later for 9.2.x branches. Additionally, implement input validation and sanitization for .beswrpt file processing to block malicious script injection.
- Consultation2.0 h
- Implementation4.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 $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-0293 — 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-2016-0293 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