dbcve.org
SnapcenterApplication · Netapp

CVE-2024-21987

MEDIUM · 5.4 CVSS v3.1 Published 2024-02-16
Fix available
A fix is available. Upgrade to 5.0 or later.
See remediation →
60/100
Remediation priority · Elevated
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
SnapCenter versions 4.8 prior to 5.0 are susceptible to a vulnerability which could allow an authenticated SnapCenter Server user to modify system logging configuration settings

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 vulnerability in SnapCenter versions 4.8 prior to 5.0 allows any authenticated SnapCenter Server user to modify system logging configuration settings. An attacker with valid credentials could exploit this to tamper with or disable logging, potentially covering tracks of malicious activities or undermining forensic investigations.

MitigationUpgrade SnapCenter to version 5.0 or later to obtain the patch. Until then, limit SnapCenter user accounts to only trusted personnel and monitor for unauthorized changes to logging configuration.

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.8, < 5.0

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
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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 checks

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

  1. Verify SnapCenter installation
    Check if SnapCenter is installed on the system. Look for the SnapCenter service in Windows Services, or check for installation directory at C:\Program Files\NetApp\SnapCenter (default path on Windows).
    Affected if SnapCenter is installed on this host.
  2. Determine installed SnapCenter version
    Open SnapCenter UI and navigate to About page, or check the Windows registry at HKEY_LOCAL_MACHINE\SOFTWARE\NetApp\SnapCenter\Version, or inspect the file at C:\Program Files\NetApp\SnapCenter\VERSION file if present.
    Affected if Installed version is 4.8.x or any version >= 4.8 but < 5.0.
  3. Identify logging configuration location
    Locate the logging configuration file. In SnapCenter, logging settings are typically stored in configuration files within the SnapCenter installation directory or in the Windows application data folder (C:\ProgramData\NetApp\SnapCenter\Config).
    Affected if SnapCenter is installed and the configuration files exist.
  4. Inspect current logging configuration settings
    Open the logging configuration files (commonly named logging.config, log4j.config, or similar XML/JSON configuration files in the config directory). Review the log level settings, log file paths, and whether logging has been disabled or redirected.
    Affected if Logging has been disabled, log levels set to OFF, or log paths modified to unusual locations.
  5. Check for recent unauthorized modifications to logging config
    Review file system audit logs or Windows Event Logs (Security event 4663 for file access, or look for Event ID 4656 on the config files) for recent changes to logging configuration files. Compare current settings against a known baseline if available.
    Affected if Logging configuration files were modified by unexpected users or at unusual times, or modifications resulted in reduced logging capability.

You are affected if SnapCenter version 4.8 or higher but below 5.0 is installed, and either the logging configuration has been tampered with or any untrusted users have access to SnapCenter accounts.

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

Upgrade SnapCenter to version 5.0 or later to obtain the patch. Until then, limit SnapCenter user accounts to only trusted personnel and monitor for unauthorized changes to logging configuration.

Recommended fix Moderate confidence

SnapCenter 5.0 or later

  1. 1. Review NetApp SnapCenter 5.0 release notes and upgrade documentation at security.netapp.com for pre-upgrade requirements
  2. 2. Create a complete backup of the existing SnapCenter server configuration and database
  3. 3. Ensure all running backup, clone, and restore jobs are completed or cancelled before upgrade
  4. 4. Stop all SnapCenter services in the correct order as documented
  5. 5. Download SnapCenter 5.0 or later from the NetApp support site
  6. 6. Run the installer with appropriate permissions and follow the upgrade wizard
  7. 7. Verify all SnapCenter services start successfully after upgrade
  8. 8. Validate that SnapCenter functionality works correctly including backups, clones, and restores
Caveat Review NetApp documentation for any configuration or feature changes between 4.x and 5.0 that may impact existing workflows or integrations

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

Fix this in Snapcenter Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
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,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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