Show filters
56 Total Results
Displaying 51-56 of 56
Sort by:
Attacker Value
Unknown
CVE-2007-2294
Disclosure Date: April 26, 2007 (last updated October 04, 2023)
The Manager Interface in Asterisk before 1.2.18 and 1.4.x before 1.4.3 allows remote attackers to cause a denial of service (crash) by using MD5 authentication to authenticate a user that does not have a password defined in manager.conf, resulting in a NULL pointer dereference.
0
Attacker Value
Unknown
CVE-2007-1594
Disclosure Date: March 22, 2007 (last updated October 04, 2023)
The handle_response function in chan_sip.c in Asterisk before 1.2.17 and 1.4.x before 1.4.2 allows remote attackers to cause a denial of service (crash) via a SIP Response code 0 in a SIP packet.
0
Attacker Value
Unknown
CVE-2007-1595
Disclosure Date: March 22, 2007 (last updated October 04, 2023)
The Asterisk Extension Language (AEL) in pbx/pbx_ael.c in Asterisk does not properly generate extensions, which allows remote attackers to execute arbitrary extensions and have an unknown impact by specifying an invalid extension in a certain form.
0
Attacker Value
Unknown
CVE-2007-1561
Disclosure Date: March 21, 2007 (last updated October 04, 2023)
The channel driver in Asterisk before 1.2.17 and 1.4.x before 1.4.2 allows remote attackers to cause a denial of service (crash) via a SIP INVITE message with an SDP containing one valid and one invalid IP address.
0
Attacker Value
Unknown
CVE-2006-2020
Disclosure Date: April 25, 2006 (last updated October 04, 2023)
Asterisk Recording Interface (ARI) in Asterisk@Home before 2.8 stores recordings/includes/main.conf under the web document root with insufficient access control, which allows remote attackers to obtain password information.
0
Attacker Value
Unknown
CVE-2006-2021
Disclosure Date: April 25, 2006 (last updated October 04, 2023)
Absolute path traversal vulnerability in recordings/misc/audio.php in the Asterisk Recording Interface (ARI) web interface in Asterisk@Home before 2.8 allows remote attackers to read arbitrary MP3, WAV, and GSM files via a full pathname in the recording parameter. NOTE: this issue can also be used to determine existence of files.
0