Storage Resource MonitorApplication · Solarwinds

CVE-2016-4350

CRITICAL · 9.8 CVSS v3.0 Published 2016-05-09

Fix available

A fix is available. Upgrade to after 6.2.1 or later.

See remediation →

100/100

Remediation priority · Urgent

High EPSS Remotely reachable No privileges Zero-click

Official description

NVD · unedited

Multiple SQL injection vulnerabilities in the Web Services web server in SolarWinds Storage Resource Monitor (SRM) Profiler (formerly Storage Manager (STM)) before 6.2.3 allow remote attackers to execute arbitrary SQL commands via the (1) ScriptSchedule parameter in the ScriptServlet servlet; the (2) winEventId or (3) winEventLog parameter in the WindowsEventLogsServlet servlet; the (4) processOS parameter in the ProcessesServlet servlet; the (5) group, (6) groupName, or (7) clientName parameter in the BackupExceptionsServlet servlet; the (8) valDB or (9) valFS parameter in the BackupAssociationServlet servlet; the (10) orderBy or (11) orderDir parameter in the HostStorageServlet servlet; the (12) fileName, (13) sortField, or (14) sortDirection parameter in the DuplicateFilesServlet servlet; the (15) orderFld or (16) orderDir parameter in the QuantumMonitorServlet servlet; the (17) exitCode parameter in the NbuErrorMessageServlet servlet; the (18) udfName, (19) displayName, (20) udfDescription, (21) udfDataValue, (22) udfSectionName, or (23) udfId parameter in the UserDefinedFieldConfigServlet servlet; the (24) sortField or (25) sortDirection parameter in the XiotechMonitorServlet servlet; the (26) sortField or (27) sortDirection parameter in the BexDriveUsageSummaryServlet servlet; the (28) state parameter in the ScriptServlet servlet; the (29) assignedNames parameter in the FileActionAssignmentServlet servlet; the (30) winEventSource parameter in the WindowsEventLogsServlet servlet; or the (31) name, (32) ipOne, (33) ipTwo, or (34) ipThree parameter in the XiotechMonitorServlet servlet.

Technical summary

dbcve analysis · high confidence

Critical SQL injection vulnerabilities exist in SolarWinds Storage Resource Monitor (SRM) Profiler web server before version 6.2.3. Remote unauthenticated attackers can execute arbitrary SQL commands through 31 different parameters across 13 servlets including ScriptServlet, WindowsEventLogsServlet, ProcessesServlet, BackupExceptionsServlet, and others, due to insufficient input validation on user-supplied parameters.

MitigationImmediately upgrade to SRM Profiler version 6.2.3 or later. If patching is not immediately feasible, disable the affected web services or implement web application firewall (WAF) rules to block SQL injection attempts in the identified parameters.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

Storage Resource MonitorApplication

Affected:<= 6.2.1

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Privileges: None
User interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: High

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

Am I affected?

dbcve checks

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

Identify SolarWinds SRM installation

Check for SolarWinds Storage Resource Monitor installation on the system - look in Program Files for SolarWinds folders, check services for 'SolarWinds Storage Resource Monitor' or 'SRM' services, or check the Windows registry under HKLM\SOFTWARE\SolarWinds\StorageResourceMonitor

Affected if SolarWinds SRM is installed on the system
Determine installed SRM version

Open the SRM Profiler web interface and check the About page, or check the version in Add/Remove Programs, or examine the SRM installation directory for a version file

Affected if The installed version is 6.2.1 or earlier (6.2.0, 6.1.x, etc.)
Confirm web server component is enabled

Access the SRM Profiler web interface via browser at the configured port (default 8080 or 443) - try accessing http://hostname:8080 or https://hostname:8443

Affected if The web interface responds and is accessible on the network
Verify affected servlets exist

Attempt to access or probe known affected servlet paths such as /ScriptServlet, /WindowsEventLogsServlet, /ProcessesServlet, /BackupExceptionsServlet on the SRM web server

Affected if Any of these servlets return a response (indicating they are enabled and reachable)

The environment is affected if SolarWinds Storage Resource Monitor is installed with version 6.2.1 or earlier and the SRM Profiler web server component is enabled and accessible.

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

Remediation

dbcve · scoped

Upgrade available Upgrade to a release after 6.2.1

Interim mitigation

Immediately upgrade to SRM Profiler version 6.2.3 or later. If patching is not immediately feasible, disable the affected web services or implement web application firewall (WAF) rules to block SQL injection attempts in the identified parameters.

Recommended fix High confidence

Storage Resource Monitor 6.2.3 or later

Verify the current version of SolarWinds Storage Resource Monitor (SRM) by accessing the web interface or checking the installed software
If the installed version is 6.2.1 or earlier, plan for an upgrade to version 6.2.3 or later
Download Storage Resource Monitor version 6.2.3 or the latest stable version from the official SolarWinds download portal
Review the SolarWinds upgrade documentation and release notes for SRM 6.2.3
Create a full backup of the SRM database and configuration before proceeding with the upgrade
Stop the Storage Resource Monitor services on the server
Install the upgrade following the standard SolarWinds upgrade procedure
After installation, verify the new version is 6.2.3 or later

Caveat Review release notes for any changes to features, configuration requirements, or compatibility updates before upgrading

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

Fix this in Storage Resource Monitor Scoped from the published advisory

Consultation3.0 h
Implementation12.0 h
Testing6.0 h
Review / QA3.0 h

24.0 hours of engineering $4,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 $6,720.

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

Practitioner notes

Contributed

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

Notes0 Guidelines

Know something about CVE-2016-4350?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

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

At a glance

A fix existsUpgrade to after 6.2.1 or later

Severity 9.8 Critical

Exploit likelihood EPSS, next 30 days 70.2%

Affects: Storage Resource Monitor

Remediation

A high-priority fix

Fix this in Storage Resource Monitor 24 hrs · Moderate

Typical engagement from $4,200

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2016-4350 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

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

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References