CVE-2015-5371
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 · uneditedThe AuthenticationFilter class in SolarWinds Storage Manager allows remote attackers to upload and execute arbitrary scripts via unspecified vectors.
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 confidenceThe AuthenticationFilter class in SolarWinds Storage Manager contains a vulnerability that allows remote, unauthenticated attackers to bypass authentication controls and upload arbitrary script files to the system, which can then be executed to achieve remote code execution with the privileges of the affected service.
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 dataall versionsCVSS 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
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/Au:N/C:C/I:C/A:C
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm SolarWinds Storage Manager installationCheck for the presence of SolarWinds Storage Manager service or installation directory on the system. On Windows, look in Program Files for 'SolarWinds' folder or check Windows Services for 'Storage Manager' service. On Linux, check /opt or common application directories for Storage Manager components.Affected if SolarWinds Storage Manager is installed or running on the system, as all versions are affected by this vulnerability.
-
Identify the AuthenticationFilter configurationLocate the web application configuration files for Storage Manager (typically in the conf or config directory under the installation path). Search for the AuthenticationFilter class definition in web.xml or equivalent configuration files.Affected if The AuthenticationFilter class is present in the Storage Manager configuration, indicating the vulnerable component is enabled.
-
Check for unauthorized script uploadsExamine the web application upload directories within Storage Manager (commonly the 'uploads', 'scripts', or web root directories). Look for unexpected files with extensions such as .jsp, .asp, .php, .exe, or other executable file types.Affected if Unexpected script or executable files exist in Storage Manager upload directories, suggesting successful exploitation.
-
Review web server access logsAnalyze Storage Manager access and audit logs for requests to upload endpoints without proper authentication headers, or requests that bypass the AuthenticationFilter. Look for HTTP POST requests to upload functionality from unfamiliar IP addresses.Affected if Log entries show unauthenticated upload attempts or requests that successfully bypassed authentication to reach upload functionality.
-
Assess network exposure of the management interfaceDetermine if the Storage Manager web interface is accessible from untrusted networks by reviewing firewall rules, network ACLs, and listening services. Check if port 9000 or the configured Storage Manager port is exposed to the internet or untrusted VLANs.Affected if The Storage Manager management interface is accessible from untrusted networks, enabling remote attackers to reach the vulnerable AuthenticationFilter.
If SolarWinds Storage Manager is installed and its management interface is network-accessible (especially from untrusted networks), the environment is affected by this vulnerability and may show signs of unauthorized script uploads in the application directories.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataApply the vendor-provided security patch for SolarWinds Storage Manager immediately. Until patched, restrict network exposure of the Storage Manager interface to trusted networks only and monitor for unauthorized script uploads.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-5371 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2015-5371 in production — separate from our analysis above.
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.
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.
- 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