CERTA-2011-AVI-451
Vulnerability from certfr_avis - Published: 2011-08-11 - Updated: 2011-08-11
De multiples vulnérabilités permettant de faire de l'injection de code indirecte (XSS) et de l'injection de requêtes illégitime par rebond (CSRF) ont été corrigées dans Symantec Endpoint Protection Manager.
Description
Des erreurs dans le traitement des requêtes Web reçues par Symantec Endpoint Protection Manager permettent à une personne malintentionnée d'injecter indirectement du code à distance et des requêtes illégitimes par rebond (XSS et CSRF).
Solution
Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation).
Symantec Endpoint Protection Manager 11.x.
| Vendor | Product | Description |
|---|
| Title | Publication Time | Tags | ||||||
|---|---|---|---|---|---|---|---|---|
|
||||||||
{
"$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
"affected_systems": [],
"affected_systems_content": "\u003cp\u003eSymantec Endpoint Protection Manager 11.x.\u003c/p\u003e",
"content": "## Description\n\nDes erreurs dans le traitement des requ\u00eates Web re\u00e7ues par Symantec\nEndpoint Protection Manager permettent \u00e0 une personne malintentionn\u00e9e\nd\u0027injecter indirectement du code \u00e0 distance et des requ\u00eates ill\u00e9gitimes\npar rebond (XSS et CSRF).\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-2011-0551",
"url": "https://www.cve.org/CVERecord?id=CVE-2011-0551"
},
{
"name": "CVE-2011-0550",
"url": "https://www.cve.org/CVERecord?id=CVE-2011-0550"
}
],
"initial_release_date": "2011-08-11T00:00:00",
"last_revision_date": "2011-08-11T00:00:00",
"links": [
{
"title": "Bulletin de s\u00e9curit\u00e9 Symantec SYM11-009 du 10 ao\u00fbt 2011 :",
"url": "http://www.symantec.com/business/security_response/securityupdates/detail.jsp?fid=security_advisory\u0026pvid=security_advisory\u0026year=2011\u0026suid=20110810_00"
}
],
"reference": "CERTA-2011-AVI-451",
"revisions": [
{
"description": "version initiale.",
"revision_date": "2011-08-11T00:00:00.000000"
}
],
"risks": [
{
"description": "Injection de requ\u00eates ill\u00e9gitimes par rebond (CSRF)"
},
{
"description": "Injection de code indirecte \u00e0 distance"
}
],
"summary": "De multiples vuln\u00e9rabilit\u00e9s permettant de faire de l\u0027injection de code\nindirecte (XSS) et de l\u0027injection de requ\u00eates ill\u00e9gitime par rebond\n(CSRF) ont \u00e9t\u00e9 corrig\u00e9es dans \u003cspan class=\"textit\"\u003eSymantec Endpoint\nProtection Manager\u003c/span\u003e.\n",
"title": "Vuln\u00e9rabilit\u00e9s dans Symantec Endpoint Protection Manager",
"vendor_advisories": [
{
"published_at": null,
"title": "Bulletin de s\u00e9curit\u00e9 Symantec du 10 ao\u00fbt 2011",
"url": null
}
]
}
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.