CERTA-2006-AVI-304
Vulnerability from certfr_avis - Published: 2006-07-20 - Updated: 2006-07-21None
Description
Une vulnérabilité présente sur Zope peut être exploitée par un utilisateur mal intentionné pour accéder à des pages non autorisées sur le serveur. Cette vulnérabilité ne peut être exploitée que par un utilisateur ayant les privilèges d'éditer des pages en mode « restructured text ».
Solution
Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation).
Zope versions 2.x antérieures à la version 2.7.
| Vendor | Product | Description |
|---|
| Title | Publication Time | Tags | ||||||
|---|---|---|---|---|---|---|---|---|
|
||||||||
{
"$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
"affected_systems": [],
"affected_systems_content": "\u003cp\u003eZope versions 2.x ant\u00e9rieures \u00e0 la version 2.7.\u003c/p\u003e",
"content": "## Description\n\nUne vuln\u00e9rabilit\u00e9 pr\u00e9sente sur Zope peut \u00eatre exploit\u00e9e par un\nutilisateur mal intentionn\u00e9 pour acc\u00e9der \u00e0 des pages non autoris\u00e9es sur\nle serveur. Cette vuln\u00e9rabilit\u00e9 ne peut \u00eatre exploit\u00e9e que par un\nutilisateur ayant les privil\u00e8ges d\u0027\u00e9diter des pages en mode \u00ab\nrestructured text \u00bb.\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-3458",
"url": "https://www.cve.org/CVERecord?id=CVE-2006-3458"
}
],
"initial_release_date": "2006-07-20T00:00:00",
"last_revision_date": "2006-07-21T00:00:00",
"links": [
{
"title": "Bulletin de s\u00e9curit\u00e9 FreeBSD du 14 juillet 2006 :",
"url": "http://www.vuxml.org/freebsd/"
}
],
"reference": "CERTA-2006-AVI-304",
"revisions": [
{
"description": "version initiale ;",
"revision_date": "2006-07-20T00:00:00.000000"
},
{
"description": "ajout du bulletin de s\u00e9curit\u00e9 FreeBSD.",
"revision_date": "2006-07-21T00:00:00.000000"
}
],
"risks": [
{
"description": "Atteinte \u00e0 la confidentialit\u00e9 des donn\u00e9es"
}
],
"summary": null,
"title": "Vuln\u00e9rabilit\u00e9 sur zope",
"vendor_advisories": [
{
"published_at": null,
"title": "Bulletin de s\u00e9curit\u00e9 Debian",
"url": "http://www.debian.org/security/2006/dsa-1113"
}
]
}
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.