CERTA-2008-AVI-150

Vulnerability from certfr_avis - Published: 2008-03-19 - Updated: 2008-03-19

Plusieurs vulnérabilités ont été identifiées dans le gestionnaire de téléphonie sur IP Asterisk. Celles-ci peuvent être exploitées afin de perturber le service, lancer des appels à l'insu des utilisateurs ou écrire dans des zones de mémoire arbitraires.

Description

Plusieurs vulnérabilités ont été identifiées dans le gestionnaire de téléphonie sur IP Asterisk :

  • l'application ne manipulerait pas correctement certains contenus RTP, provoquant des écritures dans des zones arbitraires de la mémoire. Ces vulnérabilités peuvent être exploitées par le biais de toute requête SIP avec SDP (Session Description Protocol), comme INVITE.
  • il serait possible de lancer des appels non authentifiés à cause d'un mauvais contrôle du champs From de l'en-tête SIP par le pilote de canal SIP. Il s'agit du contournement de l'option de configuration allowguest.
  • le format de journalisation des messages n'est pas interprété correctement via l'interface ast_verbose.
  • la génération des identifiants de session (manager ID) dans le serveur AsteriskGUI HTTP serait relativement prévisible.

Ces vulnérabilités peuvent donc être exploitées afin de perturber le service, lancer des appels à l'insu des utilisateurs ou écrire dans des zones de mémoire arbitraires.

Solution

Se référer aux bulletins du projet Asterisk pour l'obtention des correctifs (cf. section Documentation).

None
Impacted products
Vendor Product Description
Asterisk Asterisk Asterisk Business Edition C.x.x pour les versions antérieures à C.1.6.1 ;
Asterisk Asterisk Asterisk Open Source 1.4.x pour les versions antérieures à 1.4.18.1 et 1.4.19-rc3 ;
Asterisk Asterisk s800i (Asterisk Appliance) 1.1.x pour les versions antérieures à 1.1.0.2.
Asterisk Asterisk Asterisk Open Source 1.6.x pour les versions antérieures à 1.6.0-beta6 ;
Asterisk Asterisk Asterisk Business Edition B.x.x pour les versions antérieures à B.2.5.1 ;
Asterisk Asterisk Asterisk Appliance Developer Kit (SVN) pour les versions antérieures à 1.4 revision 109386 ;
Asterisk N/A AsteriskNOW 1.0.x pour les versions antérieures à 1.0.2 ;
Asterisk Asterisk Asterisk Open Source 1.2.x pour les versions antérieures à 1.2.27 ;
References

Show details on source website
To clipboard 

