CVE-2017-14053
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 Unified Manager for Clustered Data ONTAP before 7.2P1 does not set the secure flag for an unspecified cookie in an HTTPS session, which makes it easier for remote attackers to capture this cookie by intercepting its transmission within an HTTP session.
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 confidenceThe vulnerability is a missing Secure flag on cookies in NetApp OnCommand Unified Manager for Clustered Data ONTAP. When a user accesses the application over HTTPS, affected cookies are still transmitted in a manner that allows interception if any HTTP traffic occurs or if there's an HTTP-to-HTTPS transition. Attackers can capture these cookies by intercepting network traffic and use them for session hijacking.
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.2CVSS 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 Unified Manager versionLog into the OnCommand Unified Manager web interface and navigate to the Help > About page, or run 'ucmadmin -v' from the command line if you have shell access to the server.Affected if The installed version is 7.2 or earlier (any version <= 7.2).
-
Capture HTTPS session cookiesUse a web browser's developer tools (F12), a proxy tool like Burp Suite, or tcpdump to capture HTTP traffic when authenticating to the OnCommand Unified Manager web interface over HTTPS. Inspect the Set-Cookie headers in the response.Affected if Set-Cookie headers are present for session or authentication cookies without the 'Secure' attribute.
-
Inspect cookie attributes in browserAfter logging into OnCommand Unified Manager over HTTPS, open the browser's developer tools, go to the Application or Storage tab, and examine the cookies for the domain. Look for the Secure flag column or inspect the cookie details.Affected if Sensitive cookies (such as session IDs, auth tokens, or JSESSIONID) do not have the Secure flag enabled.
-
Verify HTTP-to-HTTPS transition behaviorWhile capturing traffic, observe if any HTTP requests occur or if the application performs any redirects from HTTP to HTTPS. Check if cookies are transmitted during any such transitions.Affected if The application transmits cookies over HTTP or allows cookie transmission during HTTP-to-HTTPS transitions.
You are affected if your OnCommand Unified Manager version is 7.2 or earlier and sensitive cookies lack the Secure flag when the application is accessed over HTTPS, allowing potential cookie interception.
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 dataSet the Secure flag on all sensitive cookies in the application configuration or code to ensure they are only transmitted over encrypted HTTPS connections. Upgrading to version 7.2P1 or later also addresses this vulnerability.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-14053 — 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-14053 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