dbcve.org
Storage ManagerApplication · Solarwinds

CVE-2015-7838

HIGH · 10.0 CVSS v2.0 Published 2015-10-15
Fix available
A fix is available. Upgrade to after 6.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
ProcessFileUpload.jsp in SolarWinds Storage Manager before 6.2 allows remote attackers to upload and execute arbitrary files 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 · high confidence

ProcessFileUpload.jsp in SolarWinds Storage Manager versions before 6.2 contains an unauthenticated arbitrary file upload vulnerability allowing remote attackers to upload and execute arbitrary files, leading to complete remote code execution and full system compromise.

MitigationUpgrade to SolarWinds Storage Manager version 6.2 or later to obtain the patched component, or disable/remove the ProcessFileUpload.jsp endpoint if not required for business operations.

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 data
Storage ManagerApplication
Affected:<= 6.1

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
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 checks

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

  1. Confirm SolarWinds Storage Manager installation
    Locate the SolarWinds Storage Manager application directory on the system. Common paths include C:\Program Files\SolarWinds\Storage Manager or /opt/solarwinds/storage_manager. Check for the presence of the main application executables or service.
    Affected if SolarWinds Storage Manager software is found on the system
  2. Identify installed version
    Locate the version information for the installation. Check the application GUI about screen, the install directory for a version file, or query the running service. Compare the version number to the affected range of <= 6.1.
    Affected if The installed version is 6.1 or earlier, or the version cannot be determined but the product is present
  3. Locate ProcessFileUpload.jsp
    Search for ProcessFileUpload.jsp in the web application's webroot directory. This is typically found in the webapps or www directory of the Storage Manager installation. Use file system search or check the web application structure.
    Affected if ProcessFileUpload.jsp file exists in the application directory
  4. Verify unauthenticated web access
    Check if the Storage Manager web interface is exposed and accessible without authentication. Attempt to access the ProcessFileUpload.jsp endpoint via HTTP/HTTPS from an unauthorized network location. The endpoint path is typically /ProcessFileUpload.jsp or /sm/ProcessFileUpload.jsp.
    Affected if The web interface and ProcessFileUpload.jsp are reachable without credentials

The environment is affected if SolarWinds Storage Manager version 6.1 or earlier is installed and the ProcessFileUpload.jsp endpoint is accessible on the network.

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

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 a release after 6.1
Interim mitigation

Upgrade to SolarWinds Storage Manager version 6.2 or later to obtain the patched component, or disable/remove the ProcessFileUpload.jsp endpoint if not required for business operations.

Recommended fix High confidence

SolarWinds Storage Manager 6.2

  1. Backup all Storage Manager data, configurations, and database
  2. Download SolarWinds Storage Manager version 6.2 or later from the official SolarWinds download portal
  3. Review SolarWinds upgrade documentation for Storage Manager 6.1 to 6.2
  4. Execute the upgrade installer on the Storage Manager server
  5. Verify the ProcessFileUpload.jsp vulnerability is no longer present by reviewing the updated file
  6. Confirm Storage Manager services start successfully after upgrade
  7. Validate that existing storage resources and monitoring data are intact

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

Fix this in Storage Manager Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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