CVE-2016-4350

Home/CVE/Multiple SQL injection vulnerabilities in the Web Services web server in SolarWinds Storage Resource Monitor (SRM) Profi

CVE

Multiple SQL injection vulnerabilities in the Web Services web server in SolarWinds Storage Resource Monitor (SRM) Profi

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.

CRITICAL · CVSS 9.8 EPSS 0.63498

Act now

EPSS ≥ 0.50 - high probability of exploitation in the next 30 days
EPSS percentile: top 2% of all CVEs by exploitation likelihood
Public exploit or PoC is available
CVSS base score ≥ 7.0

Sigma rules0 YARA rules0

Look this up elsewhere - one-click external pivots

NVD CVE.org CISA Vulners Exploit-DB GitHub PoC VulnCheck KEV GreyNoise

▸ How to read a CVE - triage first, then detect and patch

This page is every public fact about CVE-2016-4350, cross-linked. Its job is to answer one question fast - does this need my attention now? - and then hand you the two things you do about it. Here is how an analyst reads it.

Triage: should I act now? Four signals, and they are not interchangeable:

CVSSseverity - how bad it is IF exploited, 0-10. A high CVSS alone is not urgency; a flaw can be a perfect 10 and never actually be attacked. EPSSprobability - a model’s estimate of the chance it is exploited in the next 30 days, 0-1. This is the “will it actually happen” signal. CISA KEVconfirmed - it is being exploited in the wild right now. The strongest signal on the page; KEV beats any score. Weaponisedavailability - public exploits / PoCs, and especially Metasploit modules rated Excellent / Great. Reliable, packaged exploit code means low-skill attackers can use it today.

How they combine: KEV, or a dependable Metasploit module, means patch now regardless of CVSS. High CVSS + low EPSS + no exploit is real but not an emergency - schedule it. Low CVSS but KEV-listed still gets patched now. The verdict above already weighed these for you; this is how it got there.

Then what - two workflows:

Detectwhen you cannot patch today, follow this CVE to the ATT&CK techniques it enables, then Build a SIEM detection (the green button) - author a rule, test it in Atomic, deploy it. That buys visibility while the patch waits. PatchAffected products / packages tell you if you are exposed; Fixed versions by distribution and Vendor advisories give the exact version that closes it.

Reading order for the panels below: verdict + badges, then Public exploits / Metasploit (is it weaponised), then ATT&CK techniques + Sigma / IDS rules (can I detect it), then Affected products / packages + Fixed versions (am I exposed, what patches it), then Threat actors / IOCs (who uses it), then Scoring & timeline / references (the evidence).

View attack path from CVE-2016-4350

◆

ATT&CK techniques

Techniques this CVE enables - linked via CWECAPECATT&CK. High◆ = named directly in ATT&CK or Nuclei templates.

T1190 · Exploit Public-Facing Application

▤ Build a SIEM detection for these techniques

▤

CAPEC attack patterns

Attack patterns this CVE enables - the bridge from weakness to ATT&CK technique.

CAPEC-CAPEC-108 · Command Line Execution through SQL Injection CAPEC-CAPEC-109 · Object Relational Mapping Injection CAPEC-CAPEC-110 · SQL Injection through SOAP Parameter Tampering CAPEC-CAPEC-470 · Expanding Control over the Operating System from the Database CAPEC-CAPEC-66 · SQL Injection CAPEC-CAPEC-7 · Blind SQL Injection

⬡

Weakness Classification

CWE-89Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

▤

Affected Products & Versions

solarwinds storage resource monitor<= 6.2.1

⚠

Public Exploits & PoCs

These PoC and exploit links come from public sources and are not verified to be safe or functional. Review the code before running anything, and treat unverified entries as untrusted.

pocARPSyndicate/cve-scores (trickest)

▣