dbcve.org
SnapcenterApplication · Netapp

CVE-2023-1096

CRITICAL · 9.8 CVSS v3.1 Published 2023-05-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
SnapCenter versions 4.7 prior to 4.7P2 and 4.8 prior to 4.8P1 are susceptible to a vulnerability which could allow a remote unauthenticated attacker to gain access as an admin 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 · moderate confidence

This is an authentication bypass vulnerability in NetApp SnapCenter allowing remote unauthenticated attackers to gain admin-level access. The flaw affects versions 4.7 prior to 4.7P2 and 4.8 prior to 4.8P1, likely due to improper authentication logic that can be circumvented without credentials.

MitigationApply the vendor patches (SnapCenter 4.7P2 or 4.8P1) to remediate the vulnerability. Until patched, restrict network exposure of SnapCenter interfaces to trusted networks only.

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
SnapcenterApplication
Affected:= 4.7= 4.8

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 SnapCenter version via web interface
    Log into the SnapCenter web UI and navigate to the About or Settings page to view the installed version number
    Affected if The version displayed is exactly 4.7 or 4.8 (any patch level prior to P2 for 4.7 or P1 for 4.8)
  2. Identify SnapCenter version via PowerShell
    Open SnapCenter PowerShell and run Get-SmVersion or check the installed packages using Get-Package -Name 'NetApp SnapCenter'
    Affected if The returned version matches 4.7.x where x is less than 2, or 4.8.x where x is less than 1
  3. Check Windows services for SnapCenter version
    On the SnapCenter server, open Services console (services.msc) and locate the 'SnapCenter Server' service, then check the executable path or use 'sc query' command
    Affected if The installed binaries correspond to versions 4.7 or 4.8 prior to the patched releases
  4. Verify network exposure of SnapCenter interface
    Check firewall rules or network configuration to determine if the SnapCenter web port (typically 8146 or 8443) is accessible from untrusted networks
    Affected if The SnapCenter UI is exposed to the internet or untrusted internal networks, allowing remote attackers to reach the authentication endpoint

You are affected if your installed SnapCenter version is exactly 4.7 or 4.8 without the P2 or P1 patches respectively, and the web interface is network-accessible.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor patches (SnapCenter 4.7P2 or 4.8P1) to remediate the vulnerability. Until patched, restrict network exposure of SnapCenter interfaces to trusted networks only.

Recommended fix High confidence

SnapCenter 4.8P1 (minimum fixed release)

  1. Download the SnapCenter 4.8P1 (or 4.7P2) software package from the NetApp support site at my.netapp.com
  2. Review the SnapCenter upgrade documentation for prerequisites and compatibility requirements
  3. Stop all SnapCenter services and ensure no active jobs are running
  4. Run the SnapCenter upgrade installer on the server
  5. Follow the on-screen prompts to complete the upgrade
  6. After upgrade, verify the SnapCenter services are running correctly
  7. Confirm the upgraded version by checking Help > About in the SnapCenter GUI

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Snapcenter Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-1096 — 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-2023-1096 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