CVE-2014-3915
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 userRequest servlet in the Admin Center for Tivoli Storage Manager in Rocket Servergraph allows remote attackers to execute arbitrary commands via a (1) auth, (2) auth_session, (3) auth_simple, (4) add, (5) add_flat, (6) remove, (7) set_pwd, (8) add_permissions, (9) revoke_permissions, (10) runAsync, or (11) tsmRequest command.
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 confidenceThe userRequest servlet in the Admin Center for Tivoli Storage Manager (Rocket Servergraph) contains a command injection vulnerability allowing remote attackers to execute arbitrary OS commands through multiple parameters (auth, auth_session, add, runAsync, tsmRequest, etc.). This is a direct execution flaw where user-supplied input is passed to system shell commands without proper sanitization.
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.
-
Identify if Rocket Servergraph is installedCheck for the installation directory (commonly C:\Program Files\Rocket Software\Rocket Servergraph or /opt/rocket/servergraph) and locate the version information in version files or the program's About/Properties dialogAffected if Rocket Servergraph is installed and running
-
Verify the Admin Center web interface is accessibleAttempt to access the Admin Center URL (typically http://hostname:port/admin or https://hostname:port/admin) in a web browser or via curl/wget. Look for the login page or userRequest servlet endpointAffected if The Admin Center web interface responds to requests, indicating the vulnerable servlet is exposed
-
Confirm network accessibility of the Admin CenterUse netstat or ss commands to identify which network interfaces and ports the Admin Center is listening on (common ports include 8080, 8443, or 11080). Check if it binds to 0.0.0.0 or a non-loopback addressAffected if The Admin Center is listening on a routable network interface rather than localhost only
-
Review firewall and access control settingsExamine host-based firewall rules (Windows Firewall, iptables) and any network ACLs to determine if the Admin Center port is exposed to untrusted networks or the internetAffected if The Admin Center port is accessible from networks beyond trusted management subnets
If Rocket Servergraph with an accessible Admin Center is installed and the web interface is network-reachable from untrusted sources, the environment is affected by this command injection vulnerability.
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 dataRestrict network access to the Admin Center to trusted IPs only via firewall or ACLs. If available, apply vendor-supplied patches. Implement input validation and consider web application firewall as compensating control until patch is applied.
- Consultation8.0 h
- Implementation16.0 h
- Testing8.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 $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-3915 — 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-2014-3915 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