CERTA-2007-AVI-535
Vulnerability from certfr_avis - Published: 2007-12-12 - Updated: 2007-12-12
Deux vulnérabilités concernant DirectX permettent à une personne malintentionnée d'exécuter du code arbitraire à distance.
Description
Deux vulnérabilités ont été identifiées dans Microsoft DirectX :
- la première faille concerne le traitement de fichiers SAMI (Synchronized Accessible Media Interchange) et permet l'exécution de code arbitraire à distance si un utilisateur ouvre un fichier spécialement construit ;
- la deuxième vulnérabilité est une erreur dans le traitement de fichiers WAV et AVI. Une personne malintentionnée pourrait ainsi exécuter du code arbitraire à distance en incitant un utilisateur à visiter un site web ou à ouvrir un courrier électronique spécialement conçu.
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 | DirectX 7.0 sur Microsoft Windows 2000 Service Pack 4 ; | ||
| Microsoft | Windows | DirectX 9.0c sur Windows XP Professionnel Édition x64 et Windows XP Professionnel Édition x64 Service Pack 2 ; | ||
| Microsoft | Windows | DirectX 8.1 sur Microsoft Windows 2000 Service Pack 4 ; | ||
| Microsoft | Windows | DirectX 10.0 sur Windows Vista ; | ||
| Microsoft | Windows | DirectX 9.0c sur Windows Server 2003 Service Pack 1 et Windows Server 2003 Service Pack 2 ; | ||
| Microsoft | Windows | DirectX 9.0c sur Microsoft Windows 2000 Service Pack 4 ; | ||
| Microsoft | Windows | DirectX 9.0c sur Microsoft Windows XP Service Pack 2 ; | ||
| Microsoft | Windows | DirectX 9.0c sur Windows Server 2003 Édition x64 et Windows Server 2003 Édition x64 Service Pack 2 ; | ||
| Microsoft | Windows | DirectX 9.0c sur Windows Server 2003 avec SP1 pour les systèmes Itanium et Windows Server 2003 avec SP2 pour les systèmes Itanium ; | ||
| Microsoft | Windows | DirectX 10.0 sur Windows Vista Édition x64. |
| Title | Publication Time | Tags | |||
|---|---|---|---|---|---|
|
|||||
{
"$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
"affected_systems": [
{
"description": "DirectX 7.0 sur Microsoft Windows 2000 Service Pack 4 ;",
"product": {
"name": "Windows",
"vendor": {
"name": "Microsoft",
"scada": false
}
}
},
{
"description": "DirectX 9.0c sur Windows XP Professionnel \u00c9dition x64 et Windows XP Professionnel \u00c9dition x64 Service Pack 2 ;",
"product": {
"name": "Windows",
"vendor": {
"name": "Microsoft",
"scada": false
}
}
},
{
"description": "DirectX 8.1 sur Microsoft Windows 2000 Service Pack 4 ;",
"product": {
"name": "Windows",
"vendor": {
"name": "Microsoft",
"scada": false
}
}
},
{
"description": "DirectX 10.0 sur Windows Vista ;",
"product": {
"name": "Windows",
"vendor": {
"name": "Microsoft",
"scada": false
}
}
},
{
"description": "DirectX 9.0c sur Windows Server 2003 Service Pack 1 et Windows Server 2003 Service Pack 2 ;",
"product": {
"name": "Windows",
"vendor": {
"name": "Microsoft",
"scada": false
}
}
},
{
"description": "DirectX 9.0c sur Microsoft Windows 2000 Service Pack 4 ;",
"product": {
"name": "Windows",
"vendor": {
"name": "Microsoft",
"scada": false
}
}
},
{
"description": "DirectX 9.0c sur Microsoft Windows XP Service Pack 2 ;",
"product": {
"name": "Windows",
"vendor": {
"name": "Microsoft",
"scada": false
}
}
},
{
"description": "DirectX 9.0c sur Windows Server 2003 \u00c9dition x64 et Windows Server 2003 \u00c9dition x64 Service Pack 2 ;",
"product": {
"name": "Windows",
"vendor": {
"name": "Microsoft",
"scada": false
}
}
},
{
"description": "DirectX 9.0c sur Windows Server 2003 avec SP1 pour les syst\u00e8mes Itanium et Windows Server 2003 avec SP2 pour les syst\u00e8mes Itanium ;",
"product": {
"name": "Windows",
"vendor": {
"name": "Microsoft",
"scada": false
}
}
},
{
"description": "DirectX 10.0 sur Windows Vista \u00c9dition x64.",
"product": {
"name": "Windows",
"vendor": {
"name": "Microsoft",
"scada": false
}
}
}
],
"affected_systems_content": null,
"content": "## Description\n\nDeux vuln\u00e9rabilit\u00e9s ont \u00e9t\u00e9 identifi\u00e9es dans Microsoft DirectX :\n\n- la premi\u00e8re faille concerne le traitement de fichiers SAMI\n (Synchronized Accessible Media Interchange) et permet l\u0027ex\u00e9cution de\n code arbitraire \u00e0 distance si un utilisateur ouvre un fichier\n sp\u00e9cialement construit ;\n- la deuxi\u00e8me vuln\u00e9rabilit\u00e9 est une erreur dans le traitement de\n fichiers WAV et AVI. Une personne malintentionn\u00e9e pourrait ainsi\n ex\u00e9cuter du code arbitraire \u00e0 distance en incitant un utilisateur \u00e0\n visiter un site web ou \u00e0 ouvrir un courrier \u00e9lectronique\n sp\u00e9cialement con\u00e7u.\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-2007-3895",
"url": "https://www.cve.org/CVERecord?id=CVE-2007-3895"
},
{
"name": "CVE-2007-3901",
"url": "https://www.cve.org/CVERecord?id=CVE-2007-3901"
}
],
"initial_release_date": "2007-12-12T00:00:00",
"last_revision_date": "2007-12-12T00:00:00",
"links": [],
"reference": "CERTA-2007-AVI-535",
"revisions": [
{
"description": "version initiale.",
"revision_date": "2007-12-12T00:00:00.000000"
}
],
"risks": [
{
"description": "Ex\u00e9cution de code arbitraire \u00e0 distance"
}
],
"summary": "Deux vuln\u00e9rabilit\u00e9s concernant DirectX permettent \u00e0 une personne\nmalintentionn\u00e9e d\u0027ex\u00e9cuter du code arbitraire \u00e0 distance.\n",
"title": "Vuln\u00e9rabilit\u00e9s dans Microsoft DirectX",
"vendor_advisories": [
{
"published_at": null,
"title": "Bulletin de s\u00e9curit\u00e9 Microsoft MS07-064 du 11 d\u00e9cembre 2007",
"url": "http://www.microsoft.com/technet/security/Bulletin/MS07-064.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.