CVE-2017-13652
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 · uneditedNetApp OnCommand Insight version 7.3.0 and versions prior to 7.2.0 are susceptible to clickjacking attacks which could cause a user to perform an unintended action in the user interface.
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 confidenceNetApp OnCommand Insight versions 7.3.0 and prior to 7.2.0 are vulnerable to clickjacking attacks. The application can be embedded within an iframe by malicious sites, allowing attackers to overlay invisible or disguised UI elements on top of the legitimate interface to trick authenticated users into performing unintended actions such as clicking buttons or modifying configurations.
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.2.0= 7.3.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
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/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 installed OnCommand Insight versionAccess the OnCommand Insight web interface and navigate to Administration > Settings > Server, or check the installer/backup metadata. Alternatively, query the REST API endpoint /api/1.0/server/version or check the installation logs.Affected if The installed version is 7.3.0 or any version prior to 7.2.0 (versions < 7.2.0 or = 7.3.0 are affected)
-
Verify X-Frame-Options header presenceSend an HTTP GET request to the OnCommand Insight login page or any authenticated endpoint using a tool like curl or browser dev tools. Inspect the response headers for X-Frame-Options.Affected if The X-Frame-Options header is missing, set to ALLOWALL, or not configured at all (header must be DENY or SAMEORIGIN to be protected)
-
Verify CSP frame-ancestors directiveInspect the Content-Security-Policy HTTP header in responses from the OnCommand Insight server. Look for the frame-ancestors directive.Affected if The CSP frame-ancestors directive is missing, not configured, or allows external domains to embed the site in iframes
You are affected if your installed OnCommand Insight version is 7.3.0 or any version prior to 7.2.0 AND the application lacks proper X-Frame-Options (DENY/SAMEORIGIN) or CSP frame-ancestors protections, allowing it to be embedded in iframes by malicious sites.
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.2.0
Implement X-Frame-Options header (DENY or SAMEORIGIN) or Content Security Policy (CSP) frame-ancestors directive at the web server, load balancer, or application level to prevent the application from being embedded in iframes.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.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,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-13652 — 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-2017-13652 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