Symantec Critical System ProtectionApplication · Broadcom

CVE-2015-8157

HIGH · 8.8 CVSS v3.1 Published 2016-06-08
Fix available
A fix is available. Upgrade to after 6.6.0 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
SQL injection 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 SQL commands 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

SQL injection vulnerability in the Management Server component of multiple Symantec security products (SES:CSP, SCSP, DCS:SA). The flaw allows remote authenticated users to execute arbitrary SQL commands via unspecified vectors in the application's database queries, likely due to improper input sanitization in SQL query construction.

MitigationApply vendor-supplied patches: SES:CSP 1.0.x to 1.0 MP5, SES:CSP 6.5.0 to MP1, SCSP to 5.2.9 MP6, and DCS:SA 6.x/6.6 to their respective MP1 releases. As a compensating control, restrict Management Server access to minimal required personnel and enforce least-privilege database accounts.

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

CVSS:3.1/AV:N/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 Management Server component installation
    Locate the installed Symantec security product that includes the Management Server component (SES:CSP, SCSP, or DCS:SA). Check installed programs or services list for these product names.
    Affected if The Management Server component for any of the listed products is installed.
  2. Determine installed product version
    Use the product's built-in version check (typically via about dialog, command line flag like -version, or checking installed packages) to obtain the exact version number.
    Affected if Version is at or below 5.2.9 for Critical System Protection; equals 6.5.0 or 6.6.0 for Data Center Security Server; at or below 6.6.0 for DCS Server And Agents; at or below 1.0 for Embedded Security CSP; or at or below 6.5.0 for Embedded Security CSP For Controllers.
  3. Confirm Management Server remote access is enabled
    Check the Management Server configuration for remote management or web console access settings. Look for exposed network listeners that accept remote connections.
    Affected if The Management Server web console or API is accessible from network locations beyond localhost.
  4. Verify database query interface availability
    Examine whether the application's database query functionality or reporting features that execute database commands are accessible to authenticated users.
    Affected if Authenticated users can access features that construct and execute database queries through the application.
  5. Review user account privileges
    Check the accounts granted access to the Management Server interface and database interaction capabilities.
    Affected if Any user accounts with Management Server access exist (including low-privilege accounts), as the SQL injection can be exploited by any authenticated user.

If the Management Server component is installed and the version falls within the affected ranges listed, the environment is vulnerable to SQL injection via authenticated database query access.

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-supplied patches: SES:CSP 1.0.x to 1.0 MP5, SES:CSP 6.5.0 to MP1, SCSP to 5.2.9 MP6, and DCS:SA 6.x/6.6 to their respective MP1 releases. As a compensating control, restrict Management Server access to minimal required personnel and enforce least-privilege database accounts.

Fix this in Symantec Critical System Protection Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2015-8157 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