CVE-2019-4366
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 · uneditedIBM Cognos Analytics 11.0 and 11.1 is susceptible to an information disclosure vulnerability where an attacker could gain access to cached browser data. IBM X-Force ID: 161748.
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 · moderate confidenceIBM Cognos Analytics 11.0 and 11.1 contains an information disclosure vulnerability where an attacker with access to the user's browser or cached data could obtain sensitive information from cached browser data. This is a client-side information disclosure issue stemming from improper cache control on sensitive responses.
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= 11.0.0= 11.1.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
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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.
-
Identify IBM Cognos Analytics versionCheck the installed version of IBM Cognos Analytics by accessing the About section in the product UI, or by querying the Cognos Configuration or installation directory for version information. Compare against the affected versions 11.0.0 and 11.1.0.Affected if The installed version is exactly 11.0.0 or 11.1.0
-
Inspect HTTP response headers for sensitive endpointsUse browser developer tools (Network tab) or an HTTP proxy to capture responses from the Cognos Analytics web interface. Examine the HTTP response headers, specifically looking for the Cache-Control header on endpoints that return sensitive data such as user profiles, credentials, or data reports.Affected if The Cache-Control header is missing, or does not include no-store, no-cache, or must-revalidate directives on sensitive endpoints
-
Verify browser cache for stored sensitive dataOpen the browser's cached files view (for Chrome: chrome://cache/, or check the application data directory). Search for cached copies of Cognos Analytics pages that may contain sensitive user information, session data, or authentication credentials.Affected if Sensitive Cognos Analytics content is found cached in the browser
A user is affected if they run IBM Cognos Analytics version 11.0.0 or 11.1.0 AND the application fails to send proper Cache-Control headers (no-store, no-cache, must-revalidate) on sensitive responses, allowing data to be stored in the browser cache.
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 dataConfigure the application and underlying web server to send appropriate HTTP cache-control headers (no-store, no-cache, must-revalidate) to prevent sensitive data from being cached in the browser, and consider implementing cache-clearing mechanisms.
- Consultation2.0 h
- Implementation2.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,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-4366 — 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-2019-4366 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