CERTA-2008-AVI-383
Vulnerability from certfr_avis - Published: 2008-08-01 - Updated: 2008-08-01
Plusieurs vulnérabilités de phpMyAdmin permettent à un utilisateur malveillant de réaliser de l'injection de code indirecte ou de porter atteinte à l'intégrité des données.
Description
Une première vulnérabilité réside dans un manque de vérification lors des requêtes HTTP. Le détournement par un utilisateur malveillant d'une requête d'un utilisateur authentifié peut conduire à la création d'une base de données ou à la modification du jeu de caractères à l'insu de ce dernier.
Une deuxième vulnérabilité permet à un utilisateur malveillant de réaliser de l'injection de code indirecte (cross site scripting).
Solution
La version 2.11.8 ne présente pas ces vulnérabilités. Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation).
phpMyAdmin, versions antérieures à la version 2.11.8.
| Vendor | Product | Description |
|---|
| Title | Publication Time | Tags | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||
{
"$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
"affected_systems": [],
"affected_systems_content": "\u003cSPAN class=\"textit\"\u003ephpMyAdmin\u003c/SPAN\u003e, versions ant\u00e9rieures \u00e0 la version 2.11.8.",
"content": "## Description\n\nUne premi\u00e8re vuln\u00e9rabilit\u00e9 r\u00e9side dans un manque de v\u00e9rification lors\ndes requ\u00eates HTTP. Le d\u00e9tournement par un utilisateur malveillant d\u0027une\nrequ\u00eate d\u0027un utilisateur authentifi\u00e9 peut conduire \u00e0 la cr\u00e9ation d\u0027une\nbase de donn\u00e9es ou \u00e0 la modification du jeu de caract\u00e8res \u00e0 l\u0027insu de ce\ndernier.\n\nUne deuxi\u00e8me vuln\u00e9rabilit\u00e9 permet \u00e0 un utilisateur malveillant de\nr\u00e9aliser de l\u0027injection de code indirecte (cross site scripting).\n\n## Solution\n\nLa version 2.11.8 ne pr\u00e9sente pas ces vuln\u00e9rabilit\u00e9s. Se r\u00e9f\u00e9rer au\nbulletin de s\u00e9curit\u00e9 de l\u0027\u00e9diteur pour l\u0027obtention des correctifs (cf.\nsection Documentation).\n",
"cves": [
{
"name": "CVE-2008-3197",
"url": "https://www.cve.org/CVERecord?id=CVE-2008-3197"
}
],
"initial_release_date": "2008-08-01T00:00:00",
"last_revision_date": "2008-08-01T00:00:00",
"links": [
{
"title": "Site de t\u00e9l\u00e9chargement du projet phpMyAdmin :",
"url": "http://www.phpMyAdmin.net"
},
{
"title": "Bulletins de s\u00e9curit\u00e9 du projet phpMyAdmin :",
"url": "http://www.phpMyAdmin.net/home_page/security.php?issue=PMASA-2008-5"
},
{
"title": "Bulletins de s\u00e9curit\u00e9 du projet phpMyAdmin :",
"url": "http://www.phpMyAdmin.net/home_page/security.php?issue=PMASA-2008-6"
}
],
"reference": "CERTA-2008-AVI-383",
"revisions": [
{
"description": "version initiale.",
"revision_date": "2008-08-01T00:00:00.000000"
}
],
"risks": [
{
"description": "Injection de code indirecte"
},
{
"description": "Atteinte \u00e0 l\u0027int\u00e9grit\u00e9 des donn\u00e9es"
}
],
"summary": "Plusieurs vuln\u00e9rabilit\u00e9s de \u003cspan class=\"textit\"\u003ephpMyAdmin\u003c/span\u003e\npermettent \u00e0 un utilisateur malveillant de r\u00e9aliser de l\u0027injection de\ncode indirecte ou de porter atteinte \u00e0 l\u0027int\u00e9grit\u00e9 des donn\u00e9es.\n",
"title": "Vuln\u00e9rabilit\u00e9s de phpMyAdmin",
"vendor_advisories": [
{
"published_at": null,
"title": "Bulletins PMASA-2008-5 et PMASA-2008-6",
"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.