var-200312-0087
Vulnerability from variot
The Session Initiation Protocol (SIP) implementation in Ingate Firewall and Ingate SIParator before 3.1.3 allows remote attackers to cause a denial of service and possibly execute arbitrary code via crafted INVITE messages, as demonstrated by the OUSPG PROTOS c07-sip test suite. Oulu University has discovered a variety of vulnerabilities affecting products that implement the Session Initiation Protocol (SIP). These vulnerabiltites affect a wide variety of products, with impacts ranging from denial of service to execution of arbitrary code. SIP is used in Voice Over Internet (VoIP), instant messaging, telephony, and various other applications and devices. These issues may be exploited to cause a denial of services in devices which implement the protocol. It has also been reported that unauthorized access to devices may occur under some circumstances. These issues are related to handling of SIP INVITE messages. Exploitation and the specific nature of each vulnerability may depend on the particular implementation. SIP is part of the IETF standards process, and it builds on foundations such as SMTP (Simple Mail Transfer Protocol) and HTTP (Hypertext Transfer Protocol). It is used to establish, change and terminate calls between users based on IP networks. These vulnerabilities include buffer overflow and improper handling of request messages containing illegal headers, which can cause buffer overflow on devices running this protocol, resulting in denial of service, and may also cause unauthorized access or remote execution of arbitrary commands. Cisco IP Telephony Modules 7940 and 7960 have these vulnerabilities, which can cause denial of service, and are documented in Cisco Bug IDs CSCdz26317, CSCdz29003, CSCdz29033, and CSCdz29041. Versions running Cisco IOS 12.2T train or any 12.2 \'\'X\'\' train will reset due to incorrect handling of SIP protocols containing illegal headers. These vulnerabilities are documented in Cisco Bug IDs CSCdz39284 and CSCdz41124. Devices running an IOS version with this vulnerability and configured as a SIP gateway will cause the vulnerability generated by CSCdz39284. However, any version of IOS running with this vulnerability and configured in NAT mode will cause the vulnerability described by CSCdz41124 when SIP uses UDP for transmission. The Cisco PIX firewall resets when it receives a fragmented SIP INVITE message. Since the current SIP patch does not support fragmented SIP messages, the vulnerability described by Cisco Bug ID CSCdx47789 is temporarily patched by dropping SIP fragments.
-----BEGIN PGP SIGNED MESSAGE-----
CERT Advisory CA-2003-06 Multiple vulnerabilities in implementations of the Session Initiation Protocol (SIP)
Original release date: February 21, 2003 Last revised: -- Source: CERT/CC
A complete revision history can be found at the end of this file. Other systems making use of SIP may also be vulnerable but were not specifically tested. Not all SIP implementations are affected. See Vendor Information for details from vendors who have provided feedback for this advisory.
In addition to the vendors who provided feedback for this advisory, a list of vendors whom CERT/CC contacted regarding these problems is available from VU#528719. These vulnerabilities may allow an attacker to gain unauthorized privileged access, cause denial-of-service attacks, or cause unstable system behavior. If your site uses SIP-enabled products in any capacity, the CERT/CC encourages you to read this advisory and follow the advice provided in the Solution section below.
I. SIP is a text-based protocol for initiating communication and data sessions between users.
The Oulu University Secure Programming Group (OUSPG) previously conducted research into vulnerabilities in LDAP, culminating in CERT Advisory CA-2001-18, and SNMP, resulting in CERT Advisory CA-2002-03.
OUSPG's most recent research focused on a subset of SIP related to the INVITE message, which SIP agents and proxies are required to accept in order to set up sessions. Note that "throttling" is an expected behavior.
Specifications for the Session Initiation Protocol are available in RFC3261:
http://www.ietf.org/rfc/rfc3261.txt
OUSPG has established the following site with detailed documentation regarding SIP and the implementation test results from the test suite:
http://www.ee.oulu.fi/research/ouspg/protos/testing/c07/sip/
The IETF Charter page for SIP is available at
http://www.ietf.org/html.charters/sip-charter.html
II. Impact
Exploitation of these vulnerabilities may result in denial-of-service conditions, service interruptions, and in some cases may allow an attacker to gain unauthorized access to the affected device. Specific impacts will vary from product to product.
III. Solution
Many of the mitigation steps recommended below may have significant impact on your everyday network operations and/or network architecture. Ensure that any changes made based on the following recommendations will not unacceptably affect your ongoing network operations capability.
Apply a patch from your vendor
Appendix A contains information provided by vendors for this
advisory. Please consult this appendix and VU#528719 to determine
if your product is vulnerable. If a statement is unavailable, you
may need to contact your vendor directly.
Disable the SIP-enabled devices and services
As a general rule, the CERT/CC recommends disabling any service or
capability that is not explicitly required. Some of the affected
products may rely on SIP to be functional. You should carefully
consider the impact of blocking services that you may be using.
Ingress filtering
As a temporary measure, it may be possible to limit the scope of
these vulnerabilities by blocking access to SIP devices and
services at the network perimeter.
Ingress filtering manages the flow of traffic as it enters a
network under your administrative control. Servers are typically
the only machines that need to accept inbound traffic from the
public Internet. Note that most SIP User Agents (including IP
phones or "clien"t software) consist of a User Agent Client and a
User Agent Server. In the network usage policy of many sites, there
are few reasons for external hosts to initiate inbound traffic to
machines that provide no public services. Thus, ingress filtering
should be performed at the border to prohibit externally initiated
inbound traffic to non-authorized services.
Please note that this workaround may not protect vulnerable devices
from internal attacks.
Egress filtering
Egress filtering manages the flow of traffic as it leaves a network
under your administrative control. There is typically limited need
for machines providing public services to initiate outbound traffic
to the Internet. In the case of the SIP vulnerabilities, employing
egress filtering on the ports listed above at your network border
may prevent your network from being used as a source for attacks on
other sites.
Block SIP requests directed to broadcast addresses at your router.
Since SIP requests can be transmitted via UDP, broadcast attacks
are possible. One solution to prevent your site from being used as
an intermediary in an attack is to block SIP requests directed to
broadcast addresses at your router.
Appendix A. - Vendor Information
This appendix contains information provided by vendors for this advisory. As vendors report new information to the CERT/CC, we will update this section and note the changes in our revision history. If a particular vendor is not listed below, we have not received their comments.
America Online Inc
Not vulnerable.
Apple Computer Inc.
There are currently no applications shipped by Apple with Mac OS X
or Mac OS X Server which make use of the Session Initiation
Protocol.
Borderware
No BorderWare products make use of SIP and thus no BorderWare
products are affected by this vulnerability.
We would however like to extend our thanks to the OUSPG for their
work as well as for the responsible manner in which they handle
their discoveries. Their detailed reports and test suites are
certainly well-received.
We would also like to reiterate the fact that SIP has yet to
mature, protocol-wise as well as implementation-wise. We do not
recommend that our customers set up SIP relays in parallel to our
firewall products to pass SIP-based applications in or out of
networks where security is a concern of note.
F5 Networks
F5 Networks does not have a SIP server product, and is therefore
not affected by this vulnerability.
Fujitsu
With regards to VU#528719, Fujitsu's UXP/V o.s. is not vulnerable
because the relevant function is not supported under UXP/V.
IBM
SIP is not implemented as part of the AIX operating system.
IP Filter
IPFilter does not do any SIP specific protocol handling and is
therefore not affected by the issues mentioned in the paper cited.
IPTel
All versions of SIP Express Router up to 0.8.9 are sadly vulnerable
to the OUSPG test suite. We strongly advice to upgrade to version
0.8.10. Please also apply the patch to version 0.8.10 from
http://www.iptel.org/ser/security/
before installation and keep on watching this site in the future.
We apologize to our users for the trouble.
Hewlett-Packard Company
Source:
Hewlett-Packard Company
Software Security Response Team
cross reference id: SSRT2402
HP-UX - not vulnerable
HP-MPE/ix - not vulnerable
HP Tru64 UNIX - not vulnerable
HP OpenVMS - not vulnerable
HP NonStop Servers - not vulnerable
To report potential security vulnerabilities in HP software, send
an E-mail message to: mailto:security-alert@hp.com
Lucent
No Lucent products are known to be affected by this vulnerability,
however we are still researching the issue and will update this
statement as needed.
Microsoft Corporation
Microsoft has investigated these issues. The Microsoft SIP client
implementation is not affected.
NEC Corporation
===================================================================
NEC vendor statement for VU#528719
===================================================================
sent on February 13, 2002
Server Products
* EWS/UP 48 Series operating system
* - is NOT vulnerable, because it does not support SIP.
Router Products
* IX 1000 / 2000 / 5000 Series
* - is NOT vulnerable, because it does not support SIP.
Other Network products
* We continue to check our products which support SIP protocol.
===================================================================
NETBSD
NetBSD does not ship any implementation of SIP.
NETfilter.org
As the linux 2.4/2.5 netfilter implementation currently doesn't
support connection tracking or NAT for the SIP protocol suite, we
are not vulnerable to this bug.
NetScreen
NetScreen is not vulnerable to this issue.
Network Appliance
NetApp products are not affected by this vulnerability.
Nokia
Nokia IP Security Platforms based on IPSO, Nokis Small Office
Solution platforms, Nokia VPN products and Nokia Message Protector
platform do not initiate or terminate SIP based sessions. The
mentioned Nokia products are not susceptible to this vulnerability
Nortel Networks
Nortel Networks is cooperating to the fullest extent with the CERT
Coordination Center. All Nortel Networks products that use Session
Initiation Protocol SIP) have been tested and all generally
available products, with the following exceptions, have passed the
test suite:
Succession Communication Server 2000 and Succession Communication
Server 2000 - Compact are impacted by the test suite only in
configurations where SIP-T has been provisioned within the
Communication Server; a software patch is expected to be available
by the end of February.
For further information about Nortel Networks products please
contact Nortel Networks Global Network Support.
North America: 1-800-4-NORTEL, or (1-800-466-7835)
Europe, Middle East & Africa: 00800 8008 9009, or +44 (0) 870 907
9009
Contacts for other regions available at the Global Contact
<http://www.nortelnetworks.com/help/contact/global/> web page.
Novell
Novell has no products implementing SIP.
Secure Computing Corporation
Neither Sidewinder nor Gauntlet implements SIP, so we do not need
to be on the vendor list for this vulnerability.
SecureWorx
We hereby attest that SecureWorx Basilisk Gateway Security product
suite (Firmware version 3.4.2 or later) is NOT VULNERABLE to the
Session Initiation Protocol (SIP) Vulnerability VU#528719 as
described in the OUSPG announcement (OUSPG#0106) received on Fri, 8
Nov 2002 10:17:11 -0500.
Stonesoft
Stonesoft's StoneGate high availability firewall and VPN product
does not contain any code that handles SIP protocol. No versions of
StoneGate are vulnerable.
Symantec
Symantec Corporation products are not vulnerable to this issue.
Xerox
Xerox is aware of this vulnerability and is currently assessing all
products. This statement will be updated as new information becomes
available.
Appendix B. - References
1. http://www.ee.oulu.fi/research/ouspg/protos/
2. http://www.kb.cert.org/vuls/id/528719
3. http://www.cert.org/tech_tips/denial_of_service.html
4. http://www.ietf.org/html.charters/sip-charter.html
5. RFC3261 - SIP: Session Initiation Protocol
6. RFC2327 - SDP: Session Description Protocol
7. RFC2279 - UTF-8, a transformation format of ISO 10646
8. Session Initiation Protocol Basic Call Flow Examples
9. We would also like to acknowledge the
"RedSkins" project of "MediaTeam Oulu" for their support of this research.
Feedback on this document can be directed to the authors, Jason A. Rafail and Ian A. Finlay.
This document is available from: http://www.cert.org/advisories/CA-2003-06.html
CERT/CC Contact Information
Email: cert@cert.org Phone: +1 412-268-7090 (24-hour hotline) Fax: +1 412-268-6989 Postal address: CERT Coordination Center Software Engineering Institute Carnegie Mellon University Pittsburgh PA 15213-3890 U.S.A.
CERT/CC personnel answer the hotline 08:00-17:00 EST(GMT-5) / EDT(GMT-4) Monday through Friday; they are on call for emergencies during other hours, on U.S. holidays, and on weekends.
Using encryption
We strongly urge you to encrypt sensitive information sent by email. Our public PGP key is available from http://www.cert.org/CERT_PGP.key
If you prefer to use DES, please call the CERT hotline for more information.
Getting security information
CERT publications and other security information are available from our web site http://www.cert.org/
To subscribe to the CERT mailing list for advisories and bulletins, send email to majordomo@cert.org. Please include in the body of your message
subscribe cert-advisory
- "CERT" and "CERT Coordination Center" are registered in the U.S. Patent and Trademark Office.
NO WARRANTY Any material furnished by Carnegie Mellon University and the Software Engineering Institute is furnished on an "as is" basis. Carnegie Mellon University makes no warranties of any kind, either expressed or implied as to any matter including, but not limited to, warranty of fitness for a particular purpose or merchantability, exclusivity or results obtained from use of the material. Carnegie Mellon University does not make any warranty of any kind with respect to freedom from patent, trademark, or copyright infringement. ___________
Conditions for use, disclaimers, and sponsorship information
Copyright 2003 Carnegie Mellon University.
Revision History Feb 21, 2003: Initial release
-----BEGIN PGP SIGNATURE----- Version: PGP 6.5.8
iQCVAwUBPlZDZmjtSoHZUTs5AQGBKwQAr+4iXdsjC3LcN3QB77+6uslWZlP4AZlG IXS4u50QPNhuFw/vnuOG2FM4bCSUE7h+nG3eyakS1dWO3jGyybMFWPyvykYeFUKQ 17QbmykeWBUVdGmxOeuVmSdmz7MSp6U+FZZmzuUWM85DlSUKoYg8dF7CqVuC137O Eisa8/wivlM= =p961 -----END PGP SIGNATURE-----
Show details on source website{
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/VARIoTentry#",
"affected_products": {
"@id": "https://www.variotdbs.pl/ref/affected_products"
},
"configurations": {
"@id": "https://www.variotdbs.pl/ref/configurations"
},
"credits": {
"@id": "https://www.variotdbs.pl/ref/credits"
},
"cvss": {
"@id": "https://www.variotdbs.pl/ref/cvss/"
},
"description": {
"@id": "https://www.variotdbs.pl/ref/description/"
},
"exploit_availability": {
"@id": "https://www.variotdbs.pl/ref/exploit_availability/"
},
"external_ids": {
"@id": "https://www.variotdbs.pl/ref/external_ids/"
},
"iot": {
"@id": "https://www.variotdbs.pl/ref/iot/"
},
"iot_taxonomy": {
"@id": "https://www.variotdbs.pl/ref/iot_taxonomy/"
},
"patch": {
"@id": "https://www.variotdbs.pl/ref/patch/"
},
"problemtype_data": {
"@id": "https://www.variotdbs.pl/ref/problemtype_data/"
},
"references": {
"@id": "https://www.variotdbs.pl/ref/references/"
},
"sources": {
"@id": "https://www.variotdbs.pl/ref/sources/"
},
"sources_release_date": {
"@id": "https://www.variotdbs.pl/ref/sources_release_date/"
},
"sources_update_date": {
"@id": "https://www.variotdbs.pl/ref/sources_update_date/"
},
"threat_type": {
"@id": "https://www.variotdbs.pl/ref/threat_type/"
},
"title": {
"@id": "https://www.variotdbs.pl/ref/title/"
},
"type": {
"@id": "https://www.variotdbs.pl/ref/type/"
}
},
"@id": "https://www.variotdbs.pl/vuln/VAR-200312-0087",
"affected_products": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/affected_products#",
"data": {
"@container": "@list"
},
"sources": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#"
},
"@id": "https://www.variotdbs.pl/ref/sources"
}
},
"data": [
{
"model": "siparator",
"scope": "eq",
"trust": 1.0,
"vendor": "ingate",
"version": "*"
},
{
"model": "firewall",
"scope": "eq",
"trust": 1.0,
"vendor": "ingate",
"version": "*"
},
{
"model": null,
"scope": null,
"trust": 0.8,
"vendor": "alcatel",
"version": null
},
{
"model": null,
"scope": null,
"trust": 0.8,
"vendor": "cirpack",
"version": null
},
{
"model": null,
"scope": null,
"trust": 0.8,
"vendor": "cisco",
"version": null
},
{
"model": null,
"scope": null,
"trust": 0.8,
"vendor": "columbia sip user agent sipc",
"version": null
},
{
"model": null,
"scope": null,
"trust": 0.8,
"vendor": "dynamicsoft",
"version": null
},
{
"model": null,
"scope": null,
"trust": 0.8,
"vendor": "iptel",
"version": null
},
{
"model": null,
"scope": null,
"trust": 0.8,
"vendor": "ingate",
"version": null
},
{
"model": null,
"scope": null,
"trust": 0.8,
"vendor": "mediatrix telecom",
"version": null
},
{
"model": null,
"scope": null,
"trust": 0.8,
"vendor": "nortel",
"version": null
},
{
"model": null,
"scope": null,
"trust": 0.8,
"vendor": "pingtel",
"version": null
},
{
"model": "ios 12.2 xa",
"scope": null,
"trust": 0.6,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.2 xh",
"scope": null,
"trust": 0.6,
"vendor": "cisco",
"version": null
},
{
"model": "siparator",
"scope": null,
"trust": 0.6,
"vendor": "ingate",
"version": null
},
{
"model": "firewall",
"scope": null,
"trust": 0.6,
"vendor": "ingate",
"version": null
},
{
"model": "partysip",
"scope": "ne",
"trust": 0.3,
"vendor": "partysip",
"version": "0.5.6"
},
{
"model": "ios 12.2 t3",
"scope": "ne",
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "pix firewall",
"scope": "eq",
"trust": 0.3,
"vendor": "cisco",
"version": "5.2(7)"
},
{
"model": "ios 12.2xm",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "pix firewall",
"scope": "ne",
"trust": 0.3,
"vendor": "cisco",
"version": "6.0(4)"
},
{
"model": "appengine",
"scope": null,
"trust": 0.3,
"vendor": "dymanicsoft",
"version": null
},
{
"model": "ios 12.2xs",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.2 xu",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "university sipc",
"scope": "ne",
"trust": 0.3,
"vendor": "columbia",
"version": "2.0"
},
{
"model": "ios 12.2 xi2",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.2xw",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.2xc",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "networks succession communication server",
"scope": "eq",
"trust": 0.3,
"vendor": "nortel",
"version": "2000"
},
{
"model": "sip express router",
"scope": "eq",
"trust": 0.3,
"vendor": "iptel",
"version": "0.8.9"
},
{
"model": "ios 12.2 xf",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.2 xh3",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.2xt",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.2 xk2",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.2 xu2",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "partysip",
"scope": "eq",
"trust": 0.3,
"vendor": "partysip",
"version": "0.5.3"
},
{
"model": "ios 12.2t",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.2 xe3",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.2xg",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.2 t4",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.2 xb4",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.2 xa5",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ip phone",
"scope": "eq",
"trust": 0.3,
"vendor": "cisco",
"version": "7940"
},
{
"model": "ios 12.2 xt",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.2 t",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "pix firewall",
"scope": "eq",
"trust": 0.3,
"vendor": "cisco",
"version": "5.2(6)"
},
{
"model": "partysip",
"scope": "eq",
"trust": 0.3,
"vendor": "partysip",
"version": "0.5.3-1"
},
{
"model": "ios 12.2 xi",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.2 xs1",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.2 xd4",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.2 xe",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "pix firewall",
"scope": "ne",
"trust": 0.3,
"vendor": "cisco",
"version": "5.2(9)"
},
{
"model": "pix firewall",
"scope": "ne",
"trust": 0.3,
"vendor": "cisco",
"version": "6.1(4)"
},
{
"model": "ios 12.2xd",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.2 xq",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "partysip",
"scope": "eq",
"trust": 0.3,
"vendor": "partysip",
"version": "0.5.2"
},
{
"model": "pix firewall",
"scope": "eq",
"trust": 0.3,
"vendor": "cisco",
"version": "6.1(2)"
},
{
"model": "ios 12.2xa",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "pix firewall",
"scope": "eq",
"trust": 0.3,
"vendor": "cisco",
"version": "5.3"
},
{
"model": "pix firewall",
"scope": "eq",
"trust": 0.3,
"vendor": "cisco",
"version": "6.2(1)"
},
{
"model": "ios 12.2 xd1",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "osip",
"scope": "eq",
"trust": 0.3,
"vendor": "gnu",
"version": "0.9.5"
},
{
"model": "ios 12.2xr",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.2 xt3",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.2xh",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "partysip",
"scope": "eq",
"trust": 0.3,
"vendor": "partysip",
"version": "0.5.4"
},
{
"model": "ios 12.2 xn",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.2xj",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "pix firewall",
"scope": "eq",
"trust": 0.3,
"vendor": "cisco",
"version": "5.2(3.210)"
},
{
"model": "pix firewall",
"scope": "ne",
"trust": 0.3,
"vendor": "cisco",
"version": "6.2(2)"
},
{
"model": "ios 12.2 t1",
"scope": "ne",
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.2xi",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "networks succession communication server compact",
"scope": "eq",
"trust": 0.3,
"vendor": "nortel",
"version": "2000-"
},
{
"model": "ios 12.2 xj1",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.2xq",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "partysip",
"scope": "eq",
"trust": 0.3,
"vendor": "partysip",
"version": "0.5.0"
},
{
"model": "partysip",
"scope": "eq",
"trust": 0.3,
"vendor": "partysip",
"version": "0.5.1-1"
},
{
"model": "ios 12.2xn",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.2 xh2",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "pix firewall",
"scope": "eq",
"trust": 0.3,
"vendor": "cisco",
"version": "6.0"
},
{
"model": "ios 12.2xf",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.2 xi1",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.2 xd3",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.2xk",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.2 xe2",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "university sipc",
"scope": "eq",
"trust": 0.3,
"vendor": "columbia",
"version": "1.74"
},
{
"model": "osip",
"scope": "ne",
"trust": 0.3,
"vendor": "gnu",
"version": "0.9.6"
},
{
"model": "pix firewall",
"scope": "eq",
"trust": 0.3,
"vendor": "cisco",
"version": "5.3(1.200)"
},
{
"model": "ios 12.2 xk",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "partysip",
"scope": "eq",
"trust": 0.3,
"vendor": "partysip",
"version": "0.5.5"
},
{
"model": "partysip",
"scope": "eq",
"trust": 0.3,
"vendor": "partysip",
"version": "0.5.1"
},
{
"model": "c++ sip user agent",
"scope": null,
"trust": 0.3,
"vendor": "dymanicsoft",
"version": null
},
{
"model": "pix firewall",
"scope": "eq",
"trust": 0.3,
"vendor": "cisco",
"version": "6.0(1)"
},
{
"model": "java sip user agent",
"scope": "eq",
"trust": 0.3,
"vendor": "dymanicsoft",
"version": "5.0"
},
{
"model": "sip express router",
"scope": "ne",
"trust": 0.3,
"vendor": "iptel",
"version": "0.8.10"
},
{
"model": "pix firewall",
"scope": "eq",
"trust": 0.3,
"vendor": "cisco",
"version": "5.2(2)"
},
{
"model": "ios 12.2 xd",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.2 xj",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.2 xb",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ip phone",
"scope": "eq",
"trust": 0.3,
"vendor": "cisco",
"version": "7960"
},
{
"model": "java sip user agent",
"scope": "eq",
"trust": 0.3,
"vendor": "dymanicsoft",
"version": "6.0"
},
{
"model": "ios 12.2xb",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "pix firewall",
"scope": "eq",
"trust": 0.3,
"vendor": "cisco",
"version": "5.2(1)"
},
{
"model": "pix firewall",
"scope": "eq",
"trust": 0.3,
"vendor": "cisco",
"version": "5.3(3)"
},
{
"model": "ios 12.2xe",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "partysip",
"scope": "eq",
"trust": 0.3,
"vendor": "partysip",
"version": "0.5.2-1"
},
{
"model": "pix firewall",
"scope": "eq",
"trust": 0.3,
"vendor": "cisco",
"version": "5.2(5)"
},
{
"model": "ios 12.2 xa1",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "converged communications server",
"scope": "eq",
"trust": 0.3,
"vendor": "avaya",
"version": "2.0"
},
{
"model": "pix firewall",
"scope": "eq",
"trust": 0.3,
"vendor": "cisco",
"version": "5.3(2)"
},
{
"model": "ios 12.2 xb3",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.2xl",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "pix firewall",
"scope": "eq",
"trust": 0.3,
"vendor": "cisco",
"version": "6.0(2)"
},
{
"model": "ios 12.2 xs",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "pix firewall",
"scope": "eq",
"trust": 0.3,
"vendor": "cisco",
"version": "5.3(1)"
},
{
"model": "sip express router",
"scope": "eq",
"trust": 0.3,
"vendor": "iptel",
"version": "0.8.8"
},
{
"model": "ios 12.2 xg",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
}
],
"sources": [
{
"db": "CERT/CC",
"id": "VU#528719"
},
{
"db": "BID",
"id": "6904"
},
{
"db": "NVD",
"id": "CVE-2003-1112"
},
{
"db": "CNNVD",
"id": "CNNVD-200312-209"
}
]
},
"configurations": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/configurations#",
"children": {
"@container": "@list"
},
"cpe_match": {
"@container": "@list"
},
"data": {
"@container": "@list"
},
"nodes": {
"@container": "@list"
}
},
"data": [
{
"CVE_data_version": "4.0",
"nodes": [
{
"children": [],
"cpe_match": [
{
"cpe23Uri": "cpe:2.3:h:ingate:ingate_firewall:*:*:*:*:*:*:*:*",
"cpe_name": [],
"vulnerable": true
},
{
"cpe23Uri": "cpe:2.3:h:ingate:ingate_siparator:*:*:*:*:*:*:*:*",
"cpe_name": [],
"vulnerable": true
}
],
"operator": "OR"
}
]
}
],
"sources": [
{
"db": "NVD",
"id": "CVE-2003-1112"
}
]
},
"credits": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/credits#",
"sources": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#"
}
}
},
"data": "Oulu University Secure Programming Group",
"sources": [
{
"db": "CNNVD",
"id": "CNNVD-200312-209"
}
],
"trust": 0.6
},
"cve": "CVE-2003-1112",
"cvss": {
"@context": {
"cvssV2": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/cvss/cvssV2#"
},
"@id": "https://www.variotdbs.pl/ref/cvss/cvssV2"
},
"cvssV3": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/cvss/cvssV3#"
},
"@id": "https://www.variotdbs.pl/ref/cvss/cvssV3/"
},
"severity": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/cvss/severity#"
},
"@id": "https://www.variotdbs.pl/ref/cvss/severity"
},
"sources": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#"
},
"@id": "https://www.variotdbs.pl/ref/sources"
}
},
"data": [
{
"cvssV2": [
{
"acInsufInfo": false,
"accessComplexity": "LOW",
"accessVector": "NETWORK",
"authentication": "NONE",
"author": "NVD",
"availabilityImpact": "PARTIAL",
"baseScore": 7.5,
"confidentialityImpact": "PARTIAL",
"exploitabilityScore": 10.0,
"impactScore": 6.4,
"integrityImpact": "PARTIAL",
"obtainAllPrivilege": false,
"obtainOtherPrivilege": false,
"obtainUserPrivilege": true,
"severity": "HIGH",
"trust": 1.0,
"userInteractionRequired": false,
"vectorString": "AV:N/AC:L/Au:N/C:P/I:P/A:P",
"version": "2.0"
},
{
"accessComplexity": "LOW",
"accessVector": "NETWORK",
"authentication": "NONE",
"author": "VULHUB",
"availabilityImpact": "PARTIAL",
"baseScore": 7.5,
"confidentialityImpact": "PARTIAL",
"exploitabilityScore": 10.0,
"id": "VHN-7937",
"impactScore": 6.4,
"integrityImpact": "PARTIAL",
"severity": "HIGH",
"trust": 0.1,
"vectorString": "AV:N/AC:L/AU:N/C:P/I:P/A:P",
"version": "2.0"
}
],
"cvssV3": [],
"severity": [
{
"author": "NVD",
"id": "CVE-2003-1112",
"trust": 1.0,
"value": "HIGH"
},
{
"author": "CARNEGIE MELLON",
"id": "VU#528719",
"trust": 0.8,
"value": "17.72"
},
{
"author": "CNNVD",
"id": "CNNVD-200312-209",
"trust": 0.6,
"value": "HIGH"
},
{
"author": "VULHUB",
"id": "VHN-7937",
"trust": 0.1,
"value": "HIGH"
}
]
}
],
"sources": [
{
"db": "CERT/CC",
"id": "VU#528719"
},
{
"db": "VULHUB",
"id": "VHN-7937"
},
{
"db": "NVD",
"id": "CVE-2003-1112"
},
{
"db": "CNNVD",
"id": "CNNVD-200312-209"
}
]
},
"description": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/description#",
"sources": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#"
}
}
},
"data": "The Session Initiation Protocol (SIP) implementation in Ingate Firewall and Ingate SIParator before 3.1.3 allows remote attackers to cause a denial of service and possibly execute arbitrary code via crafted INVITE messages, as demonstrated by the OUSPG PROTOS c07-sip test suite. Oulu University has discovered a variety of vulnerabilities affecting products that implement the Session Initiation Protocol (SIP). These vulnerabiltites affect a wide variety of products, with impacts ranging from denial of service to execution of arbitrary code. SIP is used in Voice Over Internet (VoIP), instant messaging, telephony, and various other applications and devices. These issues may be exploited to cause a denial of services in devices which implement the protocol. It has also been reported that unauthorized access to devices may occur under some circumstances. \nThese issues are related to handling of SIP INVITE messages. \nExploitation and the specific nature of each vulnerability may depend on the particular implementation. SIP is part of the IETF standards process, and it builds on foundations such as SMTP (Simple Mail Transfer Protocol) and HTTP (Hypertext Transfer Protocol). It is used to establish, change and terminate calls between users based on IP networks. These vulnerabilities include buffer overflow and improper handling of request messages containing illegal headers, which can cause buffer overflow on devices running this protocol, resulting in denial of service, and may also cause unauthorized access or remote execution of arbitrary commands. Cisco IP Telephony Modules 7940 and 7960 have these vulnerabilities, which can cause denial of service, and are documented in Cisco Bug IDs CSCdz26317, CSCdz29003, CSCdz29033, and CSCdz29041. Versions running Cisco IOS 12.2T train or any 12.2 \\\u0027\\\u0027X\\\u0027\\\u0027 train will reset due to incorrect handling of SIP protocols containing illegal headers. These vulnerabilities are documented in Cisco Bug IDs CSCdz39284 and CSCdz41124. Devices running an IOS version with this vulnerability and configured as a SIP gateway will cause the vulnerability generated by CSCdz39284. However, any version of IOS running with this vulnerability and configured in NAT mode will cause the vulnerability described by CSCdz41124 when SIP uses UDP for transmission. The Cisco PIX firewall resets when it receives a fragmented SIP INVITE message. Since the current SIP patch does not support fragmented SIP messages, the vulnerability described by Cisco Bug ID CSCdx47789 is temporarily patched by dropping SIP fragments. \n\n-----BEGIN PGP SIGNED MESSAGE-----\n\nCERT Advisory CA-2003-06 Multiple vulnerabilities in implementations of the\nSession Initiation Protocol (SIP)\n\n Original release date: February 21, 2003\n Last revised: --\n Source: CERT/CC\n\n A complete revision history can be found at the end of this file. \n Other systems making use of SIP may also be vulnerable but were not\n specifically tested. Not all SIP implementations are affected. See\n Vendor Information for details from vendors who have provided feedback\n for this advisory. \n\n In addition to the vendors who provided feedback for this advisory, a\n list of vendors whom CERT/CC contacted regarding these problems is\n available from VU#528719. These\n vulnerabilities may allow an attacker to gain unauthorized privileged\n access, cause denial-of-service attacks, or cause unstable system\n behavior. If your site uses SIP-enabled products in any capacity, the\n CERT/CC encourages you to read this advisory and follow the advice\n provided in the Solution section below. \n\nI. \n SIP is a text-based protocol for initiating communication and data\n sessions between users. \n\n The Oulu University Secure Programming Group (OUSPG) previously\n conducted research into vulnerabilities in LDAP, culminating in CERT\n Advisory CA-2001-18, and SNMP, resulting in CERT Advisory CA-2002-03. \n\n OUSPG\u0027s most recent research focused on a subset of SIP related to the\n INVITE message, which SIP agents and proxies are required to accept in\n order to set up sessions. Note that \"throttling\" is an expected\n behavior. \n\n Specifications for the Session Initiation Protocol are available in\n RFC3261:\n\n http://www.ietf.org/rfc/rfc3261.txt\n\n OUSPG has established the following site with detailed documentation\n regarding SIP and the implementation test results from the test suite:\n\n http://www.ee.oulu.fi/research/ouspg/protos/testing/c07/sip/\n\n The IETF Charter page for SIP is available at\n\n http://www.ietf.org/html.charters/sip-charter.html\n\nII. Impact\n\n Exploitation of these vulnerabilities may result in denial-of-service\n conditions, service interruptions, and in some cases may allow an\n attacker to gain unauthorized access to the affected device. Specific\n impacts will vary from product to product. \n\nIII. Solution\n\n Many of the mitigation steps recommended below may have significant\n impact on your everyday network operations and/or network\n architecture. Ensure that any changes made based on the following\n recommendations will not unacceptably affect your ongoing network\n operations capability. \n\n Apply a patch from your vendor\n\n Appendix A contains information provided by vendors for this\n advisory. Please consult this appendix and VU#528719 to determine\n if your product is vulnerable. If a statement is unavailable, you\n may need to contact your vendor directly. \n\n Disable the SIP-enabled devices and services\n\n As a general rule, the CERT/CC recommends disabling any service or\n capability that is not explicitly required. Some of the affected\n products may rely on SIP to be functional. You should carefully\n consider the impact of blocking services that you may be using. \n\n Ingress filtering\n\n As a temporary measure, it may be possible to limit the scope of\n these vulnerabilities by blocking access to SIP devices and\n services at the network perimeter. \n\n Ingress filtering manages the flow of traffic as it enters a\n network under your administrative control. Servers are typically\n the only machines that need to accept inbound traffic from the\n public Internet. Note that most SIP User Agents (including IP\n phones or \"clien\"t software) consist of a User Agent Client and a\n User Agent Server. In the network usage policy of many sites, there\n are few reasons for external hosts to initiate inbound traffic to\n machines that provide no public services. Thus, ingress filtering\n should be performed at the border to prohibit externally initiated\n inbound traffic to non-authorized services. \n\n Please note that this workaround may not protect vulnerable devices\n from internal attacks. \n\n Egress filtering\n\n Egress filtering manages the flow of traffic as it leaves a network\n under your administrative control. There is typically limited need\n for machines providing public services to initiate outbound traffic\n to the Internet. In the case of the SIP vulnerabilities, employing\n egress filtering on the ports listed above at your network border\n may prevent your network from being used as a source for attacks on\n other sites. \n\n Block SIP requests directed to broadcast addresses at your router. \n\n Since SIP requests can be transmitted via UDP, broadcast attacks\n are possible. One solution to prevent your site from being used as\n an intermediary in an attack is to block SIP requests directed to\n broadcast addresses at your router. \n\nAppendix A. - Vendor Information\n\n This appendix contains information provided by vendors for this\n advisory. As vendors report new information to the CERT/CC, we will\n update this section and note the changes in our revision history. If a\n particular vendor is not listed below, we have not received their\n comments. \n\n America Online Inc\n\n Not vulnerable. \n\n Apple Computer Inc. \n\n There are currently no applications shipped by Apple with Mac OS X\n or Mac OS X Server which make use of the Session Initiation\n Protocol. \n\n Borderware\n\n No BorderWare products make use of SIP and thus no BorderWare\n products are affected by this vulnerability. \n We would however like to extend our thanks to the OUSPG for their\n work as well as for the responsible manner in which they handle\n their discoveries. Their detailed reports and test suites are\n certainly well-received. \n We would also like to reiterate the fact that SIP has yet to\n mature, protocol-wise as well as implementation-wise. We do not\n recommend that our customers set up SIP relays in parallel to our\n firewall products to pass SIP-based applications in or out of\n networks where security is a concern of note. \n\n F5 Networks\n\n F5 Networks does not have a SIP server product, and is therefore\n not affected by this vulnerability. \n\n Fujitsu\n\n With regards to VU#528719, Fujitsu\u0027s UXP/V o.s. is not vulnerable\n because the relevant function is not supported under UXP/V. \n\n IBM\n\n SIP is not implemented as part of the AIX operating system. \n\n IP Filter\n\n IPFilter does not do any SIP specific protocol handling and is\n therefore not affected by the issues mentioned in the paper cited. \n\n IPTel\n\n All versions of SIP Express Router up to 0.8.9 are sadly vulnerable\n to the OUSPG test suite. We strongly advice to upgrade to version\n 0.8.10. Please also apply the patch to version 0.8.10 from\n http://www.iptel.org/ser/security/\n before installation and keep on watching this site in the future. \n We apologize to our users for the trouble. \n\n Hewlett-Packard Company\n\n Source:\n Hewlett-Packard Company\n Software Security Response Team\n cross reference id: SSRT2402\n\n HP-UX - not vulnerable\n HP-MPE/ix - not vulnerable\n HP Tru64 UNIX - not vulnerable\n HP OpenVMS - not vulnerable\n HP NonStop Servers - not vulnerable\n\n To report potential security vulnerabilities in HP software, send\n an E-mail message to: mailto:security-alert@hp.com\n\n Lucent\n\n No Lucent products are known to be affected by this vulnerability,\n however we are still researching the issue and will update this\n statement as needed. \n\n Microsoft Corporation\n\n Microsoft has investigated these issues. The Microsoft SIP client\n implementation is not affected. \n\n NEC Corporation\n\n ===================================================================\n NEC vendor statement for VU#528719\n ===================================================================\n\n sent on February 13, 2002\n Server Products\n * EWS/UP 48 Series operating system\n * - is NOT vulnerable, because it does not support SIP. \n\n Router Products\n * IX 1000 / 2000 / 5000 Series\n * - is NOT vulnerable, because it does not support SIP. \n\n Other Network products\n * We continue to check our products which support SIP protocol. \n\n ===================================================================\n\n NETBSD\n\n NetBSD does not ship any implementation of SIP. \n\n NETfilter.org\n\n As the linux 2.4/2.5 netfilter implementation currently doesn\u0027t\n support connection tracking or NAT for the SIP protocol suite, we\n are not vulnerable to this bug. \n\n NetScreen\n\n NetScreen is not vulnerable to this issue. \n\n Network Appliance\n\n NetApp products are not affected by this vulnerability. \n\n Nokia\n\n Nokia IP Security Platforms based on IPSO, Nokis Small Office\n Solution platforms, Nokia VPN products and Nokia Message Protector\n platform do not initiate or terminate SIP based sessions. The\n mentioned Nokia products are not susceptible to this vulnerability\n\n Nortel Networks\n\n Nortel Networks is cooperating to the fullest extent with the CERT\n Coordination Center. All Nortel Networks products that use Session\n Initiation Protocol SIP) have been tested and all generally\n available products, with the following exceptions, have passed the\n test suite:\n\n Succession Communication Server 2000 and Succession Communication\n Server 2000 - Compact are impacted by the test suite only in\n configurations where SIP-T has been provisioned within the\n Communication Server; a software patch is expected to be available\n by the end of February. \n\n For further information about Nortel Networks products please\n contact Nortel Networks Global Network Support. \n\n North America: 1-800-4-NORTEL, or (1-800-466-7835)\n Europe, Middle East \u0026 Africa: 00800 8008 9009, or +44 (0) 870 907\n 9009\n\n Contacts for other regions available at the Global Contact\n \u003chttp://www.nortelnetworks.com/help/contact/global/\u003e web page. \n\n Novell\n\n Novell has no products implementing SIP. \n\n Secure Computing Corporation\n\n Neither Sidewinder nor Gauntlet implements SIP, so we do not need\n to be on the vendor list for this vulnerability. \n\n SecureWorx\n\n We hereby attest that SecureWorx Basilisk Gateway Security product\n suite (Firmware version 3.4.2 or later) is NOT VULNERABLE to the\n Session Initiation Protocol (SIP) Vulnerability VU#528719 as\n described in the OUSPG announcement (OUSPG#0106) received on Fri, 8\n Nov 2002 10:17:11 -0500. \n\n Stonesoft\n\n Stonesoft\u0027s StoneGate high availability firewall and VPN product\n does not contain any code that handles SIP protocol. No versions of\n StoneGate are vulnerable. \n\n Symantec\n\n Symantec Corporation products are not vulnerable to this issue. \n\n Xerox\n\n Xerox is aware of this vulnerability and is currently assessing all\n products. This statement will be updated as new information becomes\n available. \n\nAppendix B. - References\n\n 1. http://www.ee.oulu.fi/research/ouspg/protos/\n 2. http://www.kb.cert.org/vuls/id/528719\n 3. http://www.cert.org/tech_tips/denial_of_service.html\n 4. http://www.ietf.org/html.charters/sip-charter.html\n 5. RFC3261 - SIP: Session Initiation Protocol\n 6. RFC2327 - SDP: Session Description Protocol\n 7. RFC2279 - UTF-8, a transformation format of ISO 10646\n 8. Session Initiation Protocol Basic Call Flow Examples \n 9. We would also like to acknowledge the\n \"RedSkins\" project of \"MediaTeam Oulu\" for their support of this\n research. \n _________________________________________________________________\n\n Feedback on this document can be directed to the authors, \n Jason A. Rafail and Ian A. Finlay. \n ______________________________________________________________________\n\n This document is available from:\n http://www.cert.org/advisories/CA-2003-06.html\n ______________________________________________________________________\n\nCERT/CC Contact Information\n\n Email: cert@cert.org\n Phone: +1 412-268-7090 (24-hour hotline)\n Fax: +1 412-268-6989\n Postal address:\n CERT Coordination Center\n Software Engineering Institute\n Carnegie Mellon University\n Pittsburgh PA 15213-3890\n U.S.A. \n\n CERT/CC personnel answer the hotline 08:00-17:00 EST(GMT-5) /\n EDT(GMT-4) Monday through Friday; they are on call for emergencies\n during other hours, on U.S. holidays, and on weekends. \n\nUsing encryption\n\n We strongly urge you to encrypt sensitive information sent by email. \n Our public PGP key is available from\n http://www.cert.org/CERT_PGP.key\n\n If you prefer to use DES, please call the CERT hotline for more\n information. \n\nGetting security information\n\n CERT publications and other security information are available from\n our web site\n http://www.cert.org/\n\n To subscribe to the CERT mailing list for advisories and bulletins,\n send email to majordomo@cert.org. Please include in the body of your\n message\n\n subscribe cert-advisory\n\n * \"CERT\" and \"CERT Coordination Center\" are registered in the U.S. \n Patent and Trademark Office. \n ______________________________________________________________________\n\n NO WARRANTY\n Any material furnished by Carnegie Mellon University and the Software\n Engineering Institute is furnished on an \"as is\" basis. Carnegie\n Mellon University makes no warranties of any kind, either expressed or\n implied as to any matter including, but not limited to, warranty of\n fitness for a particular purpose or merchantability, exclusivity or\n results obtained from use of the material. Carnegie Mellon University\n does not make any warranty of any kind with respect to freedom from\n patent, trademark, or copyright infringement. \n _________________________________________________________________\n\n Conditions for use, disclaimers, and sponsorship information\n\n Copyright 2003 Carnegie Mellon University. \n\n Revision History\n Feb 21, 2003: Initial release\n\n-----BEGIN PGP SIGNATURE-----\nVersion: PGP 6.5.8\n\niQCVAwUBPlZDZmjtSoHZUTs5AQGBKwQAr+4iXdsjC3LcN3QB77+6uslWZlP4AZlG\nIXS4u50QPNhuFw/vnuOG2FM4bCSUE7h+nG3eyakS1dWO3jGyybMFWPyvykYeFUKQ\n17QbmykeWBUVdGmxOeuVmSdmz7MSp6U+FZZmzuUWM85DlSUKoYg8dF7CqVuC137O\nEisa8/wivlM=\n=p961\n-----END PGP SIGNATURE-----\n",
"sources": [
{
"db": "NVD",
"id": "CVE-2003-1112"
},
{
"db": "CERT/CC",
"id": "VU#528719"
},
{
"db": "BID",
"id": "6904"
},
{
"db": "VULHUB",
"id": "VHN-7937"
},
{
"db": "PACKETSTORM",
"id": "30838"
}
],
"trust": 2.07
},
"external_ids": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/external_ids#",
"data": {
"@container": "@list"
},
"sources": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#"
}
}
},
"data": [
{
"db": "CERT/CC",
"id": "VU#528719",
"trust": 2.9
},
{
"db": "BID",
"id": "6904",
"trust": 2.0
},
{
"db": "NVD",
"id": "CVE-2003-1112",
"trust": 1.7
},
{
"db": "CNNVD",
"id": "CNNVD-200312-209",
"trust": 0.7
},
{
"db": "CERT/CC",
"id": "CA-2003-06",
"trust": 0.6
},
{
"db": "NSFOCUS",
"id": "4442",
"trust": 0.6
},
{
"db": "XF",
"id": "11379",
"trust": 0.6
},
{
"db": "VULHUB",
"id": "VHN-7937",
"trust": 0.1
},
{
"db": "PACKETSTORM",
"id": "30838",
"trust": 0.1
}
],
"sources": [
{
"db": "CERT/CC",
"id": "VU#528719"
},
{
"db": "VULHUB",
"id": "VHN-7937"
},
{
"db": "BID",
"id": "6904"
},
{
"db": "PACKETSTORM",
"id": "30838"
},
{
"db": "NVD",
"id": "CVE-2003-1112"
},
{
"db": "CNNVD",
"id": "CNNVD-200312-209"
}
]
},
"id": "VAR-200312-0087",
"iot": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/iot#",
"sources": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#"
}
}
},
"data": true,
"sources": [
{
"db": "VULHUB",
"id": "VHN-7937"
}
],
"trust": 0.47675563
},
"last_update_date": "2023-12-18T12:13:49.143000Z",
"problemtype_data": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/problemtype_data#",
"sources": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#"
}
}
},
"data": [
{
"problemtype": "NVD-CWE-Other",
"trust": 1.0
}
],
"sources": [
{
"db": "NVD",
"id": "CVE-2003-1112"
}
]
},
"references": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/references#",
"data": {
"@container": "@list"
},
"sources": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#"
}
}
},
"data": [
{
"trust": 2.9,
"url": "http://www.ee.oulu.fi/research/ouspg/protos/testing/c07/sip/"
},
{
"trust": 2.1,
"url": "http://www.cert.org/advisories/ca-2003-06.html"
},
{
"trust": 2.1,
"url": "http://www.kb.cert.org/vuls/id/528719"
},
{
"trust": 1.7,
"url": "http://www.securityfocus.com/bid/6904"
},
{
"trust": 1.1,
"url": "https://exchange.xforce.ibmcloud.com/vulnerabilities/11379"
},
{
"trust": 0.9,
"url": "http://www.ietf.org/html.charters/sip-charter.html"
},
{
"trust": 0.9,
"url": "http://www.ietf.org/rfc/rfc3261.txt"
},
{
"trust": 0.8,
"url": "http://www.ee.oulu.fi/research/ouspg/protos/ "
},
{
"trust": 0.8,
"url": "http://www.mediateam.oulu.fi/projects/redskins/?lang=en"
},
{
"trust": 0.8,
"url": "http://www.ietf.org/internet-drafts/draft-ietf-sipping-torture-tests-07.txt"
},
{
"trust": 0.8,
"url": "http://www.ietf.org/rfc/rfc3665.txt"
},
{
"trust": 0.8,
"url": "http://www.ietf.org/rfc/rfc2327.txt"
},
{
"trust": 0.8,
"url": "http://www.ietf.org/rfc/rfc2279.txt"
},
{
"trust": 0.6,
"url": "http://xforce.iss.net/xforce/xfdb/11379"
},
{
"trust": 0.6,
"url": "http://www.nsfocus.net/vulndb/4442"
},
{
"trust": 0.3,
"url": "http://www.dynamicsoft.com/support/advisory/ca-2003-06.php"
},
{
"trust": 0.3,
"url": "http://www.fsf.org/software/osip/osip.html"
},
{
"trust": 0.3,
"url": "http://www.partysip.org/"
},
{
"trust": 0.3,
"url": "http://www.iptel.org/"
},
{
"trust": 0.3,
"url": "http://support.avaya.com/japple/css/japple?temp.groupid=128450\u0026temp.selectedfamily=128451\u0026temp.selectedproduct=154235\u0026temp.selectedbucket=126655\u0026temp.feedbackstate=askforfeedback\u0026temp.documentid=16123"
},
{
"trust": 0.1,
"url": "http://www.cert.org/tech_tips/denial_of_service.html"
},
{
"trust": 0.1,
"url": "http://www.cert.org/"
},
{
"trust": 0.1,
"url": "http://www.iptel.org/ser/security/"
},
{
"trust": 0.1,
"url": "http://www.cert.org/cert_pgp.key"
},
{
"trust": 0.1,
"url": "http://www.nortelnetworks.com/help/contact/global/\u003e"
},
{
"trust": 0.1,
"url": "http://www.ee.oulu.fi/research/ouspg/protos/"
}
],
"sources": [
{
"db": "CERT/CC",
"id": "VU#528719"
},
{
"db": "VULHUB",
"id": "VHN-7937"
},
{
"db": "BID",
"id": "6904"
},
{
"db": "PACKETSTORM",
"id": "30838"
},
{
"db": "NVD",
"id": "CVE-2003-1112"
},
{
"db": "CNNVD",
"id": "CNNVD-200312-209"
}
]
},
"sources": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#",
"data": {
"@container": "@list"
}
},
"data": [
{
"db": "CERT/CC",
"id": "VU#528719"
},
{
"db": "VULHUB",
"id": "VHN-7937"
},
{
"db": "BID",
"id": "6904"
},
{
"db": "PACKETSTORM",
"id": "30838"
},
{
"db": "NVD",
"id": "CVE-2003-1112"
},
{
"db": "CNNVD",
"id": "CNNVD-200312-209"
}
]
},
"sources_release_date": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources_release_date#",
"data": {
"@container": "@list"
}
},
"data": [
{
"date": "2003-02-21T00:00:00",
"db": "CERT/CC",
"id": "VU#528719"
},
{
"date": "2003-12-31T00:00:00",
"db": "VULHUB",
"id": "VHN-7937"
},
{
"date": "2003-02-21T00:00:00",
"db": "BID",
"id": "6904"
},
{
"date": "2003-02-21T17:04:53",
"db": "PACKETSTORM",
"id": "30838"
},
{
"date": "2003-12-31T05:00:00",
"db": "NVD",
"id": "CVE-2003-1112"
},
{
"date": "2003-02-21T00:00:00",
"db": "CNNVD",
"id": "CNNVD-200312-209"
}
]
},
"sources_update_date": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources_update_date#",
"data": {
"@container": "@list"
}
},
"data": [
{
"date": "2007-05-21T00:00:00",
"db": "CERT/CC",
"id": "VU#528719"
},
{
"date": "2017-07-11T00:00:00",
"db": "VULHUB",
"id": "VHN-7937"
},
{
"date": "2003-02-21T00:00:00",
"db": "BID",
"id": "6904"
},
{
"date": "2017-07-11T01:29:45.150000",
"db": "NVD",
"id": "CVE-2003-1112"
},
{
"date": "2005-10-20T00:00:00",
"db": "CNNVD",
"id": "CNNVD-200312-209"
}
]
},
"threat_type": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/threat_type#",
"sources": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#"
}
}
},
"data": "remote",
"sources": [
{
"db": "CNNVD",
"id": "CNNVD-200312-209"
}
],
"trust": 0.6
},
"title": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/title#",
"sources": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#"
}
}
},
"data": "Multiple implementations of the Session Initiation Protocol (SIP) contain multiple types of vulnerabilities",
"sources": [
{
"db": "CERT/CC",
"id": "VU#528719"
}
],
"trust": 0.8
},
"type": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/type#",
"sources": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#"
}
}
},
"data": "Unknown",
"sources": [
{
"db": "BID",
"id": "6904"
},
{
"db": "CNNVD",
"id": "CNNVD-200312-209"
}
],
"trust": 0.9
}
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.