CERTA-2012-AVI-209
Vulnerability from certfr_avis - Published: - Updated:
Dans certains commutateurs HP, une carte mémoire flash contient un virus. La réutilisation de cette dernière dans un ordinateur peut infecter celui-ci.
Solution
Se référer au bulletin de sécurité de l'éditeur pour l'obtention de solutions (cf. section Documentation).
Certains commutateurs HP ProCurve 5400 zl, achetés après le 30 avril 2011.
La liste des numéros de série concernés est incluse dans le bulletin de l'éditeur (voir section Documentation).
| Vendor | Product | Description |
|---|
| Title | Publication Time | Tags | |||
|---|---|---|---|---|---|
|
|||||
{
"$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
"affected_systems": [],
"affected_systems_content": "\u003cp\u003eCertains commutateurs HP ProCurve 5400 zl, achet\u00e9s apr\u00e8s le 30 avril 2011. \u003cP\u003eLa liste des num\u00e9ros de s\u00e9rie concern\u00e9s est incluse dans le bulletin de l\u0027\u00e9diteur (voir section Documentation).\u003c/P\u003e\u003c/p\u003e",
"content": "## Solution\n\nSe r\u00e9f\u00e9rer au bulletin de s\u00e9curit\u00e9 de l\u0027\u00e9diteur pour l\u0027obtention de\nsolutions (cf. section Documentation).\n",
"cves": [
{
"name": "CVE-2012-0133",
"url": "https://www.cve.org/CVERecord?id=CVE-2012-0133"
}
],
"links": [],
"reference": "CERTA-2012-AVI-209",
"revisions": [
{
"description": "version initiale.",
"revision_date": "2012-04-11T00:00:00.000000"
}
],
"risks": [
{
"description": "Atteinte \u00e0 l\u0027int\u00e9grit\u00e9 des donn\u00e9es"
}
],
"summary": "Dans certains commutateurs HP, une carte m\u00e9moire flash contient un\nvirus. La r\u00e9utilisation de cette derni\u00e8re dans un ordinateur peut\ninfecter celui-ci.\n",
"title": "Pr\u00e9sence d\u0027un virus dans certains commutateurs HP",
"vendor_advisories": [
{
"published_at": null,
"title": "Bulletin de s\u00e9curit\u00e9 HP c03249176 du 10 avril 2012",
"url": "http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c03249176"
}
]
}
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.