CERTA-2007-AVI-176
Vulnerability from certfr_avis - Published: 2007-04-16 - Updated: 2007-04-16None
Description
Une vulnérabilité a été identifiée dans le produit d'administration LANDesk Management Suite. Ce dernier permet de prendre en charge des tâches automatiques de gestion d'un parc de systèmes d'informations.
Il ouvre par défaut un service d'alerte (aolnsrvr.exe) en écoute sur le port UDP 65535. Celui-ci ne manipulerait pas correctement les informations reçues, pouvant ainsi conduire à un débordement de tampon.
Une personne malveillante pourrait exploiter cette vulnérabilité pour exécuter du code arbitraire à distance, avec les droits de l'utilisateur SYSTEM.
Solution
Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation).
None| Title | Publication Time | Tags | |
|---|---|---|---|
|
|
|||
{
"$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
"affected_systems": [
{
"description": "LANDesk Management Suite 8.7.",
"product": {
"name": "N/A",
"vendor": {
"name": "N/A",
"scada": false
}
}
}
],
"affected_systems_content": null,
"content": "## Description\n\nUne vuln\u00e9rabilit\u00e9 a \u00e9t\u00e9 identifi\u00e9e dans le produit d\u0027administration\nLANDesk Management Suite. Ce dernier permet de prendre en charge des\nt\u00e2ches automatiques de gestion d\u0027un parc de syst\u00e8mes d\u0027informations.\n\nIl ouvre par d\u00e9faut un service d\u0027alerte (aolnsrvr.exe) en \u00e9coute sur le\nport UDP 65535. Celui-ci ne manipulerait pas correctement les\ninformations re\u00e7ues, pouvant ainsi conduire \u00e0 un d\u00e9bordement de tampon.\n\nUne personne malveillante pourrait exploiter cette vuln\u00e9rabilit\u00e9 pour\nex\u00e9cuter du code arbitraire \u00e0 distance, avec les droits de l\u0027utilisateur\nSYSTEM.\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-1674",
"url": "https://www.cve.org/CVERecord?id=CVE-2007-1674"
}
],
"initial_release_date": "2007-04-16T00:00:00",
"last_revision_date": "2007-04-16T00:00:00",
"links": [
{
"title": "Base de connaissances LanDesk num\u00e9ro 4142 publi\u00e9e le 13 avril 2007 :",
"url": "http://kb.landesk.com/al/12/4/article.asp?aid=4142\u0026n=1\u0026tab=search\u0026bt=4n\u0026s=1"
},
{
"title": "Avis de s\u00e9curit\u00e9 du groupe de recherche 3Com TippingPoint TSRT-07-04 du 13 avril 2007 :",
"url": "http://www.tippingpoint.com/security/advisories/TSRT-07-04.html"
},
{
"title": "Page d\u0027accueil de l\u0027application LANDesk Management Suite :",
"url": "http://www.landesk.fr/Products/LDMS/"
}
],
"reference": "CERTA-2007-AVI-176",
"revisions": [
{
"description": "version initiale.",
"revision_date": "2007-04-16T00:00:00.000000"
}
],
"risks": [
{
"description": "Ex\u00e9cution de code arbitraire \u00e0 distance"
}
],
"summary": null,
"title": "Vuln\u00e9rabilit\u00e9 dans LANDesk Management Suite",
"vendor_advisories": [
{
"published_at": null,
"title": "Base de connaissances LANDesk 4142 du 13 avril 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.