CERTA-2012-AVI-431
Vulnerability from certfr_avis - Published: 2012-08-14 - Updated: 2012-08-14
Des vulnérabilités ont été corrigées dans les produits IBM WebSphere. La première concerne un manque de contrôle d'accès dans IBM WebSphere MQ File Transfer Edition permettant à un utilisateur authentifié d'accéder aux transferts d'autres utilisateurs. La seconde concerne également le produit IBM WebSphere MQ Managed File Transfer et permet à un utilisateur malintentionné d'effectuer une injection de requêtes illégitime par rebond (Cross Site Request Forgery).
Solution
Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation).
None| Title | Publication Time | Tags | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||
{
"$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
"affected_systems": [
{
"description": "IBM WebSphere MQ Managed File Transfer version 7.5.",
"product": {
"name": "WebSphere",
"vendor": {
"name": "IBM",
"scada": false
}
}
},
{
"description": "IBM WebSphere MQ File Transfer Edition Web Gateway versions 7.0.4 et ant\u00e9rieures ;",
"product": {
"name": "WebSphere",
"vendor": {
"name": "IBM",
"scada": false
}
}
}
],
"affected_systems_content": null,
"content": "## 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-2012-2206",
"url": "https://www.cve.org/CVERecord?id=CVE-2012-2206"
},
{
"name": "CVE-2012-3294",
"url": "https://www.cve.org/CVERecord?id=CVE-2012-3294"
}
],
"initial_release_date": "2012-08-14T00:00:00",
"last_revision_date": "2012-08-14T00:00:00",
"links": [
{
"title": "Bulletin de s\u00e9curit\u00e9 IBM swg21607482 du 08 ao\u00fbt 2012 :",
"url": "http://www-01.ibm.com/support/docview.wss?uid=swg21607482"
},
{
"title": "Bulletin de s\u00e9curit\u00e9 IBM swg21607481 du 08 ao\u00fbt 2012 :",
"url": "http://www-01.ibm.com/support/docview.wss?uid=swg21607481"
}
],
"reference": "CERTA-2012-AVI-431",
"revisions": [
{
"description": "version initiale.",
"revision_date": "2012-08-14T00:00:00.000000"
}
],
"risks": [
{
"description": "Injection de requ\u00eates ill\u00e9gitimes par rebond (CSRF)"
},
{
"description": "Contournement de la politique de s\u00e9curit\u00e9"
}
],
"summary": "Des vuln\u00e9rabilit\u00e9s ont \u00e9t\u00e9 corrig\u00e9es dans les produits IBM WebSphere. La\npremi\u00e8re concerne un manque de contr\u00f4le d\u0027acc\u00e8s dans IBM WebSphere MQ\nFile Transfer Edition permettant \u00e0 un utilisateur authentifi\u00e9 d\u0027acc\u00e9der\naux transferts d\u0027autres utilisateurs. La seconde concerne \u00e9galement le\nproduit IBM WebSphere MQ Managed File Transfer et permet \u00e0 un\nutilisateur malintentionn\u00e9 d\u0027effectuer une injection de requ\u00eates\nill\u00e9gitime par rebond \u003cspan class=\"textit\"\u003e(Cross Site Request\nForgery)\u003c/span\u003e.\n",
"title": "Vuln\u00e9rabilit\u00e9s dans les produits IBM WebSphere",
"vendor_advisories": [
{
"published_at": null,
"title": "Bulletins de s\u00e9curit\u00e9 IBM du 08 ao\u00fbt 2012",
"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.