dbcve.org
Active Iq Unified ManagerApplication · Netapp

CVE-2022-23235

MEDIUM · 5.3 CVSS v3.1 Published 2022-08-25
Fix available
A fix is available. Upgrade to 9.10 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click Patch available

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
Active IQ Unified Manager for VMware vSphere, Linux, and Microsoft Windows versions prior to 9.10P1 are susceptible to a vulnerability which could allow an attacker to discover cluster, node and Active IQ Unified Manager specific information via AutoSupport telemetry data that is sent even when AutoSupport has been disabled.

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

A detailed technical summary for this CVE is being prepared.

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
Active Iq Unified ManagerApplication
Affected:< 9.10= 9.10

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

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

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 9.10 or later
Fixed in 9.10
Vendor patch security.netapp.com →
Recommended fix High confidence

9.10P1 or later

  1. 1. Identify the current installed version of Active IQ Unified Manager by checking the About or version information in the management interface
  2. 2. Download Active IQ Unified Manager version 9.10P1 or later from the NetApp support site (mysupport.netapp.com)
  3. 3. Review the upgrade documentation and release notes for Active IQ Unified Manager 9.10P1
  4. 4. Perform a backup of the current Active IQ Unified Manager configuration and data
  5. 5. Execute the upgrade following the standard upgrade procedure for your platform (VMware vSphere, Linux, or Microsoft Windows)
  6. 6. After upgrade completion, verify the new version is 9.10P1 or later
  7. 7. Confirm AutoSupport telemetry behavior - the vulnerability was that data was sent even when AutoSupport was disabled, so verify the fix is working
Caveat Refer to Active IQ Unified Manager 9.10P1 release notes for any configuration or compatibility changes from prior versions

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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