dbcve.org
Endpoint ProtectionApplication · Symantec

CVE-2012-4348

HIGH · 7.2 CVSS v2.0 Published 2012-12-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
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 management console in Symantec Endpoint Protection (SEP) 11.0 before RU7-MP3 and 12.1 before RU2, and Symantec Endpoint Protection Small Business Edition 12.x before 12.1 RU2, does not properly validate input for PHP scripts, which allows remote authenticated users to execute arbitrary code 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 confidence

The management console in Symantec Endpoint Protection versions 11.0 before RU7-MP3 and 12.1 before RU2 contains PHP scripts that do not properly validate input, allowing remote authenticated attackers to execute arbitrary code on the affected system.

MitigationApply the vendor-supplied patches (SEP 11.0 RU7-MP3, 12.1 RU2, or SBE 12.1 RU2 or later) after testing in a non-production environment to ensure compatibility with existing endpoint configurations and enterprise software.

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:= 11.0= 11.0.1= 11.0.2= 11.0.4= 11.0.3001= 11.0.6000= 11.0.6100= 11.0.6200= 11.0.6200.754= 11.0.6300= 11.0.7000= 11.0.7100

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
Adjacent
Complexity
Low
Authentication
Multiple
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:A/AC:L/Au:M/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. Confirm Symantec Endpoint Protection is installed
    Check the system for SEP installation by looking for the management console directory (typically C:\Program Files\Symantec\Symantec Endpoint Protection\ or /opt/Symantec/symantec_audit/ on Linux) and verify the presence of the 'manager' or 'console' folder containing PHP scripts.
    Affected if SEP is installed and the management console PHP scripts are present on the system
  2. Identify the installed SEP version
    On Windows, open the management console and go to Help > About Symantec Endpoint Protection, or check the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\Symantec Endpoint Protection\CurrentVersion\ProductVersion. On Linux, run 'rpm -q symantec-endpoint-protection' or check /opt/Symantec/symantec_audit/version.info.
    Affected if The installed version is 11.0.x through 11.0.7100, or any 12.1 version before RU2
  3. Verify the management console is accessible
    Confirm the SEP management console web interface is reachable by accessing it via browser (typically https://localhost:8447 or the configured management server address). Check if the console responds and PHP scripts are executable.
    Affected if The management console is accessible via HTTP/HTTPS and PHP scripts are enabled
  4. Check if remote management is enabled
    Examine the SEPM configuration: on Windows check the SEPM installation directory for 'conf' files, or review the management server settings to determine if remote administrative access is permitted. Look for settings controlling remote console access.
    Affected if Remote management/administrative console access is enabled and exposed to network access
  5. Compare version against affected range
    Cross-reference the identified version number against the affected versions: 11.0 through 11.0.7100 (all builds listed), or any unpatched 12.1 version. The fixed versions are 11.0 RU7-MP3, 12.1 RU2, or later.
    Affected if The installed version falls within 11.0.x through 11.0.7100, or is 12.1 before RU2, and the management console is accessible

A system is affected if it runs Symantec Endpoint Protection version 11.0.x through 11.0.7100 or 12.1 before RU2, has the management console with PHP scripts enabled and accessible, and remote administrative access is permitted.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor-supplied patches (SEP 11.0 RU7-MP3, 12.1 RU2, or SBE 12.1 RU2 or later) after testing in a non-production environment to ensure compatibility with existing endpoint configurations and enterprise software.

Fix this in Endpoint Protection Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,580
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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