CERTA-2007-AVI-565
Vulnerability from certfr_avis - Published: 2007-12-26 - Updated: 2007-12-26
Une vulnérabilité affectant Novell Groupwise a été découverte et permet l'exécution de code arbitraire à distance.
Description
Une vulnérablité dans le paramètre SRC la balise IMG de Novell Groupwise permet à une personne malveillante d'exécuter du code arbitraire à distance. Cette vulnérabilité est exploitable via un couriel spécialement conçu et à condition que l'option de prévisualisation en HTML soit active et que l'utilisateur réponde ou transfère le message malveillant.
Solution
Se référer au site Novell pour l'obtention des correctifs (cf. section Documentation).
Novell Groupwise version 6.5.6 et les versions antérieures.
| Vendor | Product | Description |
|---|
| Title | Publication Time | Tags | |||
|---|---|---|---|---|---|
|
|||||
{
"$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
"affected_systems": [],
"affected_systems_content": "\u003cP\u003eNovell Groupwise version 6.5.6 et les versions ant\u00e9rieures.\u003c/P\u003e",
"content": "## Description\n\nUne vuln\u00e9rablit\u00e9 dans le param\u00e8tre SRC la balise IMG de Novell Groupwise\npermet \u00e0 une personne malveillante d\u0027ex\u00e9cuter du code arbitraire \u00e0\ndistance. Cette vuln\u00e9rabilit\u00e9 est exploitable via un couriel\nsp\u00e9cialement con\u00e7u et \u00e0 condition que l\u0027option de pr\u00e9visualisation en\nHTML soit active et que l\u0027utilisateur r\u00e9ponde ou transf\u00e8re le message\nmalveillant.\n\n## Solution\n\nSe r\u00e9f\u00e9rer au site Novell pour l\u0027obtention des correctifs (cf. section\nDocumentation).\n",
"cves": [
{
"name": "CVE-2007-6435",
"url": "https://www.cve.org/CVERecord?id=CVE-2007-6435"
}
],
"initial_release_date": "2007-12-26T00:00:00",
"last_revision_date": "2007-12-26T00:00:00",
"links": [
{
"title": "Mise \u00e0 jour Novell Groupwise :",
"url": "http://download.novell.com/Download?buildid=VH6T0VgdwWw"
}
],
"reference": "CERTA-2007-AVI-565",
"revisions": [
{
"description": "version initiale.",
"revision_date": "2007-12-26T00:00:00.000000"
}
],
"risks": [
{
"description": "Ex\u00e9cution de code arbitraire \u00e0 distance"
}
],
"summary": "Une vuln\u00e9rabilit\u00e9 affectant Novell Groupwise a \u00e9t\u00e9 d\u00e9couverte et permet\nl\u0027ex\u00e9cution de code arbitraire \u00e0 distance.\n",
"title": "Vuln\u00e9rabilit\u00e9 dans Novell Groupwise",
"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.