CERTA-2011-AVI-684
Vulnerability from certfr_avis - Published: - Updated:
Une vulnérabilité dans la gestion des polices TrueType de Windows permet à une personne malintentionnée d'exécuter du code arbitraire à distance.
Description
Une vulnérabilité présente dans le noyau de Windows permet d'exécuter du code arbitraire à distance et d'élever ses privilèges au niveau système. Elle est déclenchée lors de l'ouverture par l'utilisateur d'un document contenant une police de caractères TrueType spécialement conçue.
Cette vulnérabilité a été détaillée dans l'alerte du CERTA CERTA-2011-ALE-006.
Solution
Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation).
Toutes les versions supportées de Microsoft Windows.
| Vendor | Product | Description |
|---|
| Title | Publication Time | Tags | |
|---|---|---|---|
{
"$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
"affected_systems": [],
"affected_systems_content": "\u003cp\u003eToutes les versions support\u00e9es de Microsoft Windows.\u003c/p\u003e",
"content": "## Description\n\nUne vuln\u00e9rabilit\u00e9 pr\u00e9sente dans le noyau de Windows permet d\u0027ex\u00e9cuter du\ncode arbitraire \u00e0 distance et d\u0027\u00e9lever ses privil\u00e8ges au niveau syst\u00e8me.\nElle est d\u00e9clench\u00e9e lors de l\u0027ouverture par l\u0027utilisateur d\u0027un document\ncontenant une police de caract\u00e8res TrueType sp\u00e9cialement con\u00e7ue.\n\nCette vuln\u00e9rabilit\u00e9 a \u00e9t\u00e9 d\u00e9taill\u00e9e dans l\u0027alerte du CERTA\nCERTA-2011-ALE-006.\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-2011-3402",
"url": "https://www.cve.org/CVERecord?id=CVE-2011-3402"
}
],
"links": [
{
"title": "Avis de s\u00e9curit\u00e9 Microsoft 2639658 du 03 novembre 2011 :",
"url": "http://technet.microsoft.com/en-us/security/advisory/2639658"
},
{
"title": "Avis de s\u00e9curit\u00e9 Microsoft 2639658 du 03 novembre 2011 :",
"url": "http://technet.microsoft.com/fr-fr/security/advisory/2639658"
},
{
"title": "Alerte du CERTA CERTA-2011-ALE-006 du 04 novembre 2011 :",
"url": "http://www.certa.ssi.gouv.fr/site/CERTA-2011-ALE-006"
}
],
"reference": "CERTA-2011-AVI-684",
"revisions": [
{
"description": "version initiale.",
"revision_date": "2011-12-14T00:00:00.000000"
}
],
"risks": [
{
"description": "Ex\u00e9cution de code arbitraire \u00e0 distance"
},
{
"description": "\u00c9l\u00e9vation de privil\u00e8ges"
}
],
"summary": "Une vuln\u00e9rabilit\u00e9 dans la gestion des polices TrueType de Windows permet\n\u00e0 une personne malintentionn\u00e9e d\u0027ex\u00e9cuter du code arbitraire \u00e0 distance.\n",
"title": "Vuln\u00e9rabilit\u00e9 dans la gestion des polices TrueType sur Windows",
"vendor_advisories": [
{
"published_at": null,
"title": "Bulletin de s\u00e9curit\u00e9 Microsoft MS11-087 du 13 d\u00e9cembre 2011",
"url": "http://technet.microsoft.com/en-us/security/bulletin/MS11-087"
}
]
}
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.