CERTA-2008-AVI-075
Vulnerability from certfr_avis - Published: 2008-02-13 - Updated: 2008-02-13
Des vulnérabilités ont été identifiées dans l'application Microsoft Office Publisher. L'exploitation de ces dernières peut entraîner dans certaines conditions l'exécution de code arbitraire sur le système vulnérable.
Description
Des vulnérabilités ont été identifiées dans l'application Microsoft Office Publisher. Parmi celles-ci :
- les données de l'application ne seraient pas correctement vérifiées lors du chargement de fichiers Publisher en mémoire. Une personne pourrait exploiter cette vulnérabilité au moyen d'un fichier .pub spécialement construit afin d'exécuter des commandes malveillantes sur le système lors de son ouverture ;
- les valeurs d'index mémoire ne seraient pas correctement validées. Une personne pourrait également exploiter cette vulnérabilité au moyen d'un fichier .pub spécialement construit.
Solution
Se référer au bulletin de sécurité MS08-012 de Microsoft pour l'obtention des correctifs (cf. section Documentation).
None| Vendor | Product | Description | ||
|---|---|---|---|---|
| Microsoft | Office | Microsoft Office Publisher 2003 SP2 dans Microsoft Office 2003 Service Pack 2. | ||
| Microsoft | Office | Microsoft Office Publisher 2002 dans Microsoft Office XP Service Pack 3 ; | ||
| Microsoft | Office | Microsoft Office Publisher 2000 dans Microsoft Office 2000 Service Pack 3 ; |
| Title | Publication Time | Tags | |||
|---|---|---|---|---|---|
|
|||||
{
"$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
"affected_systems": [
{
"description": "Microsoft Office Publisher 2003 SP2 dans Microsoft Office 2003 Service Pack 2.",
"product": {
"name": "Office",
"vendor": {
"name": "Microsoft",
"scada": false
}
}
},
{
"description": "Microsoft Office Publisher 2002 dans Microsoft Office XP Service Pack 3 ;",
"product": {
"name": "Office",
"vendor": {
"name": "Microsoft",
"scada": false
}
}
},
{
"description": "Microsoft Office Publisher 2000 dans Microsoft Office 2000 Service Pack 3 ;",
"product": {
"name": "Office",
"vendor": {
"name": "Microsoft",
"scada": false
}
}
}
],
"affected_systems_content": null,
"content": "## Description\n\nDes vuln\u00e9rabilit\u00e9s ont \u00e9t\u00e9 identifi\u00e9es dans l\u0027application Microsoft\nOffice Publisher. Parmi celles-ci :\n\n- les donn\u00e9es de l\u0027application ne seraient pas correctement v\u00e9rifi\u00e9es\n lors du chargement de fichiers Publisher en m\u00e9moire. Une personne\n pourrait exploiter cette vuln\u00e9rabilit\u00e9 au moyen d\u0027un fichier .pub\n sp\u00e9cialement construit afin d\u0027ex\u00e9cuter des commandes malveillantes\n sur le syst\u00e8me lors de son ouverture ;\n- les valeurs d\u0027index m\u00e9moire ne seraient pas correctement valid\u00e9es.\n Une personne pourrait \u00e9galement exploiter cette vuln\u00e9rabilit\u00e9 au\n moyen d\u0027un fichier .pub sp\u00e9cialement construit.\n\n## Solution\n\nSe r\u00e9f\u00e9rer au bulletin de s\u00e9curit\u00e9 MS08-012 de Microsoft pour\nl\u0027obtention des correctifs (cf. section Documentation).\n",
"cves": [
{
"name": "CVE-2008-0104",
"url": "https://www.cve.org/CVERecord?id=CVE-2008-0104"
},
{
"name": "CVE-2008-0102",
"url": "https://www.cve.org/CVERecord?id=CVE-2008-0102"
}
],
"initial_release_date": "2008-02-13T00:00:00",
"last_revision_date": "2008-02-13T00:00:00",
"links": [],
"reference": "CERTA-2008-AVI-075",
"revisions": [
{
"description": "version initiale.",
"revision_date": "2008-02-13T00:00:00.000000"
}
],
"risks": [
{
"description": "Ex\u00e9cution de code arbitraire \u00e0 distance"
}
],
"summary": "Des vuln\u00e9rabilit\u00e9s ont \u00e9t\u00e9 identifi\u00e9es dans l\u0027application Microsoft\nOffice Publisher. L\u0027exploitation de ces derni\u00e8res peut entra\u00eener dans\ncertaines conditions l\u0027ex\u00e9cution de code arbitraire sur le syst\u00e8me\nvuln\u00e9rable.\n",
"title": "Vuln\u00e9rabilit\u00e9s dans Microsoft Office Publisher",
"vendor_advisories": [
{
"published_at": null,
"title": "Bulletin de s\u00e9curit\u00e9 Microsoft MS08-012 du 12 f\u00e9vrier 2008",
"url": "http://www.microsoft.com/technet/security/Bulletin/MS08-012.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.