CERTA-2006-AVI-121
Vulnerability from certfr_avis - Published: 2006-03-21 - Updated: 2006-06-06
Une vulnérabilité dans FreeRADIUS permet à un utilisateur distant de provoquer un déni de service du système vulnérable.
Description
Une erreur dans la mise en œuvre du protocole d'authentification EAP-MSCHAPv2 dans FreeRADIUS permet à un utilisateur mal intentionné distant, mais sur le même segment de réseau, de provoquer un déni de service du système vulnérable par le biais d'une machine cliente malicieusement configurée.
Solution
La version 1.1.1 de FreeRADIUS corrige le problème :
http://www.freeradius.org/getting.html
| Vendor | Product | Description | ||
|---|---|---|---|---|
| FreeRadius | FreeRADIUS | FreeRADIUS versions 1.1.0 et antérieures. |
| Title | Publication Time | Tags | |
|---|---|---|---|
|
|
|||
{
"$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
"affected_systems": [
{
"description": "FreeRADIUS versions 1.1.0 et ant\u00e9rieures.",
"product": {
"name": "FreeRADIUS",
"vendor": {
"name": "FreeRadius",
"scada": false
}
}
}
],
"affected_systems_content": "",
"content": "## Description\n\nUne erreur dans la mise en \u0153uvre du protocole d\u0027authentification\nEAP-MSCHAPv2 dans FreeRADIUS permet \u00e0 un utilisateur mal intentionn\u00e9\ndistant, mais sur le m\u00eame segment de r\u00e9seau, de provoquer un d\u00e9ni de\nservice du syst\u00e8me vuln\u00e9rable par le biais d\u0027une machine cliente\nmalicieusement configur\u00e9e.\n\n## Solution\n\nLa version 1.1.1 de FreeRADIUS corrige le probl\u00e8me :\n\n http://www.freeradius.org/getting.html\n",
"cves": [
{
"name": "CVE-2006-1354",
"url": "https://www.cve.org/CVERecord?id=CVE-2006-1354"
}
],
"initial_release_date": "2006-03-21T00:00:00",
"last_revision_date": "2006-06-06T00:00:00",
"links": [
{
"title": "Bulletin de s\u00e9curit\u00e9 RedHat RHSA-2006:0271-11 du 4 avril 2006 :",
"url": "https://rhn.redhat.com/errata/RHSA-2006-0271.html"
},
{
"title": "Bulletin de s\u00e9curit\u00e9 Gentoo GLSA-200604-03 du 4 avril 2006 :",
"url": "http://security.gentoo.org/glsa/glsa-200604-03.xml"
},
{
"title": "Bulletin de s\u00e9curit\u00e9 Debian DSA-1089 du 3 juin 2006 :",
"url": "http://www.debian.org/security/2006/dsa-1089"
},
{
"title": "Bulletin de s\u00e9curit\u00e9 Mandriva MDKSA-2006:066 du 05 mars 2006 : ",
"url": "http://frontal2.mandriva.com/security/advisories?name=MDKSA-2006:066"
},
{
"title": "Bulletin de s\u00e9curit\u00e9 Mandriva MDKSA-2006:060 du 23 mars 2006 :",
"url": "http://frontal2.mandriva.com/security/advisories?name=MDKSA-2006:060"
},
{
"title": "Bulletin de s\u00e9curit\u00e9 FreeBSD du 4 avril 2006 :",
"url": "http://www.vuxml.org/freebsd/pkg-freeradius.html"
},
{
"title": "Site de FreeRADIUS :",
"url": "http://www.freeradius.org"
}
],
"reference": "CERTA-2006-AVI-121",
"revisions": [
{
"description": "version initiale ;",
"revision_date": "2006-03-21T00:00:00.000000"
},
{
"description": "ajout de la r\u00e9f\u00e9rence au bulletin de s\u00e9curit\u00e9 Mandriva et de la r\u00e9f\u00e9rence CVE ;",
"revision_date": "2006-03-24T00:00:00.000000"
},
{
"description": "ajout de la r\u00e9f\u00e9rence au bulletin de s\u00e9curit\u00e9 de RedHat ;",
"revision_date": "2006-04-05T00:00:00.000000"
},
{
"description": "ajout de la r\u00e9f\u00e9rence au bulletin de s\u00e9curit\u00e9 de Mandriva ;",
"revision_date": "2006-04-06T00:00:00.000000"
},
{
"description": "ajout de la r\u00e9f\u00e9rence au bulletin de s\u00e9curit\u00e9 de Debian.",
"revision_date": "2006-06-06T00:00:00.000000"
}
],
"risks": [
{
"description": "D\u00e9ni de service"
}
],
"summary": "Une vuln\u00e9rabilit\u00e9 dans FreeRADIUS permet \u00e0 un utilisateur distant de\nprovoquer un d\u00e9ni de service du syst\u00e8me vuln\u00e9rable.\n",
"title": "Vuln\u00e9rabilit\u00e9 dans FreeRADIUS",
"vendor_advisories": [
{
"published_at": "2006-03-21",
"title": "Bulletin de s\u00e9curit\u00e9 FreeRADIUS ",
"url": "http://www.freeradius.org/security.html"
}
]
}
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.