CVE-2019-5496
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 · uneditedOncommand Insight versions prior to 7.3.5 shipped without certain HTTP Security headers configured which could allow an attacker to obtain sensitive information via unspecified vectors.
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 confidenceOncommand Insight versions prior to 7.3.5 were shipped without certain HTTP Security headers configured. The absence of protective HTTP headers (such as HSTS, X-Frame-Options, X-Content-Type-Options, or CSP) could allow attackers to obtain sensitive information via web-based vectors that exploit the missing header protections.
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< 7.3.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
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/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.
-
Identify Oncommand Insight versionLog into the Oncommand Insight web interface and navigate to the Help > About page, or check the installation directory for a version file. Alternatively, check the software inventory or the SANscreen server where Oncommand Insight is installed.Affected if The installed version is any release prior to 7.3.5 (e.g., 7.3.0 through 7.3.4)
-
Capture HTTP response headers from the Oncommand Insight web applicationUsing a browser's developer tools (Network tab), navigate to the Oncommand Insight login page or main dashboard, then inspect the HTTP response headers. Alternatively, use a command-line tool like curl -I https://<your-oci-server> to retrieve response headers.Affected if The response does not contain the HSTS header (Strict-Transport-Security)
-
Check for X-Frame-Options headerInspect the same HTTP response headers captured in the previous step. Look for the header named X-Frame-Options in the response.Affected if The X-Frame-Options header is missing from the HTTP response
-
Check for X-Content-Type-Options headerInspect the HTTP response headers for the X-Content-Type-Options header.Affected if The X-Content-Type-Options header is missing from the HTTP response
-
Check for Content Security Policy (CSP) headerInspect the HTTP response headers for any Content-Security-Policy or Content-Security-Policy-Report-Only header.Affected if No CSP header is present in the HTTP response
The environment is affected if Oncommand Insight version is below 7.3.5 OR if any of the protective HTTP headers (HSTS, X-Frame-Options, X-Content-Type-Options, CSP) are missing from web responses.
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 data7.3.5
Configure missing HTTP security headers on the Oncommand Insight web server/application to protect against information disclosure attacks.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-5496 — 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-5496 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