CERTA-2010-AVI-289
Vulnerability from certfr_avis - Published: 2010-06-25 - Updated: 2010-06-25
Deux vulnérabilités présentes dans IBM WebSphere permettent à un utilisateur malveillant de réaliser de l'injection de code indirecte (XSS).
Description
Deux vulnérabilités dans la console d'administration d'IBM WebSphere permettent à un utilisateur malveillant de réaliser de l'injection de code indirecte.
Solution
Les versions 6.0.2.43, 6.1.0.33 et 7.0.0.11 résolvent ces problèmes.
Se référer aux bulletins de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation).
IBM WebSphere 6.0.x, 6.1.x, 7.0.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 6.0.x, 6.1.x, 7.0.x.\u003c/p\u003e",
"content": "## Description\n\nDeux vuln\u00e9rabilit\u00e9s dans la console d\u0027administration d\u0027IBM WebSphere\npermettent \u00e0 un utilisateur malveillant de r\u00e9aliser de l\u0027injection de\ncode indirecte.\n\n## Solution\n\nLes versions 6.0.2.43, 6.1.0.33 et 7.0.0.11 r\u00e9solvent ces probl\u00e8mes.\n\nSe r\u00e9f\u00e9rer aux bulletins de s\u00e9curit\u00e9 de l\u0027\u00e9diteur pour l\u0027obtention des\ncorrectifs (cf. section Documentation).\n",
"cves": [
{
"name": "CVE-2010-0778",
"url": "https://www.cve.org/CVERecord?id=CVE-2010-0778"
},
{
"name": "CVE-2010-0779",
"url": "https://www.cve.org/CVERecord?id=CVE-2010-0779"
}
],
"initial_release_date": "2010-06-25T00:00:00",
"last_revision_date": "2010-06-25T00:00:00",
"links": [],
"reference": "CERTA-2010-AVI-289",
"revisions": [
{
"description": "version initiale.",
"revision_date": "2010-06-25T00:00:00.000000"
}
],
"risks": [
{
"description": "Injection de code indirecte \u00e0 distance"
}
],
"summary": "Deux vuln\u00e9rabilit\u00e9s pr\u00e9sentes dans IBM WebSphere permettent \u00e0 un\nutilisateur malveillant de r\u00e9aliser de l\u0027injection de code indirecte\n(XSS).\n",
"title": "Vuln\u00e9rabilit\u00e9s dans IBM WebSphere",
"vendor_advisories": [
{
"published_at": null,
"title": "Bulletins de s\u00e9curit\u00e9 IBM ISS X-Force 59646 et 59647",
"url": "http://xforce.iss.net/xforce/xfdb/59647"
}
]
}
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.