CERTA-2010-AVI-142
Vulnerability from certfr_avis - Published: 2010-03-30 - Updated: 2010-03-30
Plusieurs vulnérabilités présentes dans IBM WebSphere permettent à un utilisateur malveillant d'accéder à des données, de provoquer un déni de service à distance ou de réaliser de l'injection de code indirecte.
Description
Plusieurs vulnérabilités affectant IBM WebSphere ont été publiées :
- (CVE-2010-0768) dans la console d'administration, un manque de vérification des données entrées est exploitable par un utilisateur malveillant pour réaliser de l'injection de code indirecte ;
- (CVE-2010-0769) un défaut dans WebSphere Application Server permet à un utilisateur distant authentifié de lire des mots de passe non chiffrés ;
- (CVE-2010-0770) une erreur dans le traitement des sessions SSL avec un client ORB (Object Request Broker) permet à un utilisateur distant authentifié de provoquer un déni de service par attente infinie du serveur.
Solution
Les versions 6.0.2.41, 6.1.0.31 et 7.0.0.9 d'IBM WebSphere remédient à 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.0.x, 6.1.x et 6.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 7.0.x, 6.1.x et 6.0.x.\u003c/p\u003e",
"content": "## Description\n\nPlusieurs vuln\u00e9rabilit\u00e9s affectant IBM WebSphere ont \u00e9t\u00e9 publi\u00e9es\u00a0:\n\n- (CVE-2010-0768) dans la console d\u0027administration, un manque de\n v\u00e9rification des donn\u00e9es entr\u00e9es est exploitable par un utilisateur\n malveillant pour r\u00e9aliser de l\u0027injection de code indirecte\u00a0;\n- (CVE-2010-0769) un d\u00e9faut dans WebSphere Application Server permet \u00e0\n un utilisateur distant authentifi\u00e9 de lire des mots de passe non\n chiffr\u00e9s\u00a0;\n- (CVE-2010-0770) une erreur dans le traitement des sessions SSL avec\n un client ORB (Object Request Broker) permet \u00e0 un utilisateur\n distant authentifi\u00e9 de provoquer un d\u00e9ni de service par attente\n infinie du serveur.\n\n## Solution\n\nLes versions 6.0.2.41, 6.1.0.31 et 7.0.0.9 d\u0027IBM WebSphere rem\u00e9dient \u00e0\nces vuln\u00e9rabilit\u00e9s. Se r\u00e9f\u00e9rer au bulletin de s\u00e9curit\u00e9 de l\u0027\u00e9diteur pour\nl\u0027obtention des correctifs (cf. section Documentation).\n",
"cves": [
{
"name": "CVE-2010-0768",
"url": "https://www.cve.org/CVERecord?id=CVE-2010-0768"
},
{
"name": "CVE-2010-0770",
"url": "https://www.cve.org/CVERecord?id=CVE-2010-0770"
},
{
"name": "CVE-2010-0769",
"url": "https://www.cve.org/CVERecord?id=CVE-2010-0769"
}
],
"initial_release_date": "2010-03-30T00:00:00",
"last_revision_date": "2010-03-30T00:00:00",
"links": [],
"reference": "CERTA-2010-AVI-142",
"revisions": [
{
"description": "version initiale.",
"revision_date": "2010-03-30T00:00:00.000000"
}
],
"risks": [
{
"description": "D\u00e9ni de service \u00e0 distance"
},
{
"description": "Injection de code indirecte \u00e0 distance"
},
{
"description": "Atteinte \u00e0 la confidentialit\u00e9 des donn\u00e9es"
}
],
"summary": "Plusieurs vuln\u00e9rabilit\u00e9s pr\u00e9sentes dans IBM WebSphere permettent \u00e0 un\nutilisateur malveillant d\u0027acc\u00e9der \u00e0 des donn\u00e9es, de provoquer un d\u00e9ni de\nservice \u00e0 distance ou de r\u00e9aliser de l\u0027injection de code indirecte.\n",
"title": "Vuln\u00e9rabilit\u00e9s dans IBM WebSphere",
"vendor_advisories": [
{
"published_at": null,
"title": "Bulletin de s\u00e9curit\u00e9 IBM swg27004980 du 29 mars 2010",
"url": "http://www-01.ibm.com/support/docview.wss?uid=swg27004980"
}
]
}
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.