dbcve.org
Symantec Critical System ProtectionApplication · Broadcom

CVE-2015-8798

HIGH · 8.0 CVSS v3.1 Published 2016-06-08
Fix available
A fix is available. Upgrade to after 6.6.0 or later.
See remediation →
82/100
Remediation priority · High
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
Directory traversal vulnerability in the Management Server in Symantec Embedded Security: Critical System Protection (SES:CSP) 1.0.x before 1.0 MP5, Embedded Security: Critical System Protection for Controllers and Devices (SES:CSP) 6.5.0 before MP1, Critical System Protection (SCSP) before 5.2.9 MP6, Data Center Security: Server Advanced Server (DCS:SA) 6.x before 6.5 MP1 and 6.6 before MP1, and Data Center Security: Server Advanced Server and Agents (DCS:SA) through 6.6 MP1 allows remote authenticated users to execute arbitrary code 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 confidence

Directory traversal vulnerability in the Management Server of multiple Symantec security products (SES:CSP, SCSP, DCS:SA) allows remote authenticated users to execute arbitrary code by manipulating file paths through unspecified vectors.

MitigationApply vendor patches (MP5 for 1.0.x, MP1 for 6.5.0/6.6, 5.2.9 MP6 for SCSP). Until patched, restrict network access to the Management Server to trusted networks and enforce least-privilege for authenticated users.

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
Symantec Critical System ProtectionApplication
Affected:<= 5.2.9
Symantec Data Center Security ServerApplication
Affected:= 6.5.0= 6.6.0
Symantec Data Center Security Server And AgentsApplication
Affected:<= 6.6.0
Symantec Embedded Security Critical System ProtectionOperating system
Affected:<= 1.0
Symantec Embedded Security Critical System Protection For Controllers And DevicesOperating system
Affected:<= 6.5.0

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
Adjacent
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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. Identify installed Symantec security product
    Inspect the system for installed software matching the affected product names: Symantec Critical System Protection, Symantec Data Center Security Server, or Symantec Embedded Security Critical System Protection. Check program files directories or use system inventory tools to list security software.
    Affected if Any of these products are found installed on the system
  2. Determine product version
    Locate the version information for the installed product. Common methods include: checking the software's About/Help dialog, reviewing version info in installation directories, or querying the Windows registry under HKLM\Software\Symantec\ or similar keys.
    Affected if The installed version falls within the affected ranges: <= 5.2.9 for SCSP, = 6.5.0 or = 6.6.0 or <= 6.6.0 for DCS, <= 1.0 for Embedded Security CSP, or <= 6.5.0 for Embedded Security CSP for Controllers
  3. Verify Management Server component is active
    Check if the Management Server service is running. On Windows, use Services.msc or run 'sc query' for services named 'Symantec Management Server', 'SCSP Management Server', or similar. On Linux, check for processes like 'sescs' or 'scsp-server'.
    Affected if The Management Server service is running and the product version is within affected ranges
  4. Confirm authenticated user access scope
    Review the system's authentication configuration and user access controls for the Management Server interface. Check if the Management Server web console or API is accessible and accepts authenticated sessions.
    Affected if The Management Server accepts authenticated connections and the product version is vulnerable

The environment is affected if any of the listed Symantec products are installed with a version within the specified ranges and the Management Server component is active and accessible to authenticated users.

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.

From vendor data
Upgrade available Upgrade to a release after 6.6.0
Interim mitigation

Apply vendor patches (MP5 for 1.0.x, MP1 for 6.5.0/6.6, 5.2.9 MP6 for SCSP). Until patched, restrict network access to the Management Server to trusted networks and enforce least-privilege for authenticated users.

Fix this in Symantec Critical System Protection Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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