CVE-2019-5491
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 · uneditedClustered Data ONTAP versions prior to 9.1P15 and 9.3 prior to 9.3P7 are susceptible to a vulnerability which discloses sensitive information to an unauthenticated user.
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 confidenceClustered Data ONTAP versions prior to 9.1P15 and 9.3 prior to 9.3P7 contain an information disclosure vulnerability that allows unauthenticated attackers to gain access to sensitive system information without requiring valid credentials.
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>= 9.0, < 9.1= 9.1= 9.3CVSS 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.
-
Confirm Clustered Data ONTAP is installedRun the command 'system node show' or 'version' in the ONTAP CLI to identify the system and verify it is a Clustered Data ONTAP storage system.Affected if The system is running Clustered Data ONTAP and responds to ONTAP CLI commands.
-
Retrieve the ONTAP versionExecute the 'version' command in the ONTAP CLI or run 'system node show -fields version' to obtain the exact installed version number.Affected if The command returns a version number.
-
Compare version against affected rangesCheck if the installed version falls within: 9.0.x, any 9.1 version prior to 9.1P15, or any 9.3 version prior to 9.3P7. These versions contain the vulnerability.Affected if The installed version is 9.0.x, 9.1.x prior to 9.1P15, or 9.3.x prior to 9.3P7.
-
Verify the system is network-accessibleConfirm that the ONTAP management interface or API endpoints are reachable from network locations, as the vulnerability allows unauthenticated attackers to access sensitive system information remotely.Affected if The ONTAP management LIF or API is exposed to untrusted networks without proper access controls.
A system is affected if it runs Clustered Data ONTAP version 9.0.x, 9.1.x before 9.1P15, or 9.3.x before 9.3P7 and has its management interface network-accessible.
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 data9.1
Upgrade Clustered Data ONTAP to version 9.1P15 or later, or 9.3P7 or later, to resolve the vulnerability.
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-5491 — 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-5491 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