Gentoo Logo

Asterisk: Multiple vulnerabilities

Content:

1.  Gentoo Linux Security Advisory

Version Information

Advisory Reference GLSA 200804-13 / asterisk
Release Date April 14, 2008
Latest Revision April 14, 2008: 01
Impact normal
Exploitable remote
Package Vulnerable versions Unaffected versions Architecture(s)
net-misc/asterisk < 1.2.27 >= 1.2.27 All supported architectures

Related bugreports: #200792, #202733, #213883

Synopsis

Multiple vulnerabilities have been found in Asterisk allowing for SQL injection, session hijacking and unauthorized usage.

2.  Impact Information

Background

Asterisk is an open source telephony engine and tool kit.

Description

Asterisk upstream developers reported multiple vulnerabilities:

  • The Call Detail Record Postgres logging engine (cdr_pgsql) does not correctly escape the ANI and DNIS arguments before using them in SQL statements (CVE-2007-6170).
  • When using database-based registrations ("realtime") and host-based authentication, Asterisk does not check the IP address when the username is correct and there is no password provided (CVE-2007-6430).
  • The SIP channel driver does not correctly determine if authentication is required (CVE-2008-1332).

Impact

Remote authenticated attackers could send specially crafted data to Asterisk to execute arbitrary SQL commands and compromise the administrative database. Remote unauthenticated attackers could bypass authentication using a valid username to hijack other user's sessions, and establish sessions on the SIP channel without authentication.

3.  Resolution Information

Workaround

There is no known workaround at this time.

Resolution

All Asterisk users should upgrade to the latest version:

Code Listing 3.1: Resolution

# emerge --sync
# emerge --ask --oneshot --verbose ">=net-misc/asterisk-1.2.27"

4.  References



Print

Page updated April 14, 2008

Summary: This is a Gentoo Linux Security Advisory

Security Team
Contact Address

Donate to support our development efforts.

Copyright 2001-2014 Gentoo Foundation, Inc. Questions, Comments? Contact us.