CERTA-2010-AVI-531
Vulnerability from certfr_avis - Published: 2010-11-03 - Updated: 2010-11-03
Deux vulnérabilités affectent ProFTPD. L'exploitation réussie de celles-ci permet, entre autre, l'exécution de code arbitraire à distance.
Description
Deux vulnérabilités ont été corrigées dans ProFTPD.
La première provient d'un débordement de pile lorsque l'utilisateur envoie au serveur une chaîne d'échappement spécifique. Lorsqu'elle est réussie, cette attaque permet l'exécution de code arbitraire à distance.
La seconde vulnérabilité se situe dans le module mod_site_misc. Si une personne malintentionnée a des droits d'accès en écriture à un répertoire, elle peut ensuite modifier des fichiers et des répertoires auxquels elle n'aurait théoriquement pas accès.
Solution
Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation).
ProFTPD versions 1.3.0 à 1.3.3b.
| Vendor | Product | Description |
|---|
| Title | Publication Time | Tags | |||
|---|---|---|---|---|---|
|
|||||
{
"$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
"affected_systems": [],
"affected_systems_content": "\u003cp\u003eProFTPD versions 1.3.0 \u00e0 1.3.3b.\u003c/p\u003e",
"content": "## Description\n\nDeux vuln\u00e9rabilit\u00e9s ont \u00e9t\u00e9 corrig\u00e9es dans ProFTPD.\n\nLa premi\u00e8re provient d\u0027un d\u00e9bordement de pile lorsque l\u0027utilisateur\nenvoie au serveur une cha\u00eene d\u0027\u00e9chappement sp\u00e9cifique. Lorsqu\u0027elle est\nr\u00e9ussie, cette attaque permet l\u0027ex\u00e9cution de code arbitraire \u00e0 distance.\n\nLa seconde vuln\u00e9rabilit\u00e9 se situe dans le module mod_site_misc. Si une\npersonne malintentionn\u00e9e a des droits d\u0027acc\u00e8s en \u00e9criture \u00e0 un\nr\u00e9pertoire, elle peut ensuite modifier des fichiers et des r\u00e9pertoires\nauxquels elle n\u0027aurait th\u00e9oriquement pas acc\u00e8s.\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-2010-3867",
"url": "https://www.cve.org/CVERecord?id=CVE-2010-3867"
}
],
"initial_release_date": "2010-11-03T00:00:00",
"last_revision_date": "2010-11-03T00:00:00",
"links": [],
"reference": "CERTA-2010-AVI-531",
"revisions": [
{
"description": "version initiale.",
"revision_date": "2010-11-03T00:00:00.000000"
}
],
"risks": [
{
"description": "Ex\u00e9cution de code arbitraire \u00e0 distance"
},
{
"description": "Atteinte \u00e0 l\u0027int\u00e9grit\u00e9 des donn\u00e9es"
}
],
"summary": "Deux vuln\u00e9rabilit\u00e9s affectent \u003cspan class=\"textit\"\u003eProFTPD\u003c/span\u003e.\nL\u0027exploitation r\u00e9ussie de celles-ci permet, entre autre, l\u0027ex\u00e9cution de\ncode arbitraire \u00e0 distance.\n",
"title": "Vuln\u00e9rabilit\u00e9s dans ProFTPD",
"vendor_advisories": [
{
"published_at": null,
"title": "Bulletin de s\u00e9curit\u00e9 ProFTPD du 29 octobre 2010",
"url": "http://www.proftpd.org/docs/NEWS-1.3.3c"
}
]
}
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.