CERTA-2006-AVI-184
Vulnerability from certfr_avis - Published: 2006-05-05 - Updated: 2006-06-12
Une vulnérabilité existe dans les versions 6.4 et 6.5 d'AWStats. Elle permet à une personne malveillante d'envoyer une requête particulière conduisant à l'exécution de code arbitraire à distance.
Description
AWStats est un outil d'analyse statistique pour site web. Les versions 6.4 et 6.5 présentent une vulnérabilité de la mise à jour des valeurs statistiques lançée à partir de la page web. La valeur d'entrée du paramètre migrate n'est pas suffisamment contrôlée. Un utilisateur peut alors envoyer une requête particulière qui ne sera pas correctement interprétée par la fonction Perl open(), afin d'injecter et d'exécuter des commandes à distance. Celles-ci seront lancées avec les mêmes privilèges que le processus associé à l'interface CGI d'AWStats. Il faut noter que cette méthode est possible si l'option AllowToUpdateStatsFromBrowser est activée dans le fichier de configuration d'AWStats. Ce n'est pas le cas par défaut.
Solution
Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation).
Les versions 6.4 et 6.5 d'AWStats.
| Vendor | Product | Description |
|---|
| Title | Publication Time | Tags | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||
{
"$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
"affected_systems": [],
"affected_systems_content": "\u003cP\u003eLes versions 6.4 et 6.5 d\u0027AWStats.\u003c/P\u003e",
"content": "## Description\n\nAWStats est un outil d\u0027analyse statistique pour site web. Les versions\n6.4 et 6.5 pr\u00e9sentent une vuln\u00e9rabilit\u00e9 de la mise \u00e0 jour des valeurs\nstatistiques lan\u00e7\u00e9e \u00e0 partir de la page web. La valeur d\u0027entr\u00e9e du\nparam\u00e8tre migrate n\u0027est pas suffisamment contr\u00f4l\u00e9e. Un utilisateur peut\nalors envoyer une requ\u00eate particuli\u00e8re qui ne sera pas correctement\ninterpr\u00e9t\u00e9e par la fonction Perl open(), afin d\u0027injecter et d\u0027ex\u00e9cuter\ndes commandes \u00e0 distance. Celles-ci seront lanc\u00e9es avec les m\u00eames\nprivil\u00e8ges que le processus associ\u00e9 \u00e0 l\u0027interface CGI d\u0027AWStats. Il faut\nnoter que cette m\u00e9thode est possible si l\u0027option\nAllowToUpdateStatsFromBrowser est activ\u00e9e dans le fichier de\nconfiguration d\u0027AWStats. Ce n\u0027est pas le cas par d\u00e9faut.\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-2006-2237",
"url": "https://www.cve.org/CVERecord?id=CVE-2006-2237"
}
],
"initial_release_date": "2006-05-05T00:00:00",
"last_revision_date": "2006-06-12T00:00:00",
"links": [
{
"title": "Mise \u00e0 jour de l\u0027outil AWStats :",
"url": "http://awstats.sourceforge.net"
},
{
"title": "Bulletin de s\u00e9curit\u00e9 Debian DSA-1058 du 18 mai 2006 :",
"url": "http://www.debian.org/security/2006/dsa-1058"
},
{
"title": "Bulletin de s\u00e9curit\u00e9 FreeBSD du 05 mai 2006 :",
"url": "http://www.vuxml.org/freebsd/pkg-awstats.html"
},
{
"title": "Bulletin de s\u00e9curit\u00e9 Gentoo GLSA 200606-06 du 07 juin 2006 :",
"url": "http://www.gentoo.org/security/en/glsa/glsa-200606-06.xml"
}
],
"reference": "CERTA-2006-AVI-184",
"revisions": [
{
"description": "version initiale.",
"revision_date": "2006-05-05T00:00:00.000000"
},
{
"description": "ajout des r\u00e9f\u00e9rences aux bulletins de s\u00e9curit\u00e9 FreeBSD, Debian et de la r\u00e9f\u00e9rence CVE.",
"revision_date": "2006-05-19T00:00:00.000000"
},
{
"description": "ajout de la r\u00e9f\u00e9rence au bulletin de s\u00e9curit\u00e9 Gentoo.",
"revision_date": "2006-06-12T00:00:00.000000"
}
],
"risks": [
{
"description": "Ex\u00e9cution de code arbitraire \u00e0 distance"
}
],
"summary": "Une vuln\u00e9rabilit\u00e9 existe dans les versions 6.4 et 6.5 d\u0027AWStats. Elle\npermet \u00e0 une personne malveillante d\u0027envoyer une requ\u00eate particuli\u00e8re\nconduisant \u00e0 l\u0027ex\u00e9cution de code arbitraire \u00e0 distance.\n",
"title": "Vuln\u00e9rabilit\u00e9 de AWStats",
"vendor_advisories": [
{
"published_at": null,
"title": "Bulletin de mise \u00e0 jour de AWStats",
"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.