CERTA-2007-AVI-416
Vulnerability from certfr_avis - Published: 2007-09-24 - Updated: 2007-09-24
Une vulnérabilité dans le noyau Linux permet à un utilisateur local d'élever ses privilèges.
Description
Une vulnérabilité dans la mise en œuvre de l'appel système ptrace par le noyau Linux permet à un utilisateur local d'élever ses privilèges. La faille est relative à une mauvaise initialisation de registre sur une architecture x86_64 lors de la sortie d'un appel système ptrace en mode 32bit.
Solution
Les versions 2.4.35.3 et 2.6.22.7 du noyau Linux corrigent le problème :
http://www.kernel.org/pub/linux/kernel/v2.4/
http://www.kernel.org/pub/linux/kernel/v2.6/
None
| Title | Publication Time | Tags | |
|---|---|---|---|
{
"$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
"affected_systems": [
{
"description": "Linux kernel versions 2.6.22.6 et ant\u00e9rieures.",
"product": {
"name": "N/A",
"vendor": {
"name": "N/A",
"scada": false
}
}
},
{
"description": "Linux kernel versions 2.4.35.2 et ant\u00e9rieures ;",
"product": {
"name": "N/A",
"vendor": {
"name": "N/A",
"scada": false
}
}
}
],
"affected_systems_content": null,
"content": "## Description\n\nUne vuln\u00e9rabilit\u00e9 dans la mise en \u0153uvre de l\u0027appel syst\u00e8me ptrace par le\nnoyau Linux permet \u00e0 un utilisateur local d\u0027\u00e9lever ses privil\u00e8ges. La\nfaille est relative \u00e0 une mauvaise initialisation de registre sur une\narchitecture x86_64 lors de la sortie d\u0027un appel syst\u00e8me ptrace en mode\n32bit.\n\n## Solution\n\nLes versions 2.4.35.3 et 2.6.22.7 du noyau Linux corrigent le probl\u00e8me :\n\n http://www.kernel.org/pub/linux/kernel/v2.4/\n\n http://www.kernel.org/pub/linux/kernel/v2.6/\n",
"cves": [
{
"name": "CVE-2007-4573",
"url": "https://www.cve.org/CVERecord?id=CVE-2007-4573"
}
],
"initial_release_date": "2007-09-24T00:00:00",
"last_revision_date": "2007-09-24T00:00:00",
"links": [
{
"title": "Site du noyau Linux :",
"url": "http://www.kernel.org"
},
{
"title": "Liste des changements apport\u00e9s \u00e0 la version 2.4.35.3 du noyau Linux :",
"url": "http://www.kernel.org/pub/linux/kernel/v2.4/Changelog-2.4.35.3"
},
{
"title": "Liste des changements apport\u00e9s \u00e0 la version 2.6.22.7 du noyau Linux :",
"url": "http://www.kernel.org/pub/linux/kernel/v2.4/Changelog-2.6.22.7"
}
],
"reference": "CERTA-2007-AVI-416",
"revisions": [
{
"description": "version initiale.",
"revision_date": "2007-09-24T00:00:00.000000"
}
],
"risks": [
{
"description": "\u00c9l\u00e9vation de privil\u00e8ges"
}
],
"summary": "Une vuln\u00e9rabilit\u00e9 dans le noyau Linux permet \u00e0 un utilisateur local\nd\u0027\u00e9lever ses privil\u00e8ges.\n",
"title": "Vuln\u00e9rabilit\u00e9 du noyau Linux",
"vendor_advisories": [
{
"published_at": null,
"title": "Liste des changements apport\u00e9s aux versions 2.4.35.3 et 2.6.22.7 du noyau Linux",
"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.