LiveActive security incident?Get immediate response
CVE Record

CVE-2011-0688: Intel Alert Management System (aka AMS or AMS2), as used in Symantec Antivirus Corporate Edition (SAVCE) 10...

Intel Alert Management System (aka AMS or AMS2), as used in Symantec Antivirus Corporate Edition (SAVCE) 10.x before 10.1 MR10, Symantec System Center (SSC) 10.x, and Symantec Quarantine Server 3.5 and 3.6, allows remote attackers to execute arbitrary commands via crafted messages over TCP, as discovered by Junaid Bohio, a different vulnerability than CVE-2010-0110 and CVE-2010-0111. NOTE: some of these details are obtained from third party information.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

This is a legacy remote command execution flaw in Intel Alert Management System components used by older Symantec antivirus management products. If an exposed, unpatched server receives crafted TCP messages, an attacker may run arbitrary commands. The main business risk is compromise of aging security-management infrastructure that may still have broad internal trust. Exposure is most likely in legacy on-premises environments still running the named Symantec products or retained quarantine/management servers. Risk increases if AMS-related TCP services are reachable from user networks, partner networks, VPNs, or the internet. Prioritize this where legacy Symantec management infrastructure remains in production. Remote command execution against security tooling can provide a valuable internal foothold, even without confirmed active exploitation in the provided sources. Mitigation focus: Identify hosts running the named Symantec and Intel AMS/AMS2 components.; Apply Symantec guidance, including upgrading SAVCE 10.x before 10.1 MR10 where applicable.; Restrict access to AMS-related TCP services to trusted management networks only..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2011-0688 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.