CERTA-2009-AVI-126
Vulnerability from certfr_avis - Published: 2009-04-01 - Updated: 2009-04-01
Plusieurs vulnérabilités présentes dans IBM WebSphere permettent à un utilisateur malveillant de contourner la politique de sécurité ou d'exécuter du code arbitraire à distance.
Description
Plusieurs vulnérabilités sont présentes dans IBM WebSphere :
- la première, dans la console d'administration, permet de réaliser de l'injection de code indirecte (XSS) ;
- un correctif intermédiaire positionne des droits d'accès à des fichiers de manière incorrecte, donnant accès en exécution à tout utilisateur ;
- une erreur non précisée permet de voler la session d'un utilisateur ;
- une erreur non précisée est présente dans la définition des signature numériques XML.
Solution
Le correctif 7.0.0.3 remédie à ces vulnérabilités.
Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation).
IBM WebSphere 7.x.
| Vendor | Product | Description |
|---|
| Title | Publication Time | Tags | |||
|---|---|---|---|---|---|
|
|||||
{
"$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
"affected_systems": [],
"affected_systems_content": "\u003cp\u003eIBM WebSphere 7.x.\u003c/p\u003e",
"content": "## Description\n\nPlusieurs vuln\u00e9rabilit\u00e9s sont pr\u00e9sentes dans IBM WebSphere :\n\n- la premi\u00e8re, dans la console d\u0027administration, permet de r\u00e9aliser de\n l\u0027injection de code indirecte (XSS) ;\n- un correctif interm\u00e9diaire positionne des droits d\u0027acc\u00e8s \u00e0 des\n fichiers de mani\u00e8re incorrecte, donnant acc\u00e8s en ex\u00e9cution \u00e0 tout\n utilisateur ;\n- une erreur non pr\u00e9cis\u00e9e permet de voler la session d\u0027un utilisateur\n ;\n- une erreur non pr\u00e9cis\u00e9e est pr\u00e9sente dans la d\u00e9finition des\n signature num\u00e9riques XML.\n\n## Solution\n\nLe correctif 7.0.0.3 rem\u00e9die \u00e0 ces vuln\u00e9rabilit\u00e9s.\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-1174",
"url": "https://www.cve.org/CVERecord?id=CVE-2009-1174"
},
{
"name": "CVE-2009-0892",
"url": "https://www.cve.org/CVERecord?id=CVE-2009-0892"
},
{
"name": "CVE-2009-1173",
"url": "https://www.cve.org/CVERecord?id=CVE-2009-1173"
}
],
"initial_release_date": "2009-04-01T00:00:00",
"last_revision_date": "2009-04-01T00:00:00",
"links": [],
"reference": "CERTA-2009-AVI-126",
"revisions": [
{
"description": "version initiale.",
"revision_date": "2009-04-01T00:00:00.000000"
}
],
"risks": [
{
"description": "Ex\u00e9cution de code arbitraire \u00e0 distance"
},
{
"description": "Contournement de la politique de s\u00e9curit\u00e9"
}
],
"summary": "Plusieurs vuln\u00e9rabilit\u00e9s pr\u00e9sentes dans IBM WebSphere permettent \u00e0 un\nutilisateur malveillant de contourner la politique de s\u00e9curit\u00e9 ou\nd\u0027ex\u00e9cuter du code arbitraire \u00e0 distance.\n",
"title": "Vuln\u00e9rabilit\u00e9s de IBM WebSphere",
"vendor_advisories": [
{
"published_at": null,
"title": "Bulletin de s\u00e9curit\u00e9 IBM swg24022549 du 26 mars 2009",
"url": "http://www-01.ibm.com/support/docview.wss?uid=swg24022549"
}
]
}
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.