CERTA-2008-ALE-010

Vulnerability from certfr_alerte - Published: 2008-07-09 - Updated: 2008-08-13

Une vulnérabilité dans Microsoft Word 2002 permet à une personne malintentionnée d'exécuter du code arbitraire à distance.

Description

Une vulnérabilité a été identifiée dans Microsoft Word 2002. Une personne malintentionnée peut exécuter du code arbitraire à distance en incitant une victime à ouvrir un document Word spécialement conçu.

Selon Microsoft, la vulnérabilité est actuellement exploitée.

Contournement provisoire

Les mesures suivantes sont recommandées :

  • utiliser une version plus récente de Microsoft Word ;
  • utiliser Word Viewer 2003 SP3 pour visionner et imprimer des fichiers Word ;
  • utiliser un logiciel alternatif tel que OpenOffice.org ;
  • n'ouvrir que des documents provenant de sources de confiance ;
  • utiliser un compte aux droits restreints.

Solution

Se référer au bulletin de sécurité MS08-042 de Microsoft pour l'obtention des correctifs (cf. section Documentation).

Ce dernier est détaillé dans l'avis CERTA-2008-AVI-403.

Microsoft Office Word 2002 Service Pack 3.

Impacted products
Vendor Product Description

Show details on source website

{
  "$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
  "affected_systems": [],
  "affected_systems_content": "\u003cP\u003eMicrosoft Office Word 2002 Service Pack 3.\u003c/P\u003e",
  "closed_at": "2008-08-13",
  "content": "## Description\n\nUne vuln\u00e9rabilit\u00e9 a \u00e9t\u00e9 identifi\u00e9e dans Microsoft Word 2002. Une\npersonne malintentionn\u00e9e peut ex\u00e9cuter du code arbitraire \u00e0 distance en\nincitant une victime \u00e0 ouvrir un document Word sp\u00e9cialement con\u00e7u.\n\nSelon Microsoft, la vuln\u00e9rabilit\u00e9 est actuellement exploit\u00e9e.\n\n## Contournement provisoire\n\nLes mesures suivantes sont recommand\u00e9es :\n\n-   utiliser une version plus r\u00e9cente de Microsoft Word ;\n-   utiliser Word Viewer 2003 SP3 pour visionner et imprimer des\n    fichiers Word ;\n-   utiliser un logiciel alternatif tel que OpenOffice.org ;\n-   n\u0027ouvrir que des documents provenant de sources de confiance ;\n-   utiliser un compte aux droits restreints.\n\n## Solution\n\nSe r\u00e9f\u00e9rer au bulletin de s\u00e9curit\u00e9 MS08-042 de Microsoft pour\nl\u0027obtention des correctifs (cf. section Documentation).\n\nCe dernier est d\u00e9taill\u00e9 dans l\u0027avis CERTA-2008-AVI-403.\n",
  "cves": [
    {
      "name": "CVE-2008-2244",
      "url": "https://www.cve.org/CVERecord?id=CVE-2008-2244"
    }
  ],
  "initial_release_date": "2008-07-09T00:00:00",
  "last_revision_date": "2008-08-13T00:00:00",
  "links": [
    {
      "title": "Avis du CERTA CERTA-2008-AVI-403 du 13 ao\u00fbt 2008 :",
      "url": "http://www.certa.ssi.gouv.fr/site/CERTA-2008-AVI-403/"
    }
  ],
  "reference": "CERTA-2008-ALE-010",
  "revisions": [
    {
      "description": "version initiale.",
      "revision_date": "2008-07-09T00:00:00.000000"
    },
    {
      "description": "publication du correctif par Microsoft.",
      "revision_date": "2008-08-13T00:00:00.000000"
    }
  ],
  "risks": [
    {
      "description": "Ex\u00e9cution de code arbitraire \u00e0 distance"
    }
  ],
  "summary": "Une vuln\u00e9rabilit\u00e9 dans Microsoft Word 2002 permet \u00e0 une personne\nmalintentionn\u00e9e d\u0027ex\u00e9cuter du code arbitraire \u00e0 distance.\n",
  "title": "Vuln\u00e9rabilit\u00e9 dans Microsoft Word",
  "vendor_advisories": [
    {
      "published_at": null,
      "title": "Bulletin de s\u00e9curit\u00e9 Microsoft 953635 du 08 juillet 2008",
      "url": "http://www.microsoft.com/technet/security/advisory/953635.mspx"
    }
  ]
}



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.