CVE-2016-0397
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 · uneditedWebReports in IBM BigFix Platform (formerly Tivoli Endpoint Manager) 9.x before 9.5.2 allows remote attackers to obtain sensitive information by sniffing the network for HTTP traffic.
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 confidenceWebReports in IBM BigFix Platform versions 9.x before 9.5.2 transmits HTTP traffic in cleartext without encryption, allowing attackers on the same network segment to sniff and capture sensitive information being transmitted between clients and the WebReports server.
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.0= 9.1= 9.2= 9.5CVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm WebReports is deployedCheck if the IBM BigFix WebReports component is installed and running on the system. This is typically accessible via a web browser to the server's web interface.Affected if WebReports is accessible on the network and is in use
-
Identify the installed BigFix Platform versionAccess the BigFix console or check the installed version through the BigFix Administration tool. The version is typically visible in the console under Help > About BigFix or in the server's version information.Affected if The installed version is 9.0, 9.1, 9.2, or 9.5 (any version before 9.5.2)
-
Check WebReports protocol configurationExamine the WebReports server configuration to determine whether it is configured to use HTTP (port 80) or HTTPS (port 443 or similar secure port). This can be verified by attempting to access WebReports via HTTP and observing whether the connection is encrypted.Affected if WebReports is accessible over HTTP (cleartext) rather than HTTPS
-
Inspect network traffic to WebReportsUse a network packet capture tool (such as Wireshark or tcpdump) on the network segment between the client and WebReports server to observe whether sensitive data is transmitted in cleartext.Affected if HTTP traffic containing sensitive information is observed in cleartext on the network
If WebReports is deployed and the installed BigFix Platform version is 9.0, 9.1, 9.2, or 9.5 with HTTP (cleartext) access enabled, the environment is affected by this vulnerability.
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.5.2 or later, which contains the security fix. Alternatively, implement network segmentation and ensure WebReports traffic traverses trusted network paths only.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-0397 — 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-0397 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