CERTA-2012-AVI-137
Vulnerability from certfr_avis - Published: 2012-03-14 - Updated: 2012-03-14
Une vulnérabilité dans Windows DirectWrite permet à un attaquant de réaliser un déni de service au moyen d'un message spécialement conçu.
Description
Un attaquant peut, au moyen d'une suite de caractères Unicode spécialement conçue, réaliser un déni de service à distance sur l'application Windows DirectWrite. Celle-ci devient alors bloquée.
Solution
Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation).
None| Vendor | Product | Description | ||
|---|---|---|---|---|
| Microsoft | Windows | Windows Vista Service Pack 2 ; | ||
| Microsoft | Windows | Windows Server 2008 version 32 bits SP2 (sauf installation Server Core) ; | ||
| Microsoft | Windows | Windows Server 2008 R2 Itanium ; | ||
| Microsoft | Windows | Windows Server 2008 R2 (sauf installation Server Core) ; | ||
| Microsoft | Windows | Windows Vista édition x64 Service Pack 2 ; | ||
| Microsoft | Windows | Windows 7 32 et bits Service Pack 1 ; | ||
| Microsoft | Windows | Windows Server 2008 R2 Service Pack 1 (sauf installation Server Core) ; | ||
| Microsoft | Windows | Windows Server 2008 édition x64 Service Pack 2 (sauf installation Server Core) ; | ||
| Microsoft | Windows | Windows Server 2008 R2 Itanium Service Pack 1. | ||
| Microsoft | Windows | Windows 7 32 et 64 bits ; |
| Title | Publication Time | Tags | |||
|---|---|---|---|---|---|
|
|||||
{
"$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
"affected_systems": [
{
"description": "Windows Vista Service Pack 2 ;",
"product": {
"name": "Windows",
"vendor": {
"name": "Microsoft",
"scada": false
}
}
},
{
"description": "Windows Server 2008 version 32 bits SP2 (sauf installation Server Core) ;",
"product": {
"name": "Windows",
"vendor": {
"name": "Microsoft",
"scada": false
}
}
},
{
"description": "Windows Server 2008 R2 Itanium ;",
"product": {
"name": "Windows",
"vendor": {
"name": "Microsoft",
"scada": false
}
}
},
{
"description": "Windows Server 2008 R2 (sauf installation Server Core) ;",
"product": {
"name": "Windows",
"vendor": {
"name": "Microsoft",
"scada": false
}
}
},
{
"description": "Windows Vista \u00e9dition x64 Service Pack 2 ;",
"product": {
"name": "Windows",
"vendor": {
"name": "Microsoft",
"scada": false
}
}
},
{
"description": "Windows 7 32 et bits Service Pack 1 ;",
"product": {
"name": "Windows",
"vendor": {
"name": "Microsoft",
"scada": false
}
}
},
{
"description": "Windows Server 2008 R2 Service Pack 1 (sauf installation Server Core) ;",
"product": {
"name": "Windows",
"vendor": {
"name": "Microsoft",
"scada": false
}
}
},
{
"description": "Windows Server 2008 \u00e9dition x64 Service Pack 2 (sauf installation Server Core) ;",
"product": {
"name": "Windows",
"vendor": {
"name": "Microsoft",
"scada": false
}
}
},
{
"description": "Windows Server 2008 R2 Itanium Service Pack 1.",
"product": {
"name": "Windows",
"vendor": {
"name": "Microsoft",
"scada": false
}
}
},
{
"description": "Windows 7 32 et 64 bits ;",
"product": {
"name": "Windows",
"vendor": {
"name": "Microsoft",
"scada": false
}
}
}
],
"affected_systems_content": null,
"content": "## Description\n\nUn attaquant peut, au moyen d\u0027une suite de caract\u00e8res Unicode\nsp\u00e9cialement con\u00e7ue, r\u00e9aliser un d\u00e9ni de service \u00e0 distance sur\nl\u0027application Windows DirectWrite. Celle-ci devient alors bloqu\u00e9e.\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-2012-0156",
"url": "https://www.cve.org/CVERecord?id=CVE-2012-0156"
}
],
"initial_release_date": "2012-03-14T00:00:00",
"last_revision_date": "2012-03-14T00:00:00",
"links": [],
"reference": "CERTA-2012-AVI-137",
"revisions": [
{
"description": "version initiale.",
"revision_date": "2012-03-14T00:00:00.000000"
}
],
"risks": [
{
"description": "D\u00e9ni de service \u00e0 distance"
}
],
"summary": "Une vuln\u00e9rabilit\u00e9 dans \u003cspan class=\"textit\"\u003eWindows DirectWrite\u003c/span\u003e\npermet \u00e0 un attaquant de r\u00e9aliser un d\u00e9ni de service au moyen d\u0027un\nmessage sp\u00e9cialement con\u00e7u.\n",
"title": "Vuln\u00e9rabilit\u00e9 dans Windows DirectWrite",
"vendor_advisories": [
{
"published_at": null,
"title": "Bulletin de s\u00e9curit\u00e9 Microsoft MS12-019 du 13 mars 2012",
"url": "http://technet.microsoft.com/en-us/security/bulletin/MS12-019"
}
]
}
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.