dbcve.org
Clustered Data OntapApplication · Netapp

CVE-2018-5490

HIGH · 8.8 CVSS v3.0 Published 2018-08-03
Fix available
A fix is available. Upgrade to 8.3 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
Read-Only export policy rules are not correctly enforced in Clustered Data ONTAP 8.3 Release Candidate versions and therefore may allow more than "read-only" access from authenticated SMBv2 and SMBv3 clients. This behavior has been resolved in the GA release. Customers running prior release candidates (RCs) are requested to update their systems to the NetApp Data ONTAP 8.3 GA release.

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 confidence

In Clustered Data ONTAP 8.3 Release Candidate versions, read-only export policy rules are incorrectly enforced, allowing authenticated SMBv2 and SMBv3 clients to gain more than read-only access when they should be restricted to read-only. This is a policy enforcement failure in the SMB/CIFS export mechanism.

MitigationUpdate Clustered Data ONTAP 8.3 Release Candidates to the GA release to enforce read-only export policy rules correctly.

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
Clustered Data OntapApplication
Affected:< 8.3

CVSS 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
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the Clustered Data ONTAP version
    Run the command to display the ONTAP version: version or system node show -fields version
    Affected if The installed version is 8.3 Release Candidate or any version prior to 8.3 GA release
  2. Confirm SMB/CIFS protocol is enabled
    Check the SMB server configuration: vserver cifs show
    Affected if SMB/CIFS is enabled on the storage virtual machine (SVM)
  3. Verify export policy rules exist for SMB access
    Inspect export policies applied to SMB shares: vserver export-policy rule show
    Affected if There are export policy rules configured that restrict access to read-only for SMB clients
  4. Check for SMBv2 or SMBv3 client connections
    Review SMB session information: vserver cifs session show
    Affected if SMBv2 or SMBv3 sessions are active and connecting to shares with read-only export policies

A user is affected if they run Clustered Data ONTAP versions prior to 8.3 GA and have SMB export policies configured with read-only rules that are being accessed by SMBv2 or SMBv3 clients.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to 8.3 or later
Fixed in 8.3
Interim mitigation

Update Clustered Data ONTAP 8.3 Release Candidates to the GA release to enforce read-only export policy rules correctly.

Fix this in Clustered Data Ontap Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-5490 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-5490 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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