dbcve.org
Endpoint ProtectionApplication · Symantec

CVE-2012-0295

HIGH · 9.3 CVSS v2.0 Published 2012-05-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 Manager service in the management console in Symantec Endpoint Protection (SEP) 12.1 before 12.1 RU1-MP1 allows remote attackers to conduct file-insertion attacks and execute arbitrary code by leveraging exploitation of CVE-2012-0294.

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 Manager service in the Symantec Endpoint Protection management console versions 12.1 before RU1-MP1 contains a vulnerability allowing remote attackers to conduct file-insertion attacks and achieve arbitrary code execution. The CVSS 9.3 score reflects a critical network-exploitable RCE that requires chaining with CVE-2012-0294 for successful exploitation.

MitigationUpgrade to Symantec Endpoint Protection 12.1 RU1-MP1 or later to remediate. Given the requirement to chain with CVE-2012-0294, ensure both vulnerabilities are addressed through the vendor patch.

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 ProtectionApplication
Affected:= 12.1= 12.1.671= 12.1.1000

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
M
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:M/Au:N/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 Symantec Endpoint Protection version
    Locate the SEP version through the client UI (Help > About), Windows Programs and Features, or registry key under HKLM\Software\Symantec\Symantec Endpoint Protection\CurrentVersion
    Affected if The installed version is 12.1, 12.1.671, or 12.1.1000 (or any version below RU1-MP1 within the 12.1 branch)
  2. Determine if Manager service is exposed
    Check whether the Symantec Endpoint Protection Manager (SEPM) web console is accessible on the network. By default this runs on ports 80, 443, or 8443. Verify if the service is listening on external interfaces versus localhost only.
    Affected if The Manager service management console is reachable over the network (especially from untrusted segments)
  3. Verify management console accessibility
    Attempt to access the SEPM login page via browser at https://<server>:8443/ or http://<server>:80/ to confirm the service is running and exposed
    Affected if The management console login page responds, indicating the vulnerable service is active
  4. Confirm patch status
    Check if the installed build is below RU1-MP1. The fixed version is 12.1 RU1-MP1 (build 12.1.4013.4013 or higher). Compare your installed build number against this threshold.
    Affected if The installed version is any build prior to 12.1 RU1-MP1

You are affected if Symantec Endpoint Protection Manager version 12.1 (any of the listed builds) is running and exposed, and the installation is below RU1-MP1 patch level.

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

Upgrade to Symantec Endpoint Protection 12.1 RU1-MP1 or later to remediate. Given the requirement to chain with CVE-2012-0294, ensure both vulnerabilities are addressed through the vendor patch.

Recommended fix High confidence

12.1 RU1-MP1 (Release Update 1 Maintenance Pack 1) or later

  1. Verify current Symantec Endpoint Protection Manager version by checking About in the management console
  2. Download Symantec Endpoint Protection 12.1 RU1-MP1 or later from the Broadcom/Symantec support portal
  3. Review the upgrade guide and release notes for SEP 12.1 RU1-MP1
  4. Create a backup of the current management server database
  5. Stop all Symantec Endpoint Protection services before upgrade
  6. Run the upgrade installer for 12.1 RU1-MP1 on the management server
  7. Follow the installation wizard prompts to complete the upgrade
  8. Restart Symantec Endpoint Protection services after upgrade completes
Caveat Within same major version (12.1.x) minimal breaking changes expected, but review release notes for configuration or feature changes

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

Fix this in Endpoint 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-2012-0295 — 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-2012-0295 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