CERTA-2007-AVI-282
Vulnerability from certfr_avis - Published: - Updated:None
Description
Une vulnérabilité de type injection de code indirecte serait possible : une personne malveillante pourrait exécuter du code arbitraire sur le système par le biais d'une page Web spécialement construite, et à la condition que l'utilisateur légitime soit connecté à la fois sur cette page et sur l'interface du système.
Une seconde vulnérabilité permettrait à tout utilisateur connecté au système de modifier le mot de passe de l'administrateur, sans connaître celui existant.
Solution
Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation).
- Check Point SafeOffice Appliances 7.x ;
- Check Point VPN-1 UTM Edge ;
- Check Point ZoneAlarm Z100G 7.x.
Les versions du logiciel antérieures à 7.0.45 seraient affectées.
| Vendor | Product | Description |
|---|
| Title | Publication Time | Tags | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||
{
"$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
"affected_systems": [],
"affected_systems_content": "\u003cUL\u003e \u003cLI\u003eCheck Point SafeOffice Appliances 7.x ;\u003c/LI\u003e \u003cLI\u003eCheck Point VPN-1 UTM Edge ;\u003c/LI\u003e \u003cLI\u003eCheck Point ZoneAlarm Z100G 7.x.\u003c/LI\u003e \u003c/UL\u003e \u003cP\u003eLes versions du logiciel ant\u00e9rieures \u00e0 7.0.45 seraient affect\u00e9es.\u003c/P\u003e",
"content": "## Description\n\nUne vuln\u00e9rabilit\u00e9 de type injection de code indirecte serait possible :\nune personne malveillante pourrait ex\u00e9cuter du code arbitraire sur le\nsyst\u00e8me par le biais d\u0027une page Web sp\u00e9cialement construite, et \u00e0 la\ncondition que l\u0027utilisateur l\u00e9gitime soit connect\u00e9 \u00e0 la fois sur cette\npage et sur l\u0027interface du syst\u00e8me.\n\nUne seconde vuln\u00e9rabilit\u00e9 permettrait \u00e0 tout utilisateur connect\u00e9 au\nsyst\u00e8me de modifier le mot de passe de l\u0027administrateur, sans conna\u00eetre\ncelui existant.\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-2007-3462",
"url": "https://www.cve.org/CVERecord?id=CVE-2007-3462"
}
],
"links": [
{
"title": "Site officiel de Check Point :",
"url": "http://www.checkpoint.com"
},
{
"title": "Mises \u00e0 jour disponibles de Check Point :",
"url": "http://www.sofaware.com/supportDownloads.aspx?boneId=182"
},
{
"title": "Avis de s\u00e9curit\u00e9 Calyptix CX-2007-04 du 26 juin 2007 :",
"url": "http://labs.calyptix.com/CX-2007-04.php"
}
],
"reference": "CERTA-2007-AVI-282",
"revisions": [
{
"description": "version initiale.",
"revision_date": "2007-06-28T00:00:00.000000"
}
],
"risks": [
{
"description": "Contournement de la politique de s\u00e9curit\u00e9"
}
],
"summary": null,
"title": "Vuln\u00e9rabilit\u00e9s dans des produits Check Point",
"vendor_advisories": [
{
"published_at": null,
"title": "Avis de s\u00e9curit\u00e9 de Calyptix CX-2007-04 du 26 juin 2007",
"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.