CERTA-2008-AVI-273
Vulnerability from certfr_avis - Published: 2008-05-28 - Updated: 2008-05-28
Des vulnérabilités ont été identifiées dans les applications de maintenance de disques EMC AlphaStor. Elles peuvent être exploitées par une personne malveillante distante afin d'exécuter du code arbitraire.
Description
Des vulnérabilités ont été identifiées dans les applications de maintenance de disques EMC AlphaStor :
- certaines concernent le service Server Agent et en particulier le processus Command Line Interface en écoute par défaut sur le port 41025/tcp. Ces vulnérabilités peuvent être exploitées par une personne malveillante distante qui pourrait se connecter au port et envoyer une trame spécialement construite.
- une autre concerne le service Library Manager et en particulier le processus robotd en écoute par défaut sur le port 3500/tcp. Cette vulnérabilité peut être exploitée par une personne malveillante distante qui pourrait se connecter au port et envoyer une requête spécialement construite.
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": "EMC AlphaStor version 3.1 SP1 ainsi que celles ant\u00e9rieures.",
"product": {
"name": "N/A",
"vendor": {
"name": "N/A",
"scada": false
}
}
}
],
"affected_systems_content": null,
"content": "## Description\n\nDes vuln\u00e9rabilit\u00e9s ont \u00e9t\u00e9 identifi\u00e9es dans les applications de\nmaintenance de disques EMC AlphaStor :\n\n- certaines concernent le service Server Agent et en particulier le\n processus Command Line Interface en \u00e9coute par d\u00e9faut sur le port\n 41025/tcp. Ces vuln\u00e9rabilit\u00e9s peuvent \u00eatre exploit\u00e9es par une\n personne malveillante distante qui pourrait se connecter au port et\n envoyer une trame sp\u00e9cialement construite.\n- une autre concerne le service Library Manager et en particulier le\n processus robotd en \u00e9coute par d\u00e9faut sur le port 3500/tcp. Cette\n vuln\u00e9rabilit\u00e9 peut \u00eatre exploit\u00e9e par une personne malveillante\n distante qui pourrait se connecter au port et envoyer une requ\u00eate\n sp\u00e9cialement construite.\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-2008-2157",
"url": "https://www.cve.org/CVERecord?id=CVE-2008-2157"
},
{
"name": "CVE-2008-2158",
"url": "https://www.cve.org/CVERecord?id=CVE-2008-2158"
}
],
"initial_release_date": "2008-05-28T00:00:00",
"last_revision_date": "2008-05-28T00:00:00",
"links": [
{
"title": "Bulletin de s\u00e9curit\u00e9 iDefense 703 du 27 mai 2008 :",
"url": "http://www.idefense.com/ntelligence/vulnerabilities/display.php?id=703"
},
{
"title": "Base d\u0027informations de EMC pour clients, article emc186391 :",
"url": "http://powerlink.emc.com"
},
{
"title": "Site officiel EMC AlphaStor :",
"url": "http://www.emc.com/products/detail/software/alphastor.htm"
},
{
"title": "Bulletin de s\u00e9curit\u00e9 iDefense 702 du 27 mai 2008 :",
"url": "http://www.idefense.com/ntelligence/vulnerabilities/display.php?id=702"
}
],
"reference": "CERTA-2008-AVI-273",
"revisions": [
{
"description": "version initiale.",
"revision_date": "2008-05-28T00:00:00.000000"
}
],
"risks": [
{
"description": "Ex\u00e9cution de code arbitraire \u00e0 distance"
},
{
"description": "Contournement de la politique de s\u00e9curit\u00e9"
}
],
"summary": "Des vuln\u00e9rabilit\u00e9s ont \u00e9t\u00e9 identifi\u00e9es dans les applications de\nmaintenance de disques EMC AlphaStor. Elles peuvent \u00eatre exploit\u00e9es par\nune personne malveillante distante afin d\u0027ex\u00e9cuter du code arbitraire.\n",
"title": "Vuln\u00e9rabilit\u00e9s d\u0027EMC AlphaStor",
"vendor_advisories": [
{
"published_at": null,
"title": "Bulletins de s\u00e9curit\u00e9 iDefense 702 et 703 du 27 mai 2008",
"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.