CERTA-2010-AVI-225
Vulnerability from certfr_avis - Published: 2010-05-21 - Updated: 2010-05-21
Plusieurs vulnérabilités dans IBM WebSphere Application Server permettent de réaliser un déni de service à distance et d'accéder indûment à des fichiers.
Description
Plusieurs vulnérabilités ont été découvertes dans IBM WebSphere Application Server :
- par le biais d'une requête spécifiquement constituée, il est possible de provoquer un déni de service à distance (CVE-2010-0775) ;
- le composant Web Container ne gère pas correctement certaines requêtes GET, ce qui permet de réaliser un déni de service à distance (CVE-2010-0776) ;
- une erreur lors de la gestion, par le composant Web Container, des fichiers dont la longueur du nom est supérieure à 20 caractères provoque le renvoi d'un autre fichier (CVE-2010-0777).
Solution
Se référer aux bulletins de sécurité d'ISS X-Force (cf. section Documentation).
IBM WebSphere Application Server versions 6.0, 6.1 et 7.0.
| Vendor | Product | Description |
|---|
| Title | Publication Time | Tags | |
|---|---|---|---|
{
"$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
"affected_systems": [],
"affected_systems_content": "\u003cP\u003e\u003cSPAN class=\"textit\"\u003eIBM WebSphere Application Server\u003c/SPAN\u003e versions 6.0, 6.1 et 7.0.\u003c/P\u003e",
"content": "## Description\n\nPlusieurs vuln\u00e9rabilit\u00e9s ont \u00e9t\u00e9 d\u00e9couvertes dans IBM WebSphere\nApplication Server :\n\n- par le biais d\u0027une requ\u00eate sp\u00e9cifiquement constitu\u00e9e, il est\n possible de provoquer un d\u00e9ni de service \u00e0 distance (CVE-2010-0775)\n ;\n- le composant Web Container ne g\u00e8re pas correctement certaines\n requ\u00eates GET, ce qui permet de r\u00e9aliser un d\u00e9ni de service \u00e0\n distance (CVE-2010-0776) ;\n- une erreur lors de la gestion, par le composant Web Container, des\n fichiers dont la longueur du nom est sup\u00e9rieure \u00e0 20 caract\u00e8res\n provoque le renvoi d\u0027un autre fichier (CVE-2010-0777).\n\n## Solution\n\nSe r\u00e9f\u00e9rer aux bulletins de s\u00e9curit\u00e9 d\u0027ISS X-Force (cf. section\nDocumentation).\n",
"cves": [
{
"name": "CVE-2010-0775",
"url": "https://www.cve.org/CVERecord?id=CVE-2010-0775"
},
{
"name": "CVE-2010-0777",
"url": "https://www.cve.org/CVERecord?id=CVE-2010-0777"
},
{
"name": "CVE-2010-0776",
"url": "https://www.cve.org/CVERecord?id=CVE-2010-0776"
}
],
"initial_release_date": "2010-05-21T00:00:00",
"last_revision_date": "2010-05-21T00:00:00",
"links": [
{
"title": "Bulletins de s\u00e9curit\u00e9 d\u0027ISS X-Force du 11 mai 2010 :",
"url": "http://xforce.iss.net/xforce/xfdb/58556"
},
{
"title": "Bulletins de s\u00e9curit\u00e9 d\u0027ISS X-Force du 11 mai 2010 :",
"url": "http://xforce.iss.net/xforce/xfdb/58555"
},
{
"title": "Bulletins de s\u00e9curit\u00e9 d\u0027ISS X-Force du 11 mai 2010 :",
"url": "http://xforce.iss.net/xforce/xfdb/58557"
}
],
"reference": "CERTA-2010-AVI-225",
"revisions": [
{
"description": "version initiale.",
"revision_date": "2010-05-21T00:00:00.000000"
}
],
"risks": [
{
"description": "D\u00e9ni de service \u00e0 distance"
},
{
"description": "Atteinte \u00e0 la confidentialit\u00e9 des donn\u00e9es"
}
],
"summary": "Plusieurs vuln\u00e9rabilit\u00e9s dans \u003cspan class=\"textit\"\u003eIBM WebSphere\nApplication Server\u003c/span\u003e permettent de r\u00e9aliser un d\u00e9ni de service \u00e0\ndistance et d\u0027acc\u00e9der ind\u00fbment \u00e0 des fichiers.\n",
"title": "Vuln\u00e9rabilit\u00e9s dans IBM WebSphere Application Server",
"vendor_advisories": [
{
"published_at": null,
"title": "Bulletins de s\u00e9curit\u00e9 ISS X-Force du 11 mai 2010",
"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.