CERTA-2009-AVI-294
Vulnerability from certfr_avis - Published: 2009-07-27 - Updated: 2009-07-27
Deux vulnérabilités présentes dans Cisco Unified Contact Center Express permettent à un utilisateur distant de porter atteinte à la confidentialité et à l'intégrité de certaines données ou de réaliser des attaques par injection de code indirecte.
Description
Deux vulnérabilités ont été identifiées dans Cisco Unified Contact Center Express :
- la première est relative au service Customer Responses Solutions et permet à un utilisateur distant de porter atteinte à la confidentialité ou à l'intégrité de certains fichiers du système ;
- la seconde concerne un manque de contrôle des entrées passées à la base de données de Cisco Unified Contact Center Express et permet à un utilisateur distant de réaliser des attaques de type injection de code indirecte.
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 Contact Center Express 6.x ;",
"product": {
"name": "N/A",
"vendor": {
"name": "Cisco",
"scada": false
}
}
},
{
"description": "Cisco Unified Contact Center Express 5.x ;",
"product": {
"name": "N/A",
"vendor": {
"name": "Cisco",
"scada": false
}
}
},
{
"description": "Cisco Unified Contact Center Express 7.x.",
"product": {
"name": "N/A",
"vendor": {
"name": "Cisco",
"scada": false
}
}
}
],
"affected_systems_content": null,
"content": "## Description\n\nDeux vuln\u00e9rabilit\u00e9s ont \u00e9t\u00e9 identifi\u00e9es dans Cisco Unified Contact\nCenter Express :\n\n- la premi\u00e8re est relative au service Customer Responses Solutions et\n permet \u00e0 un utilisateur distant de porter atteinte \u00e0 la\n confidentialit\u00e9 ou \u00e0 l\u0027int\u00e9grit\u00e9 de certains fichiers du syst\u00e8me ;\n- la seconde concerne un manque de contr\u00f4le des entr\u00e9es pass\u00e9es \u00e0 la\n base de donn\u00e9es de Cisco Unified Contact Center Express et permet \u00e0\n un utilisateur distant de r\u00e9aliser des attaques de type injection de\n code indirecte.\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-2009-2047",
"url": "https://www.cve.org/CVERecord?id=CVE-2009-2047"
},
{
"name": "CVE-2009-2048",
"url": "https://www.cve.org/CVERecord?id=CVE-2009-2048"
}
],
"initial_release_date": "2009-07-27T00:00:00",
"last_revision_date": "2009-07-27T00:00:00",
"links": [
{
"title": "Bulletin de s\u00e9curit\u00e9 Cisco 20090715-uccx du 15 juillet 2009 :",
"url": "http://www.cisco.com/warp/public/707/cisco-sa-20090715-uccx.shtml"
}
],
"reference": "CERTA-2009-AVI-294",
"revisions": [
{
"description": "version initiale.",
"revision_date": "2009-07-27T00:00:00.000000"
}
],
"risks": [
{
"description": "Injection de code indirecte"
},
{
"description": "Atteinte \u00e0 l\u0027int\u00e9grit\u00e9 des donn\u00e9es"
},
{
"description": "Atteinte \u00e0 la confidentialit\u00e9 des donn\u00e9es"
}
],
"summary": "Deux vuln\u00e9rabilit\u00e9s pr\u00e9sentes dans Cisco Unified Contact Center Express\npermettent \u00e0 un utilisateur distant de porter atteinte \u00e0 la\nconfidentialit\u00e9 et \u00e0 l\u0027int\u00e9grit\u00e9 de certaines donn\u00e9es ou de r\u00e9aliser des\nattaques par injection de code indirecte.\n",
"title": "Multiples vuln\u00e9rabilit\u00e9s dans Cisco Unified Contact Center Express",
"vendor_advisories": [
{
"published_at": null,
"title": "Bulletin de s\u00e9curit\u00e9 Cisco #110307",
"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.