CERTA-2008-AVI-453
Vulnerability from certfr_avis - Published: 2008-09-10 - Updated: 2008-09-19
Deux vulnérabilités présentes dans WordPress permettent à un utilisateur malveillant de contourner la politique de sécurité.
Description
Une première vulnérabilité affecte la création et la gestion des utilisateurs. Son exploitation permet à un utilisateur malveillant de réinitialiser le mot de passe d'un utilisateur légitime. Le mot de passe de ce dernier est remplacé par un mot de passe créé aléatoirement.
Une deuxième vulnérabilité affecte la fonction PHP mt_rand. Dans certaines conditions, la suite pseudoaléatoire produite par cette fonction est prédictible.
Cette fonction est notamment utilisée pour la réinitialisation des mots de passe.
Solution
Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation).
WordPress, version 2.6.1 et versions précédentes.
| Vendor | Product | Description |
|---|
| Title | Publication Time | Tags | ||||||
|---|---|---|---|---|---|---|---|---|
|
||||||||
{
"$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
"affected_systems": [],
"affected_systems_content": "\u003cp\u003eWordPress, version 2.6.1 et versions pr\u00e9c\u00e9dentes.\u003c/p\u003e",
"content": "## Description\n\nUne premi\u00e8re vuln\u00e9rabilit\u00e9 affecte la cr\u00e9ation et la gestion des\nutilisateurs. Son exploitation permet \u00e0 un utilisateur malveillant de\nr\u00e9initialiser le mot de passe d\u0027un utilisateur l\u00e9gitime. Le mot de passe\nde ce dernier est remplac\u00e9 par un mot de passe cr\u00e9\u00e9 al\u00e9atoirement.\n\nUne deuxi\u00e8me vuln\u00e9rabilit\u00e9 affecte la fonction PHP mt_rand. Dans\ncertaines conditions, la suite pseudoal\u00e9atoire produite par cette\nfonction est pr\u00e9dictible.\n\nCette fonction est notamment utilis\u00e9e pour la r\u00e9initialisation des mots\nde passe.\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-2008-4107",
"url": "https://www.cve.org/CVERecord?id=CVE-2008-4107"
},
{
"name": "CVE-2008-4106",
"url": "https://www.cve.org/CVERecord?id=CVE-2008-4106"
}
],
"initial_release_date": "2008-09-10T00:00:00",
"last_revision_date": "2008-09-19T00:00:00",
"links": [
{
"title": "Site de t\u00e9l\u00e9chargement du WordPress :",
"url": "http://wordpress.org/"
}
],
"reference": "CERTA-2008-AVI-453",
"revisions": [
{
"description": "version initiale.",
"revision_date": "2008-09-10T00:00:00.000000"
},
{
"description": "ajout de r\u00e9f\u00e9rences CVE.",
"revision_date": "2008-09-19T00:00:00.000000"
}
],
"risks": [
{
"description": "Contournement de la politique de s\u00e9curit\u00e9"
}
],
"summary": "Deux vuln\u00e9rabilit\u00e9s pr\u00e9sentes dans WordPress permettent \u00e0 un utilisateur\nmalveillant de contourner la politique de s\u00e9curit\u00e9.\n",
"title": "Vuln\u00e9rabilit\u00e9s de WordPress",
"vendor_advisories": [
{
"published_at": null,
"title": "Bulletin WordPress du 08 septembre 2008",
"url": "http://wordpress.org/development"
}
]
}
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.