CVE-2015-8157
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 · uneditedSQL 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 confidenceSQL 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.
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<= 5.2.9= 6.5.0= 6.6.0<= 6.6.0<= 1.0<= 6.5.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Management Server component installationLocate 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.
-
Determine installed product versionUse 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.
-
Confirm Management Server remote access is enabledCheck 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.
-
Verify database query interface availabilityExamine 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.
-
Review user account privilegesCheck 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.
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 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.
- Consultation6.0 h
- Implementation12.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 $8,448.
Scan for this in your stack
Free · runs locallyCheck 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2015-8157 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