CERTA-2006-AVI-284
Vulnerability from certfr_avis - Published: 2006-07-12 - Updated: 2006-07-12None
Description
Deux vulnérabilités ont été identifiées dans Microsoft Office. Elles concernent le filtrage de certains fichiers :
- la première vise le format PNG. Microsoft Office ne vérifie pas correctement l'allocation de l'espace mémoire. Une personne malveillante peut donc construire un fichier .PNG mal formé exploitant cette vulnérabilité, dans le but d'exécuter des commandes arbitraires sur le système vulnérable, quand l'utilisateur ouvrira ce fichier via Microsoft Office.
- la seconde vise le format GIF. Microsoft Office ne vérifie pas correctement l'allocation de l'espace mémoire lorsqu'il ouvre un fichier GIF. Un utilisateur malveillant peut construire un fichier spécial contenant une chaîne de caractères mal formée, afin d'exécuter du code arbitraire sur le système affecté.
Solution
Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation).
- Microsoft Office 2003 Service Pack 1 et Service Pack 2 ;
- Microsoft Office XP Service Pack 3 ;
- Microsoft Office 2000 Service Pack 3 ;
- Microsoft Project 2002 ;
- Microsoft Project 2000 ;
- Microsoft Works Suites : 2004, 2005 et 2006.
Les visionneuses Microsoft Office, ainsi que Microsoft Office 2004 et Microsoft Office v. X pour MacOS ne sont pas concernées.
| Vendor | Product | Description |
|---|
| Title | Publication Time | Tags | |
|---|---|---|---|
{
"$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
"affected_systems": [],
"affected_systems_content": "\u003cUL\u003e \u003cLI\u003eMicrosoft Office 2003 Service Pack 1 et Service Pack 2 ;\u003c/LI\u003e \u003cLI\u003eMicrosoft Office XP Service Pack 3 ;\u003c/LI\u003e \u003cLI\u003eMicrosoft Office 2000 Service Pack 3 ;\u003c/LI\u003e \u003cLI\u003eMicrosoft Project 2002 ;\u003c/LI\u003e \u003cLI\u003eMicrosoft Project 2000 ;\u003c/LI\u003e \u003cLI\u003eMicrosoft Works Suites : 2004, 2005 et 2006.\u003c/LI\u003e \u003c/UL\u003e \u003cP\u003eLes visionneuses Microsoft Office, ainsi que Microsoft Office 2004 et Microsoft Office v. X pour MacOS ne sont pas concern\u00e9es.\u003c/P\u003e",
"content": "## Description\n\nDeux vuln\u00e9rabilit\u00e9s ont \u00e9t\u00e9 identifi\u00e9es dans Microsoft Office. Elles\nconcernent le filtrage de certains fichiers :\n\n- la premi\u00e8re vise le format PNG. Microsoft Office ne v\u00e9rifie pas\n correctement l\u0027allocation de l\u0027espace m\u00e9moire. Une personne\n malveillante peut donc construire un fichier .PNG mal form\u00e9\n exploitant cette vuln\u00e9rabilit\u00e9, dans le but d\u0027ex\u00e9cuter des commandes\n arbitraires sur le syst\u00e8me vuln\u00e9rable, quand l\u0027utilisateur ouvrira\n ce fichier via Microsoft Office.\n- la seconde vise le format GIF. Microsoft Office ne v\u00e9rifie pas\n correctement l\u0027allocation de l\u0027espace m\u00e9moire lorsqu\u0027il ouvre un\n fichier GIF. Un utilisateur malveillant peut construire un fichier\n sp\u00e9cial contenant une cha\u00eene de caract\u00e8res mal form\u00e9e, afin\n d\u0027ex\u00e9cuter du code arbitraire sur le syst\u00e8me affect\u00e9.\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-2006-0033",
"url": "https://www.cve.org/CVERecord?id=CVE-2006-0033"
}
],
"initial_release_date": "2006-07-12T00:00:00",
"last_revision_date": "2006-07-12T00:00:00",
"links": [
{
"title": "Bulletin de s\u00e9curit\u00e9 Microsoft MS06-039 du 11 juillet 2006 :",
"url": "http://www.microsoft.com/france/technet/security/Bulletin/MS06-039.mspx"
},
{
"title": "Bulletin de s\u00e9curit\u00e9 Microsoft MS06-039 du 11 juillet 2006 :",
"url": "http://www.microsoft.com/technet/security/Bulletin/MS06-039.mspx"
}
],
"reference": "CERTA-2006-AVI-284",
"revisions": [
{
"description": "version initiale.",
"revision_date": "2006-07-12T00:00:00.000000"
}
],
"risks": [
{
"description": "Ex\u00e9cution de code arbitraire \u00e0 distance"
}
],
"summary": null,
"title": "Vuln\u00e9rabilit\u00e9s de certains filtres de Microsoft Office",
"vendor_advisories": [
{
"published_at": null,
"title": "Bulletin de s\u00e9curit\u00e9 de Microsoft du 11 juillet 2006",
"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.