5120 matches found
DSA-1062-1 kphone - insecure file creation
Bulletin has no description...
CVE-2006-2442
kphone 4.2 creates .qt/kphonerc with world-readable permissions, which allows local users to read usernames and SIP passwords...
CVE-2006-2442
kphone 4.2 creates .qt/kphonerc with world-readable permissions, which allows local users to read usernames and SIP passwords...
Design/Logic Flaw
kphone 4.2 creates .qt/kphonerc with world-readable permissions, which allows local users to read usernames and SIP passwords...
CVE-2006-2442
CVE-2006-2442 affects KPhone, a KDE VoIP client. The issue: kphone 4.2 creates the configuration file .qt/kphonerc with world-readable permissions, allowing local users to read usernames and SIP passwords. Connected advisories (Mandriva/MK, Debian DSA-1062-1, SUSE) confirm the root cause and stat...
CVE-2006-2442
kphone 4.2 creates .qt/kphonerc with world-readable permissions, which allows local users to read usernames and SIP passwords...
Session fixation
Multiple unspecified vulnerabilities in Linksys RT31P2 VoIP router allow remote attackers to cause a denial of service via malformed Session Initiation Protocol SIP messages...
CVE-2006-1973
Multiple unspecified vulnerabilities in Linksys RT31P2 VoIP router allow remote attackers to cause a denial of service via malformed Session Initiation Protocol SIP messages...
CVE-2006-1973
CVE-2006-1973 affects Linksys RT31P2 VoIP router. It describes multiple unspecified vulnerabilities allowing remote attackers to cause a denial of service via malformed SIP messages. NVD lists a Network attack vector, low complexity, no authentication, with a base score of 5.0 (Medium) and partia...
CVE-2006-1973
Multiple unspecified vulnerabilities in Linksys RT31P2 VoIP router allow remote attackers to cause a denial of service via malformed Session Initiation Protocol SIP messages...
CVE-2006-1973: Undefined Security Weakness
Multiple unspecified vulnerabilities in Linksys RT31P2 VoIP router allow remote attackers to cause a denial of service via malformed Session Initiation Protocol SIP messages...
Linksys RT31P2 SIP DoS
IP telephony hangs on invalid SIP message...
[SA19722] Linksys RT31P2 SIP Messages Denial of Service Vulnerabilities
TITLE: Linksys RT31P2 SIP Messages Denial of Service Vulnerabilities SECUNIA ADVISORY ID: SA19722 VERIFY ADVISORY: http://secunia.com/advisories/19722/ CRITICAL: Moderately critical IMPACT: DoS WHERE: From remote OPERATING SYSTEM: Linksys RT31P2 http://secunia.com/product/9456/ DESCRIPTION:...
Linksys RT31P2 VoIP router denial of service vulnerabilities
Overview The Linksys RT31P2 VoIP router contains several vulnerabilities that may allow a remote, unauthenticated attacker to cause a denial of service. Description The Linksys RT31P2 is a broadband router that includes Voice over Internet Protocol VoIP telephone functionality. The RT31P2 unit...
eStara SoftPhone Detection
The remote host is running eStara SoftPhone, a commercial SIP software client for Windows. C Tenable Network Security, Inc. include"compat.inc"; if description scriptid20957; scriptversion"1.14"; scriptcvsdate"Date: 2019/11/22"; scriptnameenglish:"eStara SoftPhone Detection";...
eStara SoftPhone SIP Packet SDP Data attribute Field Overflow
The version of SoftPhone installed on the remote host reportedly fails to properly handle SIP packets with long 'a=' lines in the SDP data. An unauthenticated, remote attacker may be able to exploit this flaw to overflow a buffer and execute arbitrary code on the remote host. C Tenable Network...
Cross site request forgery (csrf)
eStara SIP softphone allows remote attackers to cause a denial of service crash via an INVITE request with a Content-Length field that has more than 9 digits...
Design/Logic Flaw
eStara SIP softphone allows remote attackers to cause a denial of service crash via a SIP OPTIONS request with a negative Expires field...
Format string
Multiple format string vulnerabilities in eStara SIP softphone allow remote attackers to cause a denial of service hang via SIP INVITE requests with format string specifiers in the SDP session description, as demonstrated using 1 the field name, 2 the o field owner/creator and session identifier,...