CERTA-2006-AVI-389
Vulnerability from certfr_avis - Published: 2006-09-13 - Updated: 2006-09-13
Une vulnérabilité a été identifiée dans certaines versions de l'application Microsoft Publisher. Une personne malveillante pourrait construire une fichier exploitant cette vulnérabilité, afin d'exécuter du code arbitraire sur le système où le document sera ouvert.
Description
Publisher est une application fournie par Microsoft servant à la publication de documents (logiciel PAO, pour publication assistée par ordinateur).
Une vulnérabilité a été identifiée dans ce dernier. Il ne contrôlerait pas de manière correcte certaines chaînes de caractères malformées dans des fichiers au format .pub.
Une personne malveillante pourrait construire une fichier exploitant cette vulnérabilité, afin d'exécuter du code arbitraire sur le système où le document sera ouvert.
Solution
Se référer au bulletin de sécurité MS06-054 de Microsoft pour l'application des correctifs (cf. section Documentation).
None| Vendor | Product | Description | ||
|---|---|---|---|---|
| Microsoft | Office | Office Publisher 2000 fourni dans la suite Microsoft Office 2000 Service Pack 3 ; | ||
| Microsoft | Office | Office Publisher 2002 fourni dans la suite Microsoft Office XP Service Pack 3 ; | ||
| Microsoft | Office | Office Publisher 2003 fourni dans la suite Microsoft Office 2003 Service Pack 1 et Service Pack 2. |
| Title | Publication Time | Tags | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||
{
"$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
"affected_systems": [
{
"description": "Office Publisher 2000 fourni dans la suite Microsoft Office 2000 Service Pack 3 ;",
"product": {
"name": "Office",
"vendor": {
"name": "Microsoft",
"scada": false
}
}
},
{
"description": "Office Publisher 2002 fourni dans la suite Microsoft Office XP Service Pack 3 ;",
"product": {
"name": "Office",
"vendor": {
"name": "Microsoft",
"scada": false
}
}
},
{
"description": "Office Publisher 2003 fourni dans la suite Microsoft Office 2003 Service Pack 1 et Service Pack 2.",
"product": {
"name": "Office",
"vendor": {
"name": "Microsoft",
"scada": false
}
}
}
],
"affected_systems_content": null,
"content": "## Description\n\nPublisher est une application fournie par Microsoft servant \u00e0 la\npublication de documents (logiciel PAO, pour publication assist\u00e9e par\nordinateur).\n\nUne vuln\u00e9rabilit\u00e9 a \u00e9t\u00e9 identifi\u00e9e dans ce dernier. Il ne contr\u00f4lerait\npas de mani\u00e8re correcte certaines cha\u00eenes de caract\u00e8res malform\u00e9es dans\ndes fichiers au format .pub.\n\nUne personne malveillante pourrait construire une fichier exploitant\ncette vuln\u00e9rabilit\u00e9, afin d\u0027ex\u00e9cuter du code arbitraire sur le syst\u00e8me\no\u00f9 le document sera ouvert.\n\n## Solution\n\nSe r\u00e9f\u00e9rer au bulletin de s\u00e9curit\u00e9 MS06-054 de Microsoft pour\nl\u0027application des correctifs (cf. section Documentation).\n",
"cves": [
{
"name": "CVE-2006-0001",
"url": "https://www.cve.org/CVERecord?id=CVE-2006-0001"
}
],
"initial_release_date": "2006-09-13T00:00:00",
"last_revision_date": "2006-09-13T00:00:00",
"links": [
{
"title": "Bulletin de s\u00e9curit\u00e9 Microsoft MS06-054 du :",
"url": "http://www.microsoft.com/france/technet/security/bulletin/2006/MS06-054.mspx"
},
{
"title": "Bulletin de s\u00e9curit\u00e9 Microsoft MS06-054 du :",
"url": "http://www.microsoft.com/technet/security/Bulletin/MS06-054.mspx"
}
],
"reference": "CERTA-2006-AVI-389",
"revisions": [
{
"description": "version initiale.",
"revision_date": "2006-09-13T00:00:00.000000"
}
],
"risks": [
{
"description": "Ex\u00e9cution de code arbitraire \u00e0 distance"
}
],
"summary": "Une vuln\u00e9rabilit\u00e9 a \u00e9t\u00e9 identifi\u00e9e dans certaines versions de\nl\u0027application Microsoft Publisher. Une personne malveillante pourrait\nconstruire une fichier exploitant cette vuln\u00e9rabilit\u00e9, afin d\u0027ex\u00e9cuter\ndu code arbitraire sur le syst\u00e8me o\u00f9 le document sera ouvert.\n",
"title": "Vuln\u00e9rabilit\u00e9 dans Microsoft Publisher",
"vendor_advisories": [
{
"published_at": null,
"title": "Bulletin de s\u00e9curit\u00e9 Microsoft MS06-054 du 12 septembre 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.