CERTA-2007-AVI-081
Vulnerability from certfr_avis - Published: 2007-02-14 - Updated: 2007-02-14None
Description
Une vulnérabilité, de type débordement d'entier, a été identifiée dans le moteur de protection contre les codes malveillants (mpengine.dll) fourni avec certaines applications de sécurité Microsoft. Celle-ci se produirait au cours de l'analyse de documents au format PDF (pour Portable Document Format).
Une personne malveillante pourrait construire un fichier d'extension .pdf exploitant cette vulnérabilité. Si une personne récupère ce dernier (soit en le téléchargeant via une page Web, soit comme pièce jointe d'un courrier électronique par exemple), du code malveillant pourrait être exécuté lorsque l'antivirus de Mirosoft analyserait le fichier.
Solution
Se référer au bulletin de sécurité MS07-010 de l'éditeur pour l'obtention des correctifs (cf. section Documentation).
None| Vendor | Product | Description | ||
|---|---|---|---|---|
| Microsoft | Windows | Microsoft Windows Defender x64 Edition ; | ||
| Microsoft | Windows | Microsoft Antigen pour SMTP Gateway 9.x ; | ||
| Microsoft | Windows | Microsoft Windows Defender ; | ||
| Microsoft | Windows | Microsoft Antigen pour Exchange 9.x ; | ||
| Microsoft | Windows | Microsoft Forefront Security pour SharePoint. | ||
| Microsoft | Windows | Microsoft Forefront Security pour Exchange Server ; | ||
| Microsoft | Windows | Windows Live OneCare ; | ||
| Microsoft | Windows | Microsoft Windows Defender pour Windows Vista ; |
| Title | Publication Time | Tags | |||
|---|---|---|---|---|---|
|
|||||
{
"$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
"affected_systems": [
{
"description": "Microsoft Windows Defender x64 Edition ;",
"product": {
"name": "Windows",
"vendor": {
"name": "Microsoft",
"scada": false
}
}
},
{
"description": "Microsoft Antigen pour SMTP Gateway 9.x ;",
"product": {
"name": "Windows",
"vendor": {
"name": "Microsoft",
"scada": false
}
}
},
{
"description": "Microsoft Windows Defender ;",
"product": {
"name": "Windows",
"vendor": {
"name": "Microsoft",
"scada": false
}
}
},
{
"description": "Microsoft Antigen pour Exchange 9.x ;",
"product": {
"name": "Windows",
"vendor": {
"name": "Microsoft",
"scada": false
}
}
},
{
"description": "Microsoft Forefront Security pour SharePoint.",
"product": {
"name": "Windows",
"vendor": {
"name": "Microsoft",
"scada": false
}
}
},
{
"description": "Microsoft Forefront Security pour Exchange Server ;",
"product": {
"name": "Windows",
"vendor": {
"name": "Microsoft",
"scada": false
}
}
},
{
"description": "Windows Live OneCare ;",
"product": {
"name": "Windows",
"vendor": {
"name": "Microsoft",
"scada": false
}
}
},
{
"description": "Microsoft Windows Defender pour Windows Vista ;",
"product": {
"name": "Windows",
"vendor": {
"name": "Microsoft",
"scada": false
}
}
}
],
"affected_systems_content": null,
"content": "## Description\n\nUne vuln\u00e9rabilit\u00e9, de type d\u00e9bordement d\u0027entier, a \u00e9t\u00e9 identifi\u00e9e dans\nle moteur de protection contre les codes malveillants (mpengine.dll)\nfourni avec certaines applications de s\u00e9curit\u00e9 Microsoft. Celle-ci se\nproduirait au cours de l\u0027analyse de documents au format PDF (pour\nPortable Document Format).\n\nUne personne malveillante pourrait construire un fichier d\u0027extension\n.pdf exploitant cette vuln\u00e9rabilit\u00e9. Si une personne r\u00e9cup\u00e8re ce dernier\n(soit en le t\u00e9l\u00e9chargeant via une page Web, soit comme pi\u00e8ce jointe d\u0027un\ncourrier \u00e9lectronique par exemple), du code malveillant pourrait \u00eatre\nex\u00e9cut\u00e9 lorsque l\u0027antivirus de Mirosoft analyserait le fichier.\n\n## Solution\n\nSe r\u00e9f\u00e9rer au bulletin de s\u00e9curit\u00e9 MS07-010 de l\u0027\u00e9diteur pour\nl\u0027obtention des correctifs (cf. section Documentation).\n",
"cves": [
{
"name": "CVE-2006-5270",
"url": "https://www.cve.org/CVERecord?id=CVE-2006-5270"
}
],
"initial_release_date": "2007-02-14T00:00:00",
"last_revision_date": "2007-02-14T00:00:00",
"links": [],
"reference": "CERTA-2007-AVI-081",
"revisions": [
{
"description": "version initiale.",
"revision_date": "2007-02-14T00:00:00.000000"
}
],
"risks": [
{
"description": "Ex\u00e9cution de code arbitraire \u00e0 distance"
},
{
"description": "Contournement de la politique de s\u00e9curit\u00e9"
}
],
"summary": null,
"title": "Vuln\u00e9rabilit\u00e9 du moteur de protection mpengine.dll de Microsoft Windows",
"vendor_advisories": [
{
"published_at": null,
"title": "Bulletin de s\u00e9curit\u00e9 Microsoft MS07-010 du 13 f\u00e9vrier 2007",
"url": "http://www.microsoft.com/technet/security/Bulletin/MS07-010.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.