CERTA-2010-AVI-034
Vulnerability from certfr_avis - Published: 2010-01-29 - Updated: 2010-01-29
De multiples vulnérabilités ont été découvertes dans Cisco Unified MeetingPlace. L'exploitation de ces vulnérabilités permet de réaliser différentes actions malveillantes, allant jusqu'à l'élévation de privilèges.
Description
Quatre vulnérabilités ont été découvertes dans Cisco Unified MeetingPlace :
- la première est due à une erreur dans la gestion des requêtes SQL et peut être exploitée afin d'injecter du code SQL arbitraire ;
- la deuxième est due à une erreur dans la gestion des requêtes à destination de l'interface interne du serveur web. L'exploitation de cette vulnérabilité permet de contourner les mécanismes de sécurité ;
- la troisième et la quatrième vulnérabilité sont dues à des erreurs dans le mécanisme d'authentification MeetingTime et peuvent être exploitées afin de récupérer des couples d'authentification et/ou d'élever ses privilèges au niveau administrateur.
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": "Cisco Unified MeetingPlace versions 5.x ;",
"product": {
"name": "N/A",
"vendor": {
"name": "Cisco",
"scada": false
}
}
},
{
"description": "Cisco Unified MeetingPlace versions 7.x.",
"product": {
"name": "N/A",
"vendor": {
"name": "Cisco",
"scada": false
}
}
},
{
"description": "Cisco Unified MeetingPlace versions 6.x ;",
"product": {
"name": "N/A",
"vendor": {
"name": "Cisco",
"scada": false
}
}
}
],
"affected_systems_content": null,
"content": "## Description\n\nQuatre vuln\u00e9rabilit\u00e9s ont \u00e9t\u00e9 d\u00e9couvertes dans Cisco Unified\nMeetingPlace :\n\n- la premi\u00e8re est due \u00e0 une erreur dans la gestion des requ\u00eates SQL et\n peut \u00eatre exploit\u00e9e afin d\u0027injecter du code SQL arbitraire ;\n- la deuxi\u00e8me est due \u00e0 une erreur dans la gestion des requ\u00eates \u00e0\n destination de l\u0027interface interne du serveur web. L\u0027exploitation de\n cette vuln\u00e9rabilit\u00e9 permet de contourner les m\u00e9canismes de s\u00e9curit\u00e9\n ;\n- la troisi\u00e8me et la quatri\u00e8me vuln\u00e9rabilit\u00e9 sont dues \u00e0 des erreurs\n dans le m\u00e9canisme d\u0027authentification MeetingTime et peuvent \u00eatre\n exploit\u00e9es afin de r\u00e9cup\u00e9rer des couples d\u0027authentification et/ou\n d\u0027\u00e9lever ses privil\u00e8ges au niveau administrateur.\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-0141",
"url": "https://www.cve.org/CVERecord?id=CVE-2010-0141"
},
{
"name": "CVE-2010-0142",
"url": "https://www.cve.org/CVERecord?id=CVE-2010-0142"
},
{
"name": "CVE-2010-0140",
"url": "https://www.cve.org/CVERecord?id=CVE-2010-0140"
},
{
"name": "CVE-2010-0139",
"url": "https://www.cve.org/CVERecord?id=CVE-2010-0139"
}
],
"initial_release_date": "2010-01-29T00:00:00",
"last_revision_date": "2010-01-29T00:00:00",
"links": [
{
"title": "Bulletin de s\u00e9curit\u00e9 Cisco 20100127-mp du 27 janvier 2010 :",
"url": "http://www.cisco.com/warp/public/707/cisco-sa-20100127-mp.shtml"
}
],
"reference": "CERTA-2010-AVI-034",
"revisions": [
{
"description": "version initiale.",
"revision_date": "2010-01-29T00:00:00.000000"
}
],
"risks": [
{
"description": "Atteinte \u00e0 l\u0027int\u00e9grit\u00e9 des donn\u00e9es"
},
{
"description": "Contournement de la politique de s\u00e9curit\u00e9"
},
{
"description": "Atteinte \u00e0 la confidentialit\u00e9 des donn\u00e9es"
},
{
"description": "\u00c9l\u00e9vation de privil\u00e8ges"
}
],
"summary": "De multiples vuln\u00e9rabilit\u00e9s ont \u00e9t\u00e9 d\u00e9couvertes dans Cisco Unified\nMeetingPlace. L\u0027exploitation de ces vuln\u00e9rabilit\u00e9s permet de r\u00e9aliser\ndiff\u00e9rentes actions malveillantes, allant jusqu\u0027\u00e0 l\u0027\u00e9l\u00e9vation de\nprivil\u00e8ges.\n",
"title": "Multiples vuln\u00e9rabilit\u00e9s dans Cisco Unified MeetingPlace",
"vendor_advisories": [
{
"published_at": null,
"title": "Bulletin de s\u00e9curit\u00e9 Cisco cisco-sa-20100127-mp du 27 janvier 2010",
"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.