CERTA-2009-AVI-255
Vulnerability from certfr_avis - Published: 2009-06-25 - Updated: 2009-06-25
Des vulnérabilités affectent des produits de vidéosurveillance Cisco et permettent à un utilisateur malveillant de provoquer un déni de service à distance ou de lire indûment des informations.
Description
Une vulnérabilité est présente dans Cisco Video Surveillance Stream Manager (CVE-2009-2045). Un utilisateur malveillant peut provoquer un redémarrage du système par le biais d'un paquet UDP particulier sur le port 37000.
Une vulnérabilité affecte les caméras IP de la série 2500, avec ou sans fil (CVE-2009-2046). Un utilisateur authentifié peut lire tout fichier présent sur la caméra au travers du serveur web embarqué, via le port 80 (HTTP) ou le port 443 (HTTPS).
Solution
Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation).
None| Vendor | Product | Description | ||
|---|---|---|---|---|
| Cisco | N/A | Cisco Video Surveillance 2500 Series IP Camera firmware, versions antérieures à la version 2.1. | ||
| Cisco | N/A | Cisco Video Surveillance Stream Manager for the Cisco Video Surveillance Services Platform, versions antérieures à la version 5.3 ; | ||
| Cisco | N/A | Cisco Video Surveillance Stream Manager for the Cisco Video Surveillance Integrated Services Platform, versions antérieures à la version 5.3 ; |
| Title | Publication Time | Tags | |
|---|---|---|---|
{
"$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
"affected_systems": [
{
"description": "Cisco Video Surveillance 2500 Series IP Camera firmware, versions ant\u00e9rieures \u00e0 la version 2.1.",
"product": {
"name": "N/A",
"vendor": {
"name": "Cisco",
"scada": false
}
}
},
{
"description": "Cisco Video Surveillance Stream Manager for the Cisco Video Surveillance Services Platform, versions ant\u00e9rieures \u00e0 la version 5.3 ;",
"product": {
"name": "N/A",
"vendor": {
"name": "Cisco",
"scada": false
}
}
},
{
"description": "Cisco Video Surveillance Stream Manager for the Cisco Video Surveillance Integrated Services Platform, versions ant\u00e9rieures \u00e0 la version 5.3 ;",
"product": {
"name": "N/A",
"vendor": {
"name": "Cisco",
"scada": false
}
}
}
],
"affected_systems_content": null,
"content": "## Description\n\nUne vuln\u00e9rabilit\u00e9 est pr\u00e9sente dans Cisco Video Surveillance Stream\nManager (CVE-2009-2045). Un utilisateur malveillant peut provoquer un\nred\u00e9marrage du syst\u00e8me par le biais d\u0027un paquet UDP particulier sur le\nport 37000.\n\nUne vuln\u00e9rabilit\u00e9 affecte les cam\u00e9ras IP de la s\u00e9rie 2500, avec ou sans\nfil (CVE-2009-2046). Un utilisateur authentifi\u00e9 peut lire tout fichier\npr\u00e9sent sur la cam\u00e9ra au travers du serveur web embarqu\u00e9, via le port 80\n(HTTP) ou le port 443 (HTTPS).\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-2009-2046",
"url": "https://www.cve.org/CVERecord?id=CVE-2009-2046"
},
{
"name": "CVE-2009-2045",
"url": "https://www.cve.org/CVERecord?id=CVE-2009-2045"
}
],
"initial_release_date": "2009-06-25T00:00:00",
"last_revision_date": "2009-06-25T00:00:00",
"links": [
{
"title": "Bulletin de s\u00e9curit\u00e9 Cisco 20090624-video du 24 juin 2009 :",
"url": "http://www.cisco.com/warp/public/707/cisco-sa-20090624-video.shtml"
}
],
"reference": "CERTA-2009-AVI-255",
"revisions": [
{
"description": "version initiale.",
"revision_date": "2009-06-25T00:00:00.000000"
}
],
"risks": [
{
"description": "D\u00e9ni de service \u00e0 distance"
},
{
"description": "Atteinte \u00e0 la confidentialit\u00e9 des donn\u00e9es"
}
],
"summary": "Des vuln\u00e9rabilit\u00e9s affectent des produits de vid\u00e9osurveillance Cisco et\npermettent \u00e0 un utilisateur malveillant de provoquer un d\u00e9ni de service\n\u00e0 distance ou de lire ind\u00fbment des informations.\n",
"title": "Vuln\u00e9rabilit\u00e9s de produits Cisco Video Surveillance",
"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.