CVE-2019-4343
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 allows overly permissive cross-origin resource sharing which could allow an attacker to transfer private information. An attacker could exploit this vulnerability to access content that should be restricted. IBM X-Force ID: 161422.
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 overly permissive cross-origin resource sharing (CORS) configuration that allows unauthorized cross-origin requests to access sensitive resources. An attacker could exploit this by making requests from a malicious website to the Cognos server, potentially exfiltrating private data that should be restricted by same-origin policy.
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.0all versionsCVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Identify IBM Cognos Analytics installationLocate Cognos installation directory, typically under /opt/ibm/cognos or C:\Program Files\ibm\cognos on Windows. Check for the bi directory containing the Cognos binaries.Affected if IBM Cognos Analytics 11.0.0 or 11.1.0 is installed and accessible over the network
-
Check IBM Cognos Analytics versionLocate the version file in the installation directory, commonly at <cognos_install>/bin64/_jvm\.manifest or check the About information in the Cognos Administration console.Affected if The installed version is exactly 11.0.0 or 11.1.0
-
Identify NetApp OnCommand Insight installationCheck for OnCommand Insight installation, typically in /opt/NetApp/ocif or C:\Program Files\NetApp\OnCommand Insight on Windows. The service is often named OnCommandInsight or ocif.Affected if NetApp OnCommand Insight of any version is installed and running
-
Inspect CORS configuration in IBM Cognos AnalyticsExamine the web.xml or ibm-cognos.xml configuration file in <cognos_install>/webapps/p2pd/WEB-INF/ or <cognos_install>/configuration/. Look for CORS-related filter definitions and the allowedOrigins, allowedMethods, or allowedHeaders parameters.Affected if CORS filter is present with wildcard or unspecified origin restrictions (e.g., * or empty origin list allowing any domain)
-
Inspect CORS configuration in NetApp OnCommand InsightCheck the server configuration files in the OnCommand Insight installation directory for CORS settings. Common locations include <install_dir>/wildfly/standalone/configuration/ or the Insight server XML configuration files.Affected if CORS configuration allows unrestricted or wildcard origin access
A user is affected if they run IBM Cognos Analytics 11.0.0 or 11.1.0, or any version of NetApp OnCommand Insight, with CORS enabled and the configuration permitting arbitrary cross-origin requests.
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 CORS headers on the IBM Cognos Analytics server to whitelist only trusted origins and restrict allowed methods and headers. Upgrade to a patched version if available from IBM.
- Consultation2.0 h
- Implementation2.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-4343 — 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-4343 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