CERTA-2006-AVI-295
Vulnerability from certfr_avis - Published: 2006-07-18 - Updated: 2006-07-18None
Description
prctl est une fonction du noyau Linux permettant d'effectuer certaines opérations sur les processus. Il est aussi possible, depuis les versions 2.6.13 du noyau Linux, de spécifier si les processus peuvent créer des fichiers core dump, et sous quelles conditions. Cela peut être un argument de la fonction prctl. Une vulnérabilité a été identifiée dans celle-ci combinée à un tel argument.
Un utilisateur malveillant local peut profiter de cette vulnérabilité pour éléver ses privilèges à ceux d'administrateur (root) sur le système affecté.
Solution
Se référer aux différents bulletins de sécurité pour l'obtention des correctifs (cf. section Documentation).
Les noyaux Linux, des versions 2.6.13 jusqu'à la version 2.6.17.4 non comprise, et 2.6.16 antérieure à 2.6.16.24.
| Vendor | Product | Description |
|---|
| Title | Publication Time | Tags | |
|---|---|---|---|
|
|
|||
{
"$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
"affected_systems": [],
"affected_systems_content": "\u003cP\u003eLes noyaux Linux, des versions 2.6.13 jusqu\u0027\u00e0 la version 2.6.17.4 non comprise, et 2.6.16 ant\u00e9rieure \u00e0 2.6.16.24.\u003c/P\u003e",
"content": "## Description\n\nprctl est une fonction du noyau Linux permettant d\u0027effectuer certaines\nop\u00e9rations sur les processus. Il est aussi possible, depuis les versions\n2.6.13 du noyau Linux, de sp\u00e9cifier si les processus peuvent cr\u00e9er des\nfichiers core dump, et sous quelles conditions. Cela peut \u00eatre un\nargument de la fonction prctl. Une vuln\u00e9rabilit\u00e9 a \u00e9t\u00e9 identifi\u00e9e dans\ncelle-ci combin\u00e9e \u00e0 un tel argument.\n\nUn utilisateur malveillant local peut profiter de cette vuln\u00e9rabilit\u00e9\npour \u00e9l\u00e9ver ses privil\u00e8ges \u00e0 ceux d\u0027administrateur (root) sur le syst\u00e8me\naffect\u00e9.\n\n## Solution\n\nSe r\u00e9f\u00e9rer aux diff\u00e9rents bulletins de s\u00e9curit\u00e9 pour l\u0027obtention des\ncorrectifs (cf. section Documentation).\n",
"cves": [
{
"name": "CVE-2006-2451",
"url": "https://www.cve.org/CVERecord?id=CVE-2006-2451"
}
],
"initial_release_date": "2006-07-18T00:00:00",
"last_revision_date": "2006-07-18T00:00:00",
"links": [
{
"title": "Bulletin de s\u00e9curit\u00e9 RedHat RHSA-2006:0574 du 07 juillet 2006 :",
"url": "http://rhn.redhat.com/errata/RHSA-2006-0574.html"
},
{
"title": "Mise \u00e0 jour de s\u00e9curit\u00e9 Fedora Core 4 du 15 juillet 2006 :",
"url": "http://download.fedora.redhat.com/pub/fedora/linux/core/updates/4/"
},
{
"title": "Mise \u00e0 jour des noyaux Linux :",
"url": "http://www.kernel.org/pub/linux/kernel/v2.6/"
},
{
"title": "Bulletin de s\u00e9curit\u00e9 Ubuntu USN-311-1 du 11 juillet 2006 :",
"url": "http://www.ubuntulinux.org/usn/usn-311-1"
}
],
"reference": "CERTA-2006-AVI-295",
"revisions": [
{
"description": "version initiale.",
"revision_date": "2006-07-18T00:00:00.000000"
}
],
"risks": [
{
"description": "D\u00e9ni de service"
},
{
"description": "Contournement de la politique de s\u00e9curit\u00e9"
},
{
"description": "\u00c9l\u00e9vation de privil\u00e8ges"
}
],
"summary": null,
"title": "Vuln\u00e9rabilit\u00e9 de la fonction prctl du noyau Linux",
"vendor_advisories": [
{
"published_at": null,
"title": "Bulletin de s\u00e9curit\u00e9 RedHat du 07 juillet 2006",
"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.