CVE-2015-6555
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 · uneditedSymantec Endpoint Protection Manager (SEPM) 12.1 before 12.1-RU6-MP3 allows remote attackers to execute arbitrary Java code by connecting to the console Java port.
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 confidenceSymantec Endpoint Protection Manager (SEPM) versions 12.1 prior to 12.1-RU6-MP3 contain a vulnerability in the console Java port that allows unauthenticated remote attackers to execute arbitrary Java code by directly connecting to this port. This is a critical remote code execution (RCE) vulnerability requiring no authentication.
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<= 12.1CVSS 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
- M
- Authentication
- Single
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:M/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 checksWork through these to decide whether this CVE applies to you.
-
Verify Symantec Endpoint Protection Manager is installedCheck the Windows installed programs list or look for SEPM installation directories (typically under C:\Program Files\Symantec\Symantec Endpoint Protection Manager)Affected if SEPM is present on the system
-
Determine the SEPM versionCheck the version information in the SEPM management console or in the Windows installed programs list - look for the full version string including any RU (Release Update) and MP (Maintenance Pack) designationsAffected if The installed version is 12.1 or earlier, or is 12.1-RU6-MP2 or earlier (any version prior to 12.1-RU6-MP3)
-
Identify the console Java portExamine SEPM configuration files (such as conf.properties or similar configuration in the SEPM installation directory) or check SEPM console settings to identify which port the Java-based management console is listening onAffected if The console Java port is configured and listening (typically SEPM uses an HTTPS console port in the 8000-9000 range)
-
Verify network accessibility of the console Java portUse netstat or a network port scanner to confirm the console Java port is bound to a network interface and accessible from external systems, not just localhostAffected if The console Java port is listening on an external network interface and is reachable from untrusted networks
A system is affected if Symantec Endpoint Protection Manager version 12.1-RU6-MP3 or later is NOT installed AND the console Java port is network-accessible.
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 dataPrimary remediation is to upgrade SEPM to version 12.1-RU6-MP3 or later. As a compensating control, network access to the console Java port should be restricted via firewall to trusted management networks only until the upgrade is applied.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-6555 — 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-6555 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