CVE-2010-3497: n/a vulnerability

CVE-2010-3497: Symantec Norton AntiVirus 2011 does not properly interact with the processing of hcp:// URLs by the Microso...

Symantec Norton AntiVirus 2011 does not properly interact with the processing of hcp:// URLs by the Microsoft Help and Support Center, which makes it easier for remote attackers to execute arbitrary code via malware that is correctly detected by this product, but with a detection approach that occurs too late to stop the code execution. NOTE: the researcher indicates that a vendor response was received, stating that this issue "falls into the work of our Firewall and not our AV (per our methodology of layers of defense)."

UnknownCVSS not scoredNot KEV-listedUpdatedSep 16, 2024, 22:15 UTC (UTC+00:00)

Security readout for executives and security teams

This CVE describes a protection gap in Symantec Norton AntiVirus 2011: malware may be correctly detected, but only after Microsoft Help and Support Center hcp:// URL processing has already allowed code execution. The business risk is highest for legacy endpoints that still rely on this product and URL handling path. Exposure appears limited to legacy environments using Symantec Norton AntiVirus 2011 where Microsoft Help and Support Center hcp:// URL processing remains reachable. The source bundle does not provide CPEs, exact operating systems, CVSS, CWE, or supported-version details. Medium discovery priority, escalating for any confirmed legacy deployment. There is no KEV-backed active exploitation signal in the bundle, but the described failure mode undermines prevention and involves possible remote code execution. Mitigation focus: Inventory endpoints for Norton AntiVirus 2011 or related legacy Symantec deployments.; Check Symantec and Microsoft guidance for supported fixes or compensating controls.; Do not rely on antivirus detection alone for this URL-handling path..

Prepared: Jun 27, 2026, 16:56 UTC (UTC+00:00)

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.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup

cve · low confidence lookup

CVE-2010-3497 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: Aug 22, 2012, 10:00 UTC (UTC+00:00)

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

1Source links

CVSS and timeline data

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

Source materials

CVE List V5 sourceCVE List V5

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.