CERTA-2006-AVI-149

Vulnerability from certfr_avis - Published: 2006-04-12 - Updated: 2006-04-12

Une vulnérabilité dans Microsoft Outlook Express peut être utilisée par un utilisateur malveillant pour exécuter du code arbitraire à distance.

Description

L'application de messagerie Microsoft Outlook Express ne manipule pas correctement les fichiers dédiés au carnet d'adresse, au format .wab (pour Windows Address Book). Un utilisateur malveillant peut conduire l'utilisateur à manipuler de tels fichiers (envoi en pièce jointe d'un courriel par exemple), et profiter de cette vulnérabilité pour exécuter du code arbitraire à distance.

Solution

Appliquer le correctif tel qu'indiqué dans le bulletin de sécurité Microsoft MS06-016 (cf. section Documentation).

None
Impacted products
Vendor Product Description
Microsoft Windows Microsoft Outlook Express 6 Service Pack 1 pour Microsoft Windows 2000 Service Pack 4 ou Windows XP Service Pack 1 ;
Microsoft Windows Microsoft Outlook Express 6 pour Microsoft Windows Server 2003 ou pour Windows Server 2003 Service Pack 1 (incluant la version 64-bit Edition).
Microsoft Windows Microsoft Outlook Express 5.5 Service Pack 2 pour Microsoft Windows 2000 Service Pack 4 ;
Microsoft Windows Microsoft Outlook Express 6 pour Microsoft Windows XP Service Pack 2 (incluant la version 64-bit Edition) ;

Show details on source website

{
  "$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
  "affected_systems": [
    {
      "description": "Microsoft Outlook Express 6 Service Pack 1 pour Microsoft Windows 2000 Service Pack 4 ou Windows XP Service Pack 1 ;",
      "product": {
        "name": "Windows",
        "vendor": {
          "name": "Microsoft",
          "scada": false
        }
      }
    },
    {
      "description": "Microsoft Outlook Express 6 pour Microsoft Windows Server 2003 ou pour Windows Server 2003 Service Pack 1 (incluant la version 64-bit Edition).",
      "product": {
        "name": "Windows",
        "vendor": {
          "name": "Microsoft",
          "scada": false
        }
      }
    },
    {
      "description": "Microsoft Outlook Express 5.5 Service Pack 2 pour Microsoft Windows 2000 Service Pack 4 ;",
      "product": {
        "name": "Windows",
        "vendor": {
          "name": "Microsoft",
          "scada": false
        }
      }
    },
    {
      "description": "Microsoft Outlook Express 6 pour Microsoft Windows XP Service Pack 2 (incluant la version 64-bit Edition) ;",
      "product": {
        "name": "Windows",
        "vendor": {
          "name": "Microsoft",
          "scada": false
        }
      }
    }
  ],
  "affected_systems_content": null,
  "content": "## Description\n\nL\u0027application de messagerie Microsoft Outlook Express ne manipule pas\ncorrectement les fichiers d\u00e9di\u00e9s au carnet d\u0027adresse, au format .wab\n(pour Windows Address Book). Un utilisateur malveillant peut conduire\nl\u0027utilisateur \u00e0 manipuler de tels fichiers (envoi en pi\u00e8ce jointe d\u0027un\ncourriel par exemple), et profiter de cette vuln\u00e9rabilit\u00e9 pour ex\u00e9cuter\ndu code arbitraire \u00e0 distance.\n\n## Solution\n\nAppliquer le correctif tel qu\u0027indiqu\u00e9 dans le bulletin de s\u00e9curit\u00e9\nMicrosoft MS06-016 (cf. section Documentation).\n",
  "cves": [
    {
      "name": "CVE-2006-0014",
      "url": "https://www.cve.org/CVERecord?id=CVE-2006-0014"
    }
  ],
  "initial_release_date": "2006-04-12T00:00:00",
  "last_revision_date": "2006-04-12T00:00:00",
  "links": [
    {
      "title": "Bulletin de s\u00e9curit\u00e9 Microsoft MS06-016 du 11 avril 2006 :",
      "url": "http://www.microsoft.com/technet/security/Bulletin/MS06-016.mspx"
    },
    {
      "title": "Bulletin de s\u00e9curit\u00e9 Microsoft MS06-016 du 11 avril 2006 :",
      "url": "http://www.microsoft.com/france/technet/securite/MS06-016.mspx"
    }
  ],
  "reference": "CERTA-2006-AVI-149",
  "revisions": [
    {
      "description": "version initiale.",
      "revision_date": "2006-04-12T00:00:00.000000"
    }
  ],
  "risks": [
    {
      "description": "Ex\u00e9cution de code arbitraire \u00e0 distance"
    }
  ],
  "summary": "Une vuln\u00e9rabilit\u00e9 dans Microsoft Outlook Express peut \u00eatre utilis\u00e9e par\nun utilisateur malveillant pour ex\u00e9cuter du code arbitraire \u00e0 distance.\n",
  "title": "Vuln\u00e9rabilit\u00e9 dans Microsoft Outlook Express",
  "vendor_advisories": [
    {
      "published_at": null,
      "title": "Bulletin de s\u00e9curit\u00e9 MS06-016 de Microsoft",
      "url": null
    }
  ]
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

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.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

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

JSON
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.

Events included in the timeline

Loading timeline…


    Loading…

    Loading…

    Loading…

    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.