dbcve.org
Endpoint Protection ManagerApplication · Symantec

CVE-2016-3651

HIGH · 8.0 CVSS v3.0 Published 2016-06-30
Fix available
A fix is available. Upgrade to after 12.1.6 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable

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
Symantec Endpoint Protection Manager (SEPM) 12.1 before RU6 MP5 allows remote authenticated users to discover the PHP JSESSIONID value 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

This vulnerability in Symantec Endpoint Protection Manager 12.1 before RU6 MP5 allows remote authenticated users to discover the PHP JSESSIONID session identifier through unspecified vectors. Exposure of this session cookie could enable attackers to perform session hijacking and impersonate legitimate authenticated users.

MitigationUpgrade to Symantec Endpoint Protection Manager 12.1 RU6 MP5 or later. Additionally, implement session security controls such as regenerating session IDs upon authentication, setting HttpOnly and Secure flags on session cookies, and monitoring for suspicious session activity.

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
Endpoint Protection ManagerApplication
Affected:<= 12.1.6

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:L/UI:R/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 Endpoint Protection Manager version
    Locate the installed version of Symantec Endpoint Protection Manager on the system. This can be done through Add/Remove Programs, the product's About dialog in the management console, or by checking installation directories for version information.
    Affected if The installed version is 12.1.6 or lower (any version before RU6 MP5)
  2. Confirm management console accessibility
    Verify that the Symantec Endpoint Protection Manager web console is accessible. This vulnerability involves session identifier exposure through the web management interface.
    Affected if The management console is running and accessible to authenticated users

If the installed version is 12.1.6 or lower and the management console is accessible, the environment is affected by this session identifier exposure vulnerability.

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 12.1.6
Interim mitigation

Upgrade to Symantec Endpoint Protection Manager 12.1 RU6 MP5 or later. Additionally, implement session security controls such as regenerating session IDs upon authentication, setting HttpOnly and Secure flags on session cookies, and monitoring for suspicious session activity.

Fix this in Endpoint Protection Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,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 $5,248.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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