CERTA-2008-AVI-497
Vulnerability from certfr_avis - Published: 2008-10-15 - Updated: 2008-10-15
Une vulnérabilité affectant Microsoft Office permet à une personne malintentionnée de porter atteinte à la confidentialité des données.
Description
Une vulnérabilité affectant la gestion du protocole CDO (Collaboration Data Objects) de Microsoft Office permet à une personne malveillante de porter atteinte à la confidentialité des données via une adresse réticulaire CDO spécialement conçue. Cette vulnérabilité permet via le navigateur du client de divulguer des informations, d'usurper du contenu ou d'entreprendre des actions que l'utilisateur pourrait effectuer sur le site Web affecté.
Solution
Se référer au bulletin de sécurité MS08-056 de Microsoft 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": "Microsoft Office XP Service Pack 3.",
"product": {
"name": "Office",
"vendor": {
"name": "Microsoft",
"scada": false
}
}
}
],
"affected_systems_content": null,
"content": "## Description\n\nUne vuln\u00e9rabilit\u00e9 affectant la gestion du protocole CDO (Collaboration\nData Objects) de Microsoft Office permet \u00e0 une personne malveillante de\nporter atteinte \u00e0 la confidentialit\u00e9 des donn\u00e9es via une adresse\nr\u00e9ticulaire CDO sp\u00e9cialement con\u00e7ue. Cette vuln\u00e9rabilit\u00e9 permet via le\nnavigateur du client de divulguer des informations, d\u0027usurper du contenu\nou d\u0027entreprendre des actions que l\u0027utilisateur pourrait effectuer sur\nle site Web affect\u00e9.\n\n## Solution\n\nSe r\u00e9f\u00e9rer au bulletin de s\u00e9curit\u00e9 MS08-056 de Microsoft pour\nl\u0027obtention des correctifs (cf. section Documentation).\n",
"cves": [
{
"name": "CVE-2008-4020",
"url": "https://www.cve.org/CVERecord?id=CVE-2008-4020"
}
],
"initial_release_date": "2008-10-15T00:00:00",
"last_revision_date": "2008-10-15T00:00:00",
"links": [],
"reference": "CERTA-2008-AVI-497",
"revisions": [
{
"description": "version initiale.",
"revision_date": "2008-10-15T00:00:00.000000"
}
],
"risks": [
{
"description": "Atteinte \u00e0 la confidentialit\u00e9 des donn\u00e9es"
}
],
"summary": "Une vuln\u00e9rabilit\u00e9 affectant Microsoft Office permet \u00e0 une personne\nmalintentionn\u00e9e de porter atteinte \u00e0 la confidentialit\u00e9 des donn\u00e9es.\n",
"title": "Vuln\u00e9rabilit\u00e9 dans Microsoft Office",
"vendor_advisories": [
{
"published_at": null,
"title": "Bulletin de s\u00e9curit\u00e9 Microsoft MS08-056 du 14 octobre 2008",
"url": "http://www.microsoft.com/technet/security/Bulletin/MS08-056.mspx"
}
]
}
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.