CERTA-2012-AVI-052
Vulnerability from certfr_avis - Published: 2012-02-03 - Updated: 2012-02-03
De multiples vulnérabilités dans Drupal permettent de contourner des restrictions d'accès à des fichiers, de modifier des informations d'utilisateur et d'injecter illégitimement des requêtes par rebond.
Description
De multiples vulnérabilités ont été découvertes dans Drupal :
- OpenId ne vérifie pas si certains attributs sont signés, ce qui permet de modifier les informations des utilisateurs (CVE-2012-0825) ;
- des injections de requêtes illégitimes par rebond sont possibles via le module Aggregator. Dans certains cas, l'exploitation de cette vulnérabilité permet de réaliser un déni de service (CVE-2012-0826) ;
- sous certaines conditions, des utilisateurs peuvent télécharger indûment des fichiers via le module File. Ce problème n'affecte que les versions 7.x de Drupal (CVE-2012-0827).
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": "Drupal versions 7.x ant\u00e9rieures \u00e0 7.11.",
"product": {
"name": "Drupal",
"vendor": {
"name": "Drupal",
"scada": false
}
}
},
{
"description": "Drupal versions 6.x ant\u00e9rieures \u00e0 6.23 ;",
"product": {
"name": "Drupal",
"vendor": {
"name": "Drupal",
"scada": false
}
}
}
],
"affected_systems_content": null,
"content": "## Description\n\nDe multiples vuln\u00e9rabilit\u00e9s ont \u00e9t\u00e9 d\u00e9couvertes dans Drupal :\n\n- OpenId ne v\u00e9rifie pas si certains attributs sont sign\u00e9s, ce qui\n permet de modifier les informations des utilisateurs (CVE-2012-0825)\n ;\n- des injections de requ\u00eates ill\u00e9gitimes par rebond sont possibles via\n le module Aggregator. Dans certains cas, l\u0027exploitation de cette\n vuln\u00e9rabilit\u00e9 permet de r\u00e9aliser un d\u00e9ni de service (CVE-2012-0826)\n ;\n- sous certaines conditions, des utilisateurs peuvent t\u00e9l\u00e9charger\n ind\u00fbment des fichiers via le module File. Ce probl\u00e8me n\u0027affecte que\n les versions 7.x de Drupal (CVE-2012-0827).\n\n## 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-0825",
"url": "https://www.cve.org/CVERecord?id=CVE-2012-0825"
},
{
"name": "CVE-2012-0826",
"url": "https://www.cve.org/CVERecord?id=CVE-2012-0826"
},
{
"name": "CVE-2012-0827",
"url": "https://www.cve.org/CVERecord?id=CVE-2012-0827"
}
],
"initial_release_date": "2012-02-03T00:00:00",
"last_revision_date": "2012-02-03T00:00:00",
"links": [
{
"title": "Bulletin de s\u00e9curit\u00e9 Drupal SA-CORE-2012-001 du 01 f\u00e9vrier 2012 :",
"url": "http://drupal.org/node/1425084"
}
],
"reference": "CERTA-2012-AVI-052",
"revisions": [
{
"description": "version initiale.",
"revision_date": "2012-02-03T00:00:00.000000"
}
],
"risks": [
{
"description": "Injection de requ\u00eates ill\u00e9gitimes par rebond (CSRF)"
},
{
"description": "Atteinte \u00e0 l\u0027int\u00e9grit\u00e9 des donn\u00e9es"
},
{
"description": "Contournement de la politique de s\u00e9curit\u00e9"
}
],
"summary": "De multiples vuln\u00e9rabilit\u00e9s dans \u003cspan class=\"textit\"\u003eDrupal\u003c/span\u003e\npermettent de contourner des restrictions d\u0027acc\u00e8s \u00e0 des fichiers, de\nmodifier des informations d\u0027utilisateur et d\u0027injecter ill\u00e9gitimement des\nrequ\u00eates par rebond.\n",
"title": "Multiples vuln\u00e9rabilit\u00e9s dans Drupal",
"vendor_advisories": [
{
"published_at": null,
"title": "Bulletin de s\u00e9curit\u00e9 Drupal SA-CORE-2012-001 du 01 f\u00e9vrier 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.