dbcve.org
Symantec Critical System ProtectionApplication · Broadcom

CVE-2014-3440

HIGH · 9.0 CVSS v2.0 Published 2015-01-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
96/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
The Agent Control Interface in the management server in Symantec Critical System Protection (SCSP) 5.2.9 before MP6 and Symantec Data Center Security: Server Advanced (SDCS:SA) 6.0.x before 6.0 MP1 allows remote authenticated users to execute arbitrary commands by leveraging client-system access to upload a log file.

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

The Agent Control Interface in the management server of Symantec Critical System Protection (SCSP) 5.2.9 before MP6 and Symantec Data Center Security: Server Advanced (SDCS:SA) 6.0.x before 6.0 MP1 contains a vulnerability allowing remote authenticated users to execute arbitrary commands through client-system access by uploading a malicious log file.

MitigationApply vendor patches: upgrade SCSP to version 5.2.9 MP6 or later, and SDCS:SA to version 6.0 MP1 or later. Restrict access to the Agent Control Interface to only trusted authenticated administrators.

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
Data Center SecurityApplication
Affected:= 6.0.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
Authentication
Single
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:S/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed product and version
    Determine whether Symantec Critical System Protection (SCSP) or Symantec Data Center Security: Server Advanced (SDCS:SA) is installed, and note the exact version number
    Affected if The installed version is SCSP 5.2.9 or SDCS:SA 6.0.0 (or any 6.0.x version before MP1)
  2. Check patch level for SCSP
    If SCSP 5.2.9 is installed, verify whether the MP6 patch has been applied
    Affected if SCSP version is 5.2.9 without MP6 applied
  3. Check patch level for SDCS:SA
    If SDCS:SA 6.0.x is installed, verify whether the MP1 patch has been applied
    Affected if SDCS:SA version is 6.0.x without MP1 applied
  4. Verify Agent Control Interface exposure
    Confirm whether the Agent Control Interface management service is exposed or accessible to network users
    Affected if The Agent Control Interface is enabled and network-accessible to untrusted users
  5. Assess authentication access
    Review which authenticated users have access to the Agent Control Interface functionality for log file upload
    Affected if Non-administrative or untrusted accounts have access to upload log files through the Agent Control Interface

You are affected if you run SCSP 5.2.9 without MP6 or SDCS:SA 6.0.x without MP1, and the Agent Control Interface is accessible to authenticated users who can upload log files.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patches: upgrade SCSP to version 5.2.9 MP6 or later, and SDCS:SA to version 6.0 MP1 or later. Restrict access to the Agent Control Interface to only trusted authenticated administrators.

Recommended fix Moderate confidence

Symantec Critical System Protection 5.2.9 MP6 or Symantec Data Center Security Server Advanced 6.0 MP1

  1. Identify which Symantec product is deployed: Symantec Critical System Protection (SCSP) or Symantec Data Center Security: Server Advanced (SDCS:SA)
  2. For SCSP 5.2.9: Upgrade to SCSP 5.2.9 MP6 (Maintenance Pack 6) to remediate the command injection vulnerability
  3. For SDCS:SA 6.0.x: Upgrade to SDCS:SA 6.0 MP1 to remediate the command injection vulnerability
  4. Verify the upgrade was successful by confirming the management server version reflects the MP level
  5. Test that the Agent Control Interface log file upload functionality works correctly after patching
Caveat Review Symantec release notes for MP6/MP1 for any configuration changes or compatibility considerations before applying

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Symantec Critical System Protection Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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