CERTA-2011-AVI-485
Vulnerability from certfr_avis - Published: - Updated:
Une vulnérabilité dans Apache Tomcat permet à un utilisateur malveillant de contourner la politique de sécurité et de porter atteinte à l'intégrité et à la confidentialité de données.
Description
Une vulnérabilité dans Apache Tomcat affecte le traitement du protocole AJP (Apache JServ Protocol).
Elle permet à un utilisateur malveillant d'insérer une adresse IP de client ou le nom d'un utilisateur authentifié, et de provoquer le mélange des réponses de requêtes d'utilisateurs différents.
Solution
Les correctifs sont les suivants selon les branches :
- révision 1162960, puis version 5.5.34 dès publication ;
- révision 1162959, puis version 6.0.34 dès publication ;
- révision 1162958, puis version 7.0.21 dès publication.
Se référer aux bulletins de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation).
Apache Tomcat, versions 5.5.x, 6.0.x et 7.0.x.
| Vendor | Product | Description |
|---|
| Title | Publication Time | Tags | |
|---|---|---|---|
{
"$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
"affected_systems": [],
"affected_systems_content": "\u003cp\u003eApache Tomcat, versions 5.5.x, 6.0.x et 7.0.x.\u003c/p\u003e",
"content": "## Description\n\nUne vuln\u00e9rabilit\u00e9 dans Apache Tomcat affecte le traitement du protocole\nAJP (Apache JServ Protocol).\n\nElle permet \u00e0 un utilisateur malveillant d\u0027ins\u00e9rer une adresse IP de\nclient ou le nom d\u0027un utilisateur authentifi\u00e9, et de provoquer le\nm\u00e9lange des r\u00e9ponses de requ\u00eates d\u0027utilisateurs diff\u00e9rents.\n\n## Solution\n\nLes correctifs sont les suivants selon les branches\u00a0:\n\n- r\u00e9vision 1162960, puis version 5.5.34 d\u00e8s publication\u00a0;\n- r\u00e9vision 1162959, puis version 6.0.34 d\u00e8s publication\u00a0;\n- r\u00e9vision 1162958, puis version 7.0.21 d\u00e8s publication.\n\nSe r\u00e9f\u00e9rer aux bulletins de s\u00e9curit\u00e9 de l\u0027\u00e9diteur pour l\u0027obtention des\ncorrectifs (cf. section Documentation).\n",
"cves": [
{
"name": "CVE-2011-3190",
"url": "https://www.cve.org/CVERecord?id=CVE-2011-3190"
}
],
"links": [
{
"title": "Annonces de versions Apache Tomcat du 29 ao\u00fbt 2011 :",
"url": "http://tomcat.apache.org/security-6.html"
},
{
"title": "Annonces de versions Apache Tomcat du 29 ao\u00fbt 2011 :",
"url": "http://tomcat.apache.org/security-7.html"
},
{
"title": "Annonces de versions Apache Tomcat du 29 ao\u00fbt 2011 :",
"url": "http://tomcat.apache.org/security-5.html"
}
],
"reference": "CERTA-2011-AVI-485",
"revisions": [
{
"description": "version initiale.",
"revision_date": "2011-08-31T00:00:00.000000"
}
],
"risks": [
{
"description": "Atteinte \u00e0 l\u0027int\u00e9grit\u00e9 des donn\u00e9es"
},
{
"description": "Contournement de la politique de s\u00e9curit\u00e9"
},
{
"description": "Atteinte \u00e0 la confidentialit\u00e9 des donn\u00e9es"
}
],
"summary": "Une vuln\u00e9rabilit\u00e9 dans Apache Tomcat permet \u00e0 un utilisateur malveillant\nde contourner la politique de s\u00e9curit\u00e9 et de porter atteinte \u00e0\nl\u0027int\u00e9grit\u00e9 et \u00e0 la confidentialit\u00e9 de donn\u00e9es.\n",
"title": "Vuln\u00e9rabilit\u00e9 dans Apache Tomcat",
"vendor_advisories": []
}
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.