CERTA-2010-AVI-087
Vulnerability from certfr_avis - Published: 2010-02-22 - Updated: 2010-02-23
De multiples vulnérabilités dans plusieurs produits Symantec permettent l'exécution de code arbitraire à distance ou le contournement de la politique de sécurité.
Description
De multiples vulnérabilités ont été découvertes dans plusieurs produits Symantec :
- une vulnérabilité de type débordement de mémoire a été découverte dans le composant Symantec Client Proxy. Un utilisateur peut exécuter du code arbitraire à distance par le biais d'un contrôle ActiveX spécialement conçu ;
- une vulnérabilité de type débordement de mémoire a été découverte dans la bibliothèque SYMLTCOM.dll. Un utilisateur peut l'exploiter pour exécuter du code arbitraire dans le contexte du navigateur de l'utilisateur ;
- une autre vulnérabilité concerne la fonctionnalité d'analyse antivirale à la demande. Cette analyse peut être contournée localement en effectuant un certain nombre d'actions spécifiques.
Solution
Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation).
None| Vendor | Product | Description | ||
|---|---|---|---|---|
| Symantec | N/A | Symantec Endpoint Protection versions 11.x. | ||
| Symantec | N/A | Symantec Client Security versions 3.0.x, 3.1.x ; | ||
| Symantec | N/A | Symantec AntiVirus versions 10.0.x, 10.1.x, et 10.2.x ; | ||
| Symantec | N/A | Norton Antivirus, SystemWorks, Confidential et Internet Security versions 2006, 2007 et 2008 ; |
| Title | Publication Time | Tags | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||
{
"$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
"affected_systems": [
{
"description": "Symantec Endpoint Protection versions 11.x.",
"product": {
"name": "N/A",
"vendor": {
"name": "Symantec",
"scada": false
}
}
},
{
"description": "Symantec Client Security versions 3.0.x, 3.1.x ;",
"product": {
"name": "N/A",
"vendor": {
"name": "Symantec",
"scada": false
}
}
},
{
"description": "Symantec AntiVirus versions 10.0.x, 10.1.x, et 10.2.x ;",
"product": {
"name": "N/A",
"vendor": {
"name": "Symantec",
"scada": false
}
}
},
{
"description": "Norton Antivirus, SystemWorks, Confidential et Internet Security versions 2006, 2007 et 2008 ;",
"product": {
"name": "N/A",
"vendor": {
"name": "Symantec",
"scada": false
}
}
}
],
"affected_systems_content": null,
"content": "## Description\n\nDe multiples vuln\u00e9rabilit\u00e9s ont \u00e9t\u00e9 d\u00e9couvertes dans plusieurs produits\nSymantec :\n\n- une vuln\u00e9rabilit\u00e9 de type d\u00e9bordement de m\u00e9moire a \u00e9t\u00e9 d\u00e9couverte\n dans le composant Symantec Client Proxy. Un utilisateur peut\n ex\u00e9cuter du code arbitraire \u00e0 distance par le biais d\u0027un contr\u00f4le\n ActiveX sp\u00e9cialement con\u00e7u ;\n- une vuln\u00e9rabilit\u00e9 de type d\u00e9bordement de m\u00e9moire a \u00e9t\u00e9 d\u00e9couverte\n dans la biblioth\u00e8que SYMLTCOM.dll. Un utilisateur peut l\u0027exploiter\n pour ex\u00e9cuter du code arbitraire dans le contexte du navigateur de\n l\u0027utilisateur\u00a0;\n- une autre vuln\u00e9rabilit\u00e9 concerne la fonctionnalit\u00e9 d\u0027analyse\n antivirale \u00e0 la demande. Cette analyse peut \u00eatre contourn\u00e9e\n localement en effectuant un certain nombre d\u0027actions sp\u00e9cifiques.\n\n## Solution\n\nSe r\u00e9f\u00e9rer au bulletin de s\u00e9curit\u00e9 de l\u0027\u00e9diteur pour l\u0027obtention des\ncorrectifs (cf. section Documentation).\n",
"cves": [
{
"name": "CVE-2010-0108",
"url": "https://www.cve.org/CVERecord?id=CVE-2010-0108"
},
{
"name": "CVE-2010-0106",
"url": "https://www.cve.org/CVERecord?id=CVE-2010-0106"
},
{
"name": "CVE-2010-0107",
"url": "https://www.cve.org/CVERecord?id=CVE-2010-0107"
}
],
"initial_release_date": "2010-02-22T00:00:00",
"last_revision_date": "2010-02-23T00:00:00",
"links": [],
"reference": "CERTA-2010-AVI-087",
"revisions": [
{
"description": "version initiale.",
"revision_date": "2010-02-22T00:00:00.000000"
},
{
"description": "ajout d\u0027une troisi\u00e8me vuln\u00e9rabilit\u00e9.",
"revision_date": "2010-02-23T00:00:00.000000"
}
],
"risks": [
{
"description": "Ex\u00e9cution de code arbitraire \u00e0 distance"
},
{
"description": "Contournement de la politique de s\u00e9curit\u00e9"
}
],
"summary": "De multiples vuln\u00e9rabilit\u00e9s dans plusieurs produits \u003cspan\nclass=\"textit\"\u003eSymantec\u003c/span\u003e permettent l\u0027ex\u00e9cution de code arbitraire\n\u00e0 distance ou le contournement de la politique de s\u00e9curit\u00e9.\n",
"title": "Multiples vuln\u00e9rabilit\u00e9s dans plusieurs produits Symantec",
"vendor_advisories": [
{
"published_at": null,
"title": "Bulletin de s\u00e9curit\u00e9 Symantec SYM10-003 du 17 f\u00e9vrier 2010",
"url": "http://www.symantec.com/business/security_response/securityupdates/detail.jsp?fid=security_advisory\u0026pvid=security_advisory\u0026year=2010\u0026suid=20100217_01"
},
{
"published_at": null,
"title": "Bulletin de s\u00e9curit\u00e9 Symantec SYM10-004 du 17 f\u00e9vrier 2010",
"url": "http://www.symantec.com/business/security_response/securityupdates/detail.jsp?fid=security_advisory\u0026pvid=security_advisory\u0026year=2010\u0026suid=20100217_02"
},
{
"published_at": null,
"title": "Bulletin de s\u00e9curit\u00e9 Symantec SYM10-002 du 17 f\u00e9vrier 2010",
"url": "http://www.symantec.com/business/security_response/securityupdates/detail.jsp?fid=security_advisory\u0026pvid=security_advisory\u0026year=2010\u0026suid=20100217_00"
}
]
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.