CERTA-2011-AVI-572
Vulnerability from certfr_avis - Published: 2011-10-18 - Updated: 2011-10-18
Des vulnérabilités dans phpMyAdmin permettent à un utilisateur malveillant de lire des données sensibles ou de réaliser de l'injection de code indirecte.
Description
Deux vulnérabilités de phpMyAdmin ont été corrigées :
- dans des configurations très particulières, un message d'erreur peut divulguer des informations sur l'arborescence des fichiers du serveur ;
- l'interface d'installation ne valide pas correctement des données entrées. Cela permet de réaliser de l'injection de code indirecte qui, dans certaines circonstances, peut être persistente.
Solution
La version phpMyAdmin 3.4.6 corrige ces vulnérabilités.
Se référer aux bulletins de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation).
phpMyAdmin 3.4.x.
| Vendor | Product | Description |
|---|
| Title | Publication Time | Tags | |
|---|---|---|---|
{
"$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
"affected_systems": [],
"affected_systems_content": "\u003cp\u003ephpMyAdmin 3.4.x.\u003c/p\u003e",
"content": "## Description\n\nDeux vuln\u00e9rabilit\u00e9s de phpMyAdmin ont \u00e9t\u00e9 corrig\u00e9es\u00a0:\n\n- dans des configurations tr\u00e8s particuli\u00e8res, un message d\u0027erreur peut\n divulguer des informations sur l\u0027arborescence des fichiers du\n serveur\u00a0;\n- l\u0027interface d\u0027installation ne valide pas correctement des donn\u00e9es\n entr\u00e9es. Cela permet de r\u00e9aliser de l\u0027injection de code indirecte\n qui, dans certaines circonstances, peut \u00eatre persistente.\n\n## Solution\n\nLa version phpMyAdmin 3.4.6 corrige ces vuln\u00e9rabilit\u00e9s.\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-2011-4064",
"url": "https://www.cve.org/CVERecord?id=CVE-2011-4064"
},
{
"name": "CVE-2011-3646",
"url": "https://www.cve.org/CVERecord?id=CVE-2011-3646"
}
],
"initial_release_date": "2011-10-18T00:00:00",
"last_revision_date": "2011-10-18T00:00:00",
"links": [
{
"title": "Bulletin de s\u00e9curit\u00e9 phpMyAdmin PMASA-2011-15 du 17 octobre 2011 :",
"url": "http://www.phpmyadmin.net/home_page/security/PMASA-2011-15.php"
},
{
"title": "Bulletin de s\u00e9curit\u00e9 phpMyAdmin PMASA-2011-16 du 17 octobre 2011 :",
"url": "http://www.phpmyadmin.net/home_page/security/PMASA-2011-16.php"
}
],
"reference": "CERTA-2011-AVI-572",
"revisions": [
{
"description": "version initiale.",
"revision_date": "2011-10-18T00:00:00.000000"
}
],
"risks": [
{
"description": "Injection de code indirecte \u00e0 distance"
},
{
"description": "Atteinte \u00e0 la confidentialit\u00e9 des donn\u00e9es"
}
],
"summary": "Des vuln\u00e9rabilit\u00e9s dans phpMyAdmin permettent \u00e0 un utilisateur\nmalveillant de lire des donn\u00e9es sensibles ou de r\u00e9aliser de l\u0027injection\nde code indirecte.\n",
"title": "Vuln\u00e9rabilit\u00e9s dans phpMyAdmin",
"vendor_advisories": [
{
"published_at": null,
"title": "Bulletins de s\u00e9curit\u00e9 phpMyAdmin PMASA-2011-15 et 16 du 17 octobre 2011",
"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.