Skip to main content
NetApp Knowledge Base

Vulnerable undertow version detected in AIQUM 9.13 and 9.14 causing high CPU and acquisition issue

  1. Last updated
  2. Save as PDF
Views:
7,443
Visibility:
Public
Votes:
1
Category:
active-iq-unified-manager
Specialty:
om
Last Updated:

Applies to

Issue

  • AIQUM is vulnerable to : 
  • Which causes the memory and CPU usage to continually increase after being scanned by vulnerability scanners like Qualys/Crowdstrike
    • This can cause Almost out of memory event in Windows system.
      • Source: Resource-Exhaustion-Detector
        Windows successfully diagnosed a low virtual memory condition. 
        The following programs consumed the most virtual memory: mysqld.exe (PID) consumed xxxx bytes, java.exe (PID) consumed xxx bytes, java.exe (PID) consumed xxx bytes.
    • This can cause AIQUM service stop in Windows system.
      • Source: Service Control Manager
        The NetApp Active IQ Management Server Service service entered the stopped state.
    • HTTPS protocol communication from server monitoring system to AIQUM repeatedly goes down and comes back up
  • As a side effect, inventory and performance collections start skipping due to previous collections becoming stuck and still considered running
    • Performance graphs are not shown with Insufficient Historical Data
    • Gaps in the performance graphs
    • This situation occurs intermittently.
  • AIQUM can send scheduled reports but the data in the reports have not been updated since a certain day
  • TCP sessions are not cleared towards the application / server from vulnerability scanners:

Data source is already performing a poll of netappstorageperformance. Therefore this poll is skipped.
-
Failed to obtain reconciliation-processing lock for 0:10:00.000 for datasource

  • ocumserver.log shows error:
    • Timeout occurred while waiting on collection completion listener ClusterSparesEventDetector..EnhancerBySpringCGLIB..abbaf0ec. Cancelling it so that others can continue
    • ERROR [oncommand] [reconciliation-0] [c.n.dfm.collector.OcieJmsListener] Ignoring PACKAGE_CHANGED at updateTime Tue <timestamp>, previous foundation poll at pollStartTime <timestamp> still being processed for ds=x(xxxxxx), adding to the droppedJmsDataSources list
    • ERROR [oncommand] [reconciliation-0] [c.n.dfm.collector.OcieJmsListener] Previous foundation poll at pollStartTime <timestamp> ongoing for ds=x(xxxxxx), adding to the droppedJmsDataSources list

Note: Even in environments where vulnerability scanners are not used, similar access patterns can cause this issue. Therefore, the absence of vulnerability scanners does not mean the environment is unaffected by this issue.

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.