CERTA-2011-AVI-574
Vulnerability from certfr_avis - Published: - Updated:
Plusieurs vulnérabilités permettant à un attaquant distant, soit de forcer l'équipement Cisco vulnérable à redémarrer, soit de contourner des politiques de sécurité ont été corrigées.
Description
Une première vulnérabilité dans le système d'inspection de paquets du protocole MSN IM permet à un attaquant de réaliser un déni de service lorsque celui-ci dirige du trafic spécialement conçu au travers de l'équipement vulnérable. L'équipement doit avoir activé l'inspection des paquets MSN IM (CVE-2011-3304).
Une vulnérabilité dans l'implémentation du protocole TACACS+ (Terminal Access Controller Access-Control System Plus) permet à un attaquant distant de contourner les règles de contrôle d'accès gérées par ce protocole (CVE-2011-3298).
Quatre vulnérabilités dans le système d'inspection des paquets du protocole SunRPC permettent à une personne malintentionnée de provoquer l'arrêt de l'appareil à distance au moyen de messages spécialement construits (CVE-2011-3299, CVE-2011-3300, CVE-2011-3301 et CVE-2011-3302).
Enfin, une vulnérabilité dans le système d'inspection de paquets du protocole ILS permet à un attaquant de réaliser un déni de service lorsque celui-ci dirige du trafic spécialement conçu au travers de l'équipement vulnérable. L'équipement doit avoir activé l'inspection des paquets ILS (CVE-2011-3303).
Solution
Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation).
None| Title | Publication Time | Tags | ||||||
|---|---|---|---|---|---|---|---|---|
|
||||||||
{
"$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
"affected_systems": [
{
"description": "\u00e9quipements Cisco s\u00e9rie 5500 Adaptive Security Appliances ;",
"product": {
"name": "N/A",
"vendor": {
"name": "Cisco",
"scada": false
}
}
},
{
"description": "\u00e9quipements Cisco Catalyst s\u00e9rie 6500 ASA Service Module.",
"product": {
"name": "N/A",
"vendor": {
"name": "Cisco",
"scada": false
}
}
}
],
"affected_systems_content": null,
"content": "## Description\n\nUne premi\u00e8re vuln\u00e9rabilit\u00e9 dans le syst\u00e8me d\u0027inspection de paquets du\nprotocole MSN IM permet \u00e0 un attaquant de r\u00e9aliser un d\u00e9ni de service\nlorsque celui-ci dirige du trafic sp\u00e9cialement con\u00e7u au travers de\nl\u0027\u00e9quipement vuln\u00e9rable. L\u0027\u00e9quipement doit avoir activ\u00e9 l\u0027inspection des\npaquets MSN IM (CVE-2011-3304).\n\nUne vuln\u00e9rabilit\u00e9 dans l\u0027impl\u00e9mentation du protocole TACACS+ (Terminal\nAccess Controller Access-Control System Plus) permet \u00e0 un attaquant\ndistant de contourner les r\u00e8gles de contr\u00f4le d\u0027acc\u00e8s g\u00e9r\u00e9es par ce\nprotocole (CVE-2011-3298).\n\nQuatre vuln\u00e9rabilit\u00e9s dans le syst\u00e8me d\u0027inspection des paquets du\nprotocole SunRPC permettent \u00e0 une personne malintentionn\u00e9e de provoquer\nl\u0027arr\u00eat de l\u0027appareil \u00e0 distance au moyen de messages sp\u00e9cialement\nconstruits (CVE-2011-3299, CVE-2011-3300, CVE-2011-3301 et\nCVE-2011-3302).\n\nEnfin, une vuln\u00e9rabilit\u00e9 dans le syst\u00e8me d\u0027inspection de paquets du\nprotocole ILS permet \u00e0 un attaquant de r\u00e9aliser un d\u00e9ni de service\nlorsque celui-ci dirige du trafic sp\u00e9cialement con\u00e7u au travers de\nl\u0027\u00e9quipement vuln\u00e9rable. L\u0027\u00e9quipement doit avoir activ\u00e9 l\u0027inspection des\npaquets ILS (CVE-2011-3303).\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-3302",
"url": "https://www.cve.org/CVERecord?id=CVE-2011-3302"
},
{
"name": "CVE-2011-3304",
"url": "https://www.cve.org/CVERecord?id=CVE-2011-3304"
},
{
"name": "CVE-2011-3299",
"url": "https://www.cve.org/CVERecord?id=CVE-2011-3299"
},
{
"name": "CVE-2011-3301",
"url": "https://www.cve.org/CVERecord?id=CVE-2011-3301"
},
{
"name": "CVE-2011-3303",
"url": "https://www.cve.org/CVERecord?id=CVE-2011-3303"
},
{
"name": "CVE-2011-3298",
"url": "https://www.cve.org/CVERecord?id=CVE-2011-3298"
},
{
"name": "CVE-2011-3300",
"url": "https://www.cve.org/CVERecord?id=CVE-2011-3300"
}
],
"links": [
{
"title": "Bulletin de s\u00e9curit\u00e9 Cisco 20111005-asa du 18 octobre 2011 :",
"url": "http://www.cisco.com/warp/public/707/cisco-sa-20111005-asa.shtml"
}
],
"reference": "CERTA-2011-AVI-574",
"revisions": [
{
"description": "version initiale.",
"revision_date": "2011-10-18T00:00:00.000000"
}
],
"risks": [
{
"description": "D\u00e9ni de service \u00e0 distance"
},
{
"description": "Contournement de la politique de s\u00e9curit\u00e9"
}
],
"summary": "Plusieurs vuln\u00e9rabilit\u00e9s permettant \u00e0 un attaquant distant, soit de\nforcer l\u0027\u00e9quipement Cisco vuln\u00e9rable \u00e0 red\u00e9marrer, soit de contourner\ndes politiques de s\u00e9curit\u00e9 ont \u00e9t\u00e9 corrig\u00e9es.\n",
"title": "Multiples vuln\u00e9rabilit\u00e9s dans Cisco Adaptive Security Appliances",
"vendor_advisories": [
{
"published_at": null,
"title": "Bulletin de s\u00e9curit\u00e9 Cisco 20111005-asa du 05 octobre 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.