{
  "$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
  "affected_systems": [
    {
      "description": "Asterisk Business Edition C.x.x pour les versions ant\u00e9rieures \u00e0 C.1.6.1 ;",
      "product": {
        "name": "Asterisk",
        "vendor": {
          "name": "Asterisk",
          "scada": false
        }
      }
    },
    {
      "description": "Asterisk Open Source 1.4.x pour les versions ant\u00e9rieures \u00e0 1.4.18.1 et 1.4.19-rc3 ;",
      "product": {
        "name": "Asterisk",
        "vendor": {
          "name": "Asterisk",
          "scada": false
        }
      }
    },
    {
      "description": "s800i (Asterisk Appliance) 1.1.x pour les versions ant\u00e9rieures \u00e0 1.1.0.2.",
      "product": {
        "name": "Asterisk",
        "vendor": {
          "name": "Asterisk",
          "scada": false
        }
      }
    },
    {
      "description": "Asterisk Open Source 1.6.x pour les versions ant\u00e9rieures \u00e0 1.6.0-beta6 ;",
      "product": {
        "name": "Asterisk",
        "vendor": {
          "name": "Asterisk",
          "scada": false
        }
      }
    },
    {
      "description": "Asterisk Business Edition B.x.x pour les versions ant\u00e9rieures \u00e0 B.2.5.1 ;",
      "product": {
        "name": "Asterisk",
        "vendor": {
          "name": "Asterisk",
          "scada": false
        }
      }
    },
    {
      "description": "Asterisk Appliance Developer Kit (SVN) pour les versions ant\u00e9rieures \u00e0 1.4 revision 109386 ;",
      "product": {
        "name": "Asterisk",
        "vendor": {
          "name": "Asterisk",
          "scada": false
        }
      }
    },
    {
      "description": "AsteriskNOW 1.0.x pour les versions ant\u00e9rieures \u00e0 1.0.2 ;",
      "product": {
        "name": "N/A",
        "vendor": {
          "name": "Asterisk",
          "scada": false
        }
      }
    },
    {
      "description": "Asterisk Open Source 1.2.x pour les versions ant\u00e9rieures \u00e0 1.2.27 ;",
      "product": {
        "name": "Asterisk",
        "vendor": {
          "name": "Asterisk",
          "scada": false
        }
      }
    }
  ],
  "affected_systems_content": null,
  "content": "## Description\n\nPlusieurs vuln\u00e9rabilit\u00e9s ont \u00e9t\u00e9 identifi\u00e9es dans le gestionnaire de\nt\u00e9l\u00e9phonie sur IP Asterisk :\n\n-   l\u0027application ne manipulerait pas correctement certains contenus\n    RTP, provoquant des \u00e9critures dans des zones arbitraires de la\n    m\u00e9moire. Ces vuln\u00e9rabilit\u00e9s peuvent \u00eatre exploit\u00e9es par le biais de\n    toute requ\u00eate SIP avec SDP (Session Description Protocol), comme\n    INVITE.\n-   il serait possible de lancer des appels non authentifi\u00e9s \u00e0 cause\n    d\u0027un mauvais contr\u00f4le du champs From de l\u0027en-t\u00eate SIP par le pilote\n    de canal SIP. Il s\u0027agit du contournement de l\u0027option de\n    configuration allowguest.\n-   le format de journalisation des messages n\u0027est pas interpr\u00e9t\u00e9\n    correctement via l\u0027interface ast_verbose.\n-   la g\u00e9n\u00e9ration des identifiants de session (manager ID) dans le\n    serveur AsteriskGUI HTTP serait relativement pr\u00e9visible.\n\nCes vuln\u00e9rabilit\u00e9s peuvent donc \u00eatre exploit\u00e9es afin de perturber le\nservice, lancer des appels \u00e0 l\u0027insu des utilisateurs ou \u00e9crire dans des\nzones de m\u00e9moire arbitraires.\n\n## Solution\n\nSe r\u00e9f\u00e9rer aux bulletins du projet Asterisk pour l\u0027obtention des\ncorrectifs (cf. section Documentation).\n",
  "cves": [
    {
      "name": "CVE-2008-1333",
      "url": "https://www.cve.org/CVERecord?id=CVE-2008-1333"
    },
    {
      "name": "CVE-2008-1289",
      "url": "https://www.cve.org/CVERecord?id=CVE-2008-1289"
    },
    {
      "name": "CVE-2008-1390",
      "url": "https://www.cve.org/CVERecord?id=CVE-2008-1390"
    },
    {
      "name": "CVE-2008-1332",
      "url": "https://www.cve.org/CVERecord?id=CVE-2008-1332"
    }
  ],
  "initial_release_date": "2008-03-19T00:00:00",
  "last_revision_date": "2008-03-19T00:00:00",
  "links": [
    {
      "title": "Bulletin de s\u00e9curit\u00e9 AST-2008-002 du projet Asterisk du 18    mars 2008 :",
      "url": "http://downloads.digium.com/pub/security/AST-2008-002.html"
    },
    {
      "title": "Bulletin de s\u00e9curit\u00e9 AST-2008-003 du projet Asterisk du 18    mars 2008 :",
      "url": "http://downloads.digium.com/pub/security/AST-2008-003.html"
    },
    {
      "title": "Bulletin de s\u00e9curit\u00e9 AST-2008-004 du projet Asterisk du 18    mars 2008 :",
      "url": "http://downloads.digium.com/pub/security/AST-2008-004.html"
    },
    {
      "title": "Bulletin de s\u00e9curit\u00e9 AST-2008-005 du projet Asterisk du 18    mars 2008 :",
      "url": "http://downloads.digium.com/pub/security/AST-2008-005.html"
    }
  ],
  "reference": "CERTA-2008-AVI-150",
  "revisions": [
    {
      "description": "version initiale.",
      "revision_date": "2008-03-19T00:00:00.000000"
    }
  ],
  "risks": [
    {
      "description": "D\u00e9ni de service \u00e0 distance"
    },
    {
      "description": "Atteinte \u00e0 l\u0027int\u00e9grit\u00e9 des donn\u00e9es"
    },
    {
      "description": "Contournement de la politique de s\u00e9curit\u00e9"
    }
  ],
  "summary": "Plusieurs vuln\u00e9rabilit\u00e9s ont \u00e9t\u00e9 identifi\u00e9es dans le gestionnaire de\nt\u00e9l\u00e9phonie sur IP Asterisk. Celles-ci peuvent \u00eatre exploit\u00e9es afin de\nperturber le service, lancer des appels \u00e0 l\u0027insu des utilisateurs ou\n\u00e9crire dans des zones de m\u00e9moire arbitraires.\n",
  "title": "Multiples vuln\u00e9rabilit\u00e9s dans Asterisk",
  "vendor_advisories": [
    {
      "published_at": null,
      "title": "Bulletins de s\u00e9curit\u00e9 Asterisk publi\u00e9s le 18 mars 2008",
      "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.