CERTA-2011-AVI-263

Vulnerability from certfr_avis - Published: 2011-04-28 - Updated: 2011-04-28

De multiples vulnérabilités dans Cisco Unified Communications Manager permettent des injections SQL, des dénis de service à distance ou le dépôt d'un fichier.

Description

De multiples vulnérabilités ont été découvertes dans Cisco Unified Communications Manager :

  • trois failles liées au traitement des messages SIP permettent de réaliser un déni de service à distance (CVE-2011-1604, CVE-2011-1605 et CVE-2011-1606) ;
  • un utilisateur authentifié qui parvient à intercepter le trafic réseau peut déposer un fichier malveillant sur le système (CVE-2011-1607) ;
  • des injections SQL sont possibles, ce qui permet la modification de la configuration du système, ainsi que l'ajout ou la suppression d'utilisateurs. L'une de ces deux vulnérabilités nécessite une authentification préalable (CVE-2011-1609 et CVE-2011-1610).

Solution

Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation).

Cisco Unified Communications Manager versions 6.x, 7.x et 8.x.

Impacted products
Vendor Product Description
References

Show details on source website
To clipboard 

{
  "$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
  "affected_systems": [],
  "affected_systems_content": "\u003cP\u003e\u003cSPAN class=\"textit\"\u003eCisco Unified Communications  Manager\u003c/SPAN\u003e versions 6.x, 7.x et 8.x.\u003c/P\u003e",
  "content": "## Description\n\nDe multiples vuln\u00e9rabilit\u00e9s ont \u00e9t\u00e9 d\u00e9couvertes dans Cisco Unified\nCommunications Manager :\n\n-   trois failles li\u00e9es au traitement des messages SIP permettent de\n    r\u00e9aliser un d\u00e9ni de service \u00e0 distance (CVE-2011-1604, CVE-2011-1605\n    et CVE-2011-1606) ;\n-   un utilisateur authentifi\u00e9 qui parvient \u00e0 intercepter le trafic\n    r\u00e9seau peut d\u00e9poser un fichier malveillant sur le syst\u00e8me\n    (CVE-2011-1607) ;\n-   des injections SQL sont possibles, ce qui permet la modification de\n    la configuration du syst\u00e8me, ainsi que l\u0027ajout ou la suppression\n    d\u0027utilisateurs. L\u0027une de ces deux vuln\u00e9rabilit\u00e9s n\u00e9cessite une\n    authentification pr\u00e9alable (CVE-2011-1609 et CVE-2011-1610).\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-2011-1605",
      "url": "https://www.cve.org/CVERecord?id=CVE-2011-1605"
    },
    {
      "name": "CVE-2011-1607",
      "url": "https://www.cve.org/CVERecord?id=CVE-2011-1607"
    },
    {
      "name": "CVE-2011-1610",
      "url": "https://www.cve.org/CVERecord?id=CVE-2011-1610"
    },
    {
      "name": "CVE-2011-1604",
      "url": "https://www.cve.org/CVERecord?id=CVE-2011-1604"
    },
    {
      "name": "CVE-2011-1606",
      "url": "https://www.cve.org/CVERecord?id=CVE-2011-1606"
    },
    {
      "name": "CVE-2011-1609",
      "url": "https://www.cve.org/CVERecord?id=CVE-2011-1609"
    }
  ],
  "initial_release_date": "2011-04-28T00:00:00",
  "last_revision_date": "2011-04-28T00:00:00",
  "links": [
    {
      "title": "Bulletin de s\u00e9curit\u00e9 Cisco 20110427-cucm du 27 avril 2011 :",
      "url": "http://www.cisco.com/warp/public/707/cisco-sa-20110427-cucm.shtml"
    }
  ],
  "reference": "CERTA-2011-AVI-263",
  "revisions": [
    {
      "description": "version initiale.",
      "revision_date": "2011-04-28T00:00:00.000000"
    }
  ],
  "risks": [
    {
      "description": "D\u00e9ni de service \u00e0 distance"
    },
    {
      "description": "D\u00e9p\u00f4t de fichier"
    },
    {
      "description": "Injection SQL"
    }
  ],
  "summary": "De multiples vuln\u00e9rabilit\u00e9s dans \u003cspan class=\"textit\"\u003eCisco Unified\nCommunications Manager\u003c/span\u003e permettent des injections SQL, des d\u00e9nis\nde service \u00e0 distance ou le d\u00e9p\u00f4t d\u0027un fichier.\n",
  "title": "Multiples vuln\u00e9rabilit\u00e9s dans Cisco Unified Communications Manager",
  "vendor_advisories": [
    {
      "published_at": null,
      "title": "Bulletin de s\u00e9curit\u00e9 cisco-sa-20110427-cucm du 27 avril 2011",
      "url": null
    }
  ]
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




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.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

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

JSON
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…




    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.