CVE-2015-1484
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 · uneditedUnquoted Windows search path vulnerability in the agent in Symantec Workspace Streaming (SWS) 6.1 before SP8 MP2 HF7 and 7.5 before SP1 HF4, when AppMgrService.exe is configured as a service, allows local users to gain privileges via a Trojan horse executable file in the %SYSTEMDRIVE% directory, as demonstrated by program.exe.
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 confidenceThis is an unquoted Windows service path vulnerability in Symantec Workspace Streaming's AppMgrService.exe. When configured as a Windows service with an unquoted path containing spaces, Windows will search for executables in path segments before the full path is resolved. A local attacker can place a malicious program.exe in the %SYSTEMDRIVE% root directory, which Windows will execute with SYSTEM privileges before locating the legitimate service binary, achieving privilege escalation.
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= 6.1= 7.5CVSS 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
- Local
- Complexity
- M
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:L/AC:M/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.
-
Verify AppMgrService is installedOpen Services (services.msc) or run 'sc query AppMgrService' to check if the Symantec Workspace Streaming service exists on the systemAffected if The service named 'AppMgrService' or similar is present on the system
-
Retrieve the service binary pathRun 'sc qc AppMgrService' to query the service configuration and examine the BINARY_PATH_NAME fieldAffected if The binary path points to AppMgrService.exe and contains spaces without surrounding quotes
-
Identify path segments before the executableParse the binary path from the previous step - if it contains spaces and is unquoted, Windows will interpret each directory segment as a potential executable locationAffected if The path is unquoted (no quotation marks around the full path) and contains one or more spaces
-
Check for writable directories in PATH preceding service locationReview the system PATH environment variable and verify if any directory listed before the service's parent directory is writable by standard usersAffected if A writable directory exists in the system PATH that appears before the directory containing AppMgrService.exe, allowing an attacker to place a malicious executable there
Your system is affected if the AppMgrService Windows service is installed with an unquoted binary path containing spaces and writable directories exist in the PATH before the service binary location.
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 patch to upgrade to SWS 6.1 SP8 MP2 HF7 or 7.5 SP1 HF4 or later. Alternatively, modify the service configuration to use quoted paths in the Windows service definition, and remove any writable directories from the system PATH that precede the service binary location.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-1484 — 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-1484 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