CERTA-2009-AVI-369
Vulnerability from certfr_avis - Published: 2009-09-09 - Updated: 2009-09-09
Une vulnérablité dans Microsoft JScript permet à un utilisateur malintentionné distant de provoquer un déni de service ou d'exécuter du code arbitraire.
Description
Microsoft JScript est le moteur de rendu de contenu Javascript propre au système d'exploitation Microsoft Windows et à son navigateur Internet Explorer.
Une vulnérabilité dans ce composant a été identifiée et permet à un utilisateur distant malintentionné de provoquer un déni de service ou d'exécuter du code arbitraire par le biais d'une page web contenant du code Javascript particulier.
Solution
Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation).
- JScript versions 5.1 ;
- JScript versions 5.6 ;
- JScript versions 5.7 ;
- JScript versions 5.8.
NB: l'impact de la vulnérabilité peut varier en fonction de la version du système d'exploitation et du navigateur Internet Explorer utilisé. Veuillez vous reporter au bulletin de sécurité de l'éditeur pour plus de détails.
| Vendor | Product | Description |
|---|
| Title | Publication Time | Tags | |
|---|---|---|---|
{
"$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
"affected_systems": [],
"affected_systems_content": "\u003cUL\u003e \u003cLI\u003eJScript versions 5.1 ;\u003c/LI\u003e \u003cLI\u003eJScript versions 5.6 ;\u003c/LI\u003e \u003cLI\u003eJScript versions 5.7 ;\u003c/LI\u003e \u003cLI\u003eJScript versions 5.8.\u003c/LI\u003e \u003c/UL\u003e \u003cP\u003eNB: l\u0027impact de la vuln\u00e9rabilit\u00e9 peut varier en fonction de la version du syst\u00e8me d\u0027exploitation et du navigateur \u003cTT\u003eInternet Explorer\u003c/TT\u003e utilis\u00e9. Veuillez vous reporter au bulletin de s\u00e9curit\u00e9 de l\u0027\u00e9diteur pour plus de d\u00e9tails.\u003c/P\u003e",
"content": "## Description\n\nMicrosoft JScript est le moteur de rendu de contenu Javascript propre au\nsyst\u00e8me d\u0027exploitation Microsoft Windows et \u00e0 son navigateur Internet\nExplorer.\n\nUne vuln\u00e9rabilit\u00e9 dans ce composant a \u00e9t\u00e9 identifi\u00e9e et permet \u00e0 un\nutilisateur distant malintentionn\u00e9 de provoquer un d\u00e9ni de service ou\nd\u0027ex\u00e9cuter du code arbitraire par le biais d\u0027une page web contenant du\ncode Javascript particulier.\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-2009-1920",
"url": "https://www.cve.org/CVERecord?id=CVE-2009-1920"
}
],
"initial_release_date": "2009-09-09T00:00:00",
"last_revision_date": "2009-09-09T00:00:00",
"links": [
{
"title": "Bulletin de s\u00e9curit\u00e9 Microsoft MS09-045 du 08 septembre 2009 :",
"url": "http://www.microsoft.com/technet/security/Bulletin/MS09-045.mspx"
},
{
"title": "Bulletin de s\u00e9curit\u00e9 Microsoft MS09-045 du 08 septembre 2009 :",
"url": "http://www.microsoft.com/france/technet/security/Bulletin/MS09-045.mspx"
}
],
"reference": "CERTA-2009-AVI-369",
"revisions": [
{
"description": "version initiale.",
"revision_date": "2009-09-09T00:00:00.000000"
}
],
"risks": [
{
"description": "D\u00e9ni de service \u00e0 distance"
},
{
"description": "Ex\u00e9cution de code arbitraire \u00e0 distance"
}
],
"summary": "Une vuln\u00e9rablit\u00e9 dans Microsoft JScript permet \u00e0 un utilisateur\nmalintentionn\u00e9 distant de provoquer un d\u00e9ni de service ou d\u0027ex\u00e9cuter du\ncode arbitraire.\n",
"title": "Vuln\u00e9rabilit\u00e9 de Microsoft JScript",
"vendor_advisories": [
{
"published_at": null,
"title": "Bulletin de s\u00e9curit\u00e9 Microsoft MS09-045 du 08 septembre 2009",
"url": null
}
]
}
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.