CERTA-2006-AVI-057
Vulnerability from certfr_avis - Published: 2006-02-07 - Updated: 2006-02-07None
Description
Plusieurs vulnérabilités affectent le module CAM présent dans plusieurs produits de Computer Associates. Ces vulnérabilités, une fois exploitées, conduisent à un déni des service du produit concerné.
Solution
Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation).
- Advantage Data Transport 3.0 ;
- BrightStor SAN Manager 1.1 ;
- BrightStor SAN Manager 1.1 SP1 ;
- BrightStor SAN Manager 1.1 SP2 ;
- BrightStor SAN Manager 11.1 ;
- BrightStor Portal 11.1 ;
- CleverPath OLAP 5.1 ;
- CleverPath ECM 3.5 ;
- CleverPath Predictive Analysis Server 2.0 ;
- CleverPath Predictive Analysis Server 3.0 ;
- CleverPath Aion 10.0 ;
- eTrust Admin 2.01 ;
- eTrust Admin 2.04 ;
- eTrust Admin 2.07 ;
- eTrust Admin 2.09 ;
- eTrust Admin 8.0 ;
- eTrust Admin 8.1 ;
- Unicenter Application Performance Monitor 3.0 ;
- Unicenter Application Performance Monitor 3.5 ;
- Unicenter Asset Management 3.1 ;
- Unicenter Asset Management 3.2 ;
- Unicenter Asset Management 3.2 SP1 ;
- Unicenter Asset Management 3.2 SP2 ;
- Unicenter Asset Management 4.0 ;
- Unicenter Asset Management 4.0 SP1 ;
- Unicenter Data Transport Option 2.0 ;
- Unicenter Enterprise Job Manager 1.0 SP1 ;
- Unicenter Enterprise Job Manager 1.0 SP2 ;
- Unicenter Jasmine 3.0 ;
- Unicenter Management for WebSphere MQ 3.5 ;
- Unicenter Management for Microsoft Exchange 4.0 ;
- Unicenter Management for Microsoft Exchange 4.1 ;
- Unicenter Management for Lotus Notes/Domino 4.0 ;
- Unicenter Management for Web Servers 5 ;
- Unicenter Management for Web Servers 5.0.1 ;
- Unicenter NSM 3.0 ;
- Unicenter NSM 3.1 ;
- Unicenter NSM Wireless Network Management Option 3.0 ;
- Unicenter Remote Control 6.0 ;
- Unicenter Remote Control 6.0 SP1 ;
- Unicenter Service Level Management 3.0 ;
- Unicenter Service Level Management 3.0.1 ;
- Unicenter Service Level Management 3.0.2 ;
- Unicenter Service Level Management 3.5 ;
- Unicenter Software Delivery 3.0 ;
- Unicenter Software Delivery 3.1 ;
- Unicenter Software Delivery 3.1 SP1 ;
- Unicenter Software Delivery 3.1 SP2 ;
- Unicenter Software Delivery 4.0 ;
- Unicenter Software Delivery 4.0 SP1 ;
- Unicenter TNG 2.1 ;
- Unicenter TNG 2.2 ;
- Unicenter TNG 2.4 ;
- Unicenter TNG 2.4.2 ;
- Unicenter TNG JPN 2.2.
Ces Produits sont vulnérables dans leurs version pour les systèmes d'exploitation suivant : AIX, DG Intel, DG Motorola, DYNIX, OSF1, HP-UX, IRIX, Linux Intel, Linux s/390, Solaris Intel, Solaris Sparc, UnixWare et Windows.
| Vendor | Product | Description |
|---|
| Title | Publication Time | Tags | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||
{
"$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
"affected_systems": [],
"affected_systems_content": "\u003cUL\u003e \u003cLI\u003eAdvantage Data Transport 3.0 ;\u003c/LI\u003e \u003cLI\u003eBrightStor SAN Manager 1.1 ;\u003c/LI\u003e \u003cLI\u003eBrightStor SAN Manager 1.1 SP1 ;\u003c/LI\u003e \u003cLI\u003eBrightStor SAN Manager 1.1 SP2 ;\u003c/LI\u003e \u003cLI\u003eBrightStor SAN Manager 11.1 ;\u003c/LI\u003e \u003cLI\u003eBrightStor Portal 11.1 ;\u003c/LI\u003e \u003cLI\u003eCleverPath OLAP 5.1 ;\u003c/LI\u003e \u003cLI\u003eCleverPath ECM 3.5 ;\u003c/LI\u003e \u003cLI\u003eCleverPath Predictive Analysis Server 2.0 ;\u003c/LI\u003e \u003cLI\u003eCleverPath Predictive Analysis Server 3.0 ;\u003c/LI\u003e \u003cLI\u003eCleverPath Aion 10.0 ;\u003c/LI\u003e \u003cLI\u003eeTrust Admin 2.01 ;\u003c/LI\u003e \u003cLI\u003eeTrust Admin 2.04 ;\u003c/LI\u003e \u003cLI\u003eeTrust Admin 2.07 ;\u003c/LI\u003e \u003cLI\u003eeTrust Admin 2.09 ;\u003c/LI\u003e \u003cLI\u003eeTrust Admin 8.0 ;\u003c/LI\u003e \u003cLI\u003eeTrust Admin 8.1 ;\u003c/LI\u003e \u003cLI\u003eUnicenter Application Performance Monitor 3.0 ;\u003c/LI\u003e \u003cLI\u003eUnicenter Application Performance Monitor 3.5 ;\u003c/LI\u003e \u003cLI\u003eUnicenter Asset Management 3.1 ;\u003c/LI\u003e \u003cLI\u003eUnicenter Asset Management 3.2 ;\u003c/LI\u003e \u003cLI\u003eUnicenter Asset Management 3.2 SP1 ;\u003c/LI\u003e \u003cLI\u003eUnicenter Asset Management 3.2 SP2 ;\u003c/LI\u003e \u003cLI\u003eUnicenter Asset Management 4.0 ;\u003c/LI\u003e \u003cLI\u003eUnicenter Asset Management 4.0 SP1 ;\u003c/LI\u003e \u003cLI\u003eUnicenter Data Transport Option 2.0 ;\u003c/LI\u003e \u003cLI\u003eUnicenter Enterprise Job Manager 1.0 SP1 ;\u003c/LI\u003e \u003cLI\u003eUnicenter Enterprise Job Manager 1.0 SP2 ;\u003c/LI\u003e \u003cLI\u003eUnicenter Jasmine 3.0 ;\u003c/LI\u003e \u003cLI\u003eUnicenter Management for WebSphere MQ 3.5 ;\u003c/LI\u003e \u003cLI\u003eUnicenter Management for Microsoft Exchange 4.0 ;\u003c/LI\u003e \u003cLI\u003eUnicenter Management for Microsoft Exchange 4.1 ;\u003c/LI\u003e \u003cLI\u003eUnicenter Management for Lotus Notes/Domino 4.0 ;\u003c/LI\u003e \u003cLI\u003eUnicenter Management for Web Servers 5 ;\u003c/LI\u003e \u003cLI\u003eUnicenter Management for Web Servers 5.0.1 ;\u003c/LI\u003e \u003cLI\u003eUnicenter NSM 3.0 ;\u003c/LI\u003e \u003cLI\u003eUnicenter NSM 3.1 ;\u003c/LI\u003e \u003cLI\u003eUnicenter NSM Wireless Network Management Option 3.0 ;\u003c/LI\u003e \u003cLI\u003eUnicenter Remote Control 6.0 ;\u003c/LI\u003e \u003cLI\u003eUnicenter Remote Control 6.0 SP1 ;\u003c/LI\u003e \u003cLI\u003eUnicenter Service Level Management 3.0 ;\u003c/LI\u003e \u003cLI\u003eUnicenter Service Level Management 3.0.1 ;\u003c/LI\u003e \u003cLI\u003eUnicenter Service Level Management 3.0.2 ;\u003c/LI\u003e \u003cLI\u003eUnicenter Service Level Management 3.5 ;\u003c/LI\u003e \u003cLI\u003eUnicenter Software Delivery 3.0 ;\u003c/LI\u003e \u003cLI\u003eUnicenter Software Delivery 3.1 ;\u003c/LI\u003e \u003cLI\u003eUnicenter Software Delivery 3.1 SP1 ;\u003c/LI\u003e \u003cLI\u003eUnicenter Software Delivery 3.1 SP2 ;\u003c/LI\u003e \u003cLI\u003eUnicenter Software Delivery 4.0 ;\u003c/LI\u003e \u003cLI\u003eUnicenter Software Delivery 4.0 SP1 ;\u003c/LI\u003e \u003cLI\u003eUnicenter TNG 2.1 ;\u003c/LI\u003e \u003cLI\u003eUnicenter TNG 2.2 ;\u003c/LI\u003e \u003cLI\u003eUnicenter TNG 2.4 ;\u003c/LI\u003e \u003cLI\u003eUnicenter TNG 2.4.2 ;\u003c/LI\u003e \u003cLI\u003eUnicenter TNG JPN 2.2. \u003cP\u003eCes Produits sont vuln\u00e9rables dans leurs version pour les syst\u00e8mes d\u0027exploitation suivant : AIX, DG Intel, DG Motorola, DYNIX, OSF1, HP-UX, IRIX, Linux Intel, Linux s/390, Solaris Intel, Solaris Sparc, UnixWare et Windows.\u003c/P\u003e \u003c/LI\u003e \u003c/UL\u003e",
"content": "## Description\n\nPlusieurs vuln\u00e9rabilit\u00e9s affectent le module CAM pr\u00e9sent dans plusieurs\nproduits de Computer Associates. Ces vuln\u00e9rabilit\u00e9s, une fois\nexploit\u00e9es, conduisent \u00e0 un d\u00e9ni des service du produit concern\u00e9.\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-0530",
"url": "https://www.cve.org/CVERecord?id=CVE-2006-0530"
},
{
"name": "CVE-2006-0529",
"url": "https://www.cve.org/CVERecord?id=CVE-2006-0529"
}
],
"initial_release_date": "2006-02-07T00:00:00",
"last_revision_date": "2006-02-07T00:00:00",
"links": [
{
"title": "R\u00e9f\u00e9rences et correctifs de l\u0027\u00e9diteur :",
"url": "http://supportconnectw.ca.com/public/ca_common_docs/camessagsecurity_cam107fixes.asp"
},
{
"title": "R\u00e9f\u00e9rences et correctifs de l\u0027\u00e9diteur :",
"url": "http://supportconnectw.ca.com/public/ca_common_docs/camessagsecurity_cam111fixes.asp"
}
],
"reference": "CERTA-2006-AVI-057",
"revisions": [
{
"description": "version initiale.",
"revision_date": "2006-02-07T00:00:00.000000"
}
],
"risks": [
{
"description": "D\u00e9ni de service \u00e0 distance"
}
],
"summary": null,
"title": "Multiples vuln\u00e9rabilit\u00e9s dans les produits Computer Associate",
"vendor_advisories": [
{
"published_at": null,
"title": "Bulletin de s\u00e9curit\u00e9 de Computer Associate",
"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.