Asterisk Open Source 1.2.x before 1.2.32, 1.4.x before 1.4.24.1, and 1.6.0.x before 1.6.0.8; Asterisk Business Edition A.x.x, B.x.x before B.2.5.8, C.1.x.x before C.1.10.5, and C.2.x.x before C.2.3.3; s800i 1.3.x before 1.3.0.2; and Trixbox PBX 2.6.1, when Digest authentication and authalwaysreject are enabled, generates different responses depending on whether a SIP username is valid, which allows remote attackers to enumerate valid usernames.

Several vulnerabilities have been discovered in asterisk, an Open Source PBX and telephony toolkit. The Common Vulnerabilities and Exposures project identifies the following problems :

  - CVE-2009-0041     It is possible to determine valid login names via     probing, due to the IAX2 response from asterisk     (AST-2009-001).

  - CVE-2008-3903     It is possible to determine a valid SIP username, when     Digest authentication and authalwaysreject are enabled     (AST-2009-003).

  - CVE-2009-3727     It is possible to determine a valid SIP username via     multiple crafted REGISTER messages (AST-2009-008).

  - CVE-2008-7220 CVE-2007-2383     It was discovered that asterisk contains an obsolete     copy of the Prototype JavaScript framework, which is     vulnerable to several security issues. This copy is     unused and now removed from asterisk (AST-2009-009).

  - CVE-2009-4055     It was discovered that it is possible to perform a     denial of service attack via RTP comfort noise payload     with a long data length (AST-2009-010).

The current version in oldstable is not supported by upstream anymore and is affected by several security issues. Backporting fixes for these and any future issues has become unfeasible and therefore we need to drop our security support for the version in oldstable. We recommend that all asterisk users upgrade to the stable distribution (lenny).

The remote host is affected by the vulnerability described in GLSA-200905-01 (Asterisk: Multiple vulnerabilities)

    Multiple vulnerabilities have been discovered in the IAX2 channel     driver when performing the 3-way handshake (CVE-2008-1897), when     handling a large number of POKE requests (CVE-2008-3263), when handling     authentication attempts (CVE-2008-5558) and when handling firmware     download (FWDOWNL) requests (CVE-2008-3264). Asterisk does also not     correctly handle SIP INVITE messages that lack a 'From' header     (CVE-2008-2119), and responds differently to a failed login attempt     depending on whether the user account exists (CVE-2008-3903,     CVE-2009-0041).
  Impact :

    Remote unauthenticated attackers could send specially crafted data to     Asterisk, possibly resulting in a Denial of Service via a daemon crash,     call-number exhaustion, CPU or traffic consumption. Remote     unauthenticated attackers could furthermore enumerate valid usernames     to facilitate brute-force login attempts.
  Workaround :

    There is no known workaround at this time.

ID	Name	Product	Family	Severity
44817	Debian DSA-1952-1 : asterisk - several vulnerabilities, end-of-life announcement in oldstable	Nessus	Debian Local Security Checks	high
38677	GLSA-200905-01 : Asterisk: Multiple vulnerabilities	Nessus	Gentoo Local Security Checks	high

Detections

Analytics

CVE-2008-3903

medium

Tenable Plugins

high

high