H&D HACKING & DEFENSE: enero 2007

martes, 30 de enero de 2007

Ingresa ahora al TechNet Learning Center y capacítate

Para este comienzo de año, hemos lanzado 3 nuevos cursos en nuestro Learning Center.

Ellos se basan en las versiones RTM de los nuevos productos Exchange Server 2007, Windows Vista, y 2007 Office system. Capacítate antes que nadie sobre estas nuevas herramientas que harán historia:

El curso sobre Exchange Server 2007 permite conocer la protección avanzada que su empresa necesita junto a la posibilidad de acceder desde cualquier parte, sin sacrificar el desempeño operativo necesario hoy en día.

El de Windows Vista abarca su instalación, las mejoras en seguridad, y las nuevas funciones y actualizaciones ya conocidas.

Mientras que en el de 2007 Office system se abordarán las ediciones Professional Plus, Enterprise y Small Business. Con esta nueva versión, Microsoft introduce el formato de archivo XML.
Ingresa ahora al TechNet Learning Center y capacítate antes que nadie.

NECESITAS EMPLEO?

24/01/2007 19:39 Posted by teamexpertnet

EMPRESA DE CAPACITACIONES - INTECAP
BOGOTA
PROFESIONALES EN LAS SIGUIENTES AREAS:
WEBMASTER : Dominio total de Flash(Action Script) + Php + MySQL para dictar capacitacion en desarrollo de páginas web dinámicas, preferiblemente certificado en Macromedia, manejo de herramientas 3D.
SQL SERVER 2000-2005: Dominio de la herramienta para dar capacitacion en la Administracion de la Base de Datos, tener experiencia en manejo de bases de datos.
MySQL 5: Dominio de la herramienta para dar capacitacion en la Administracion de la Base de Datos, tener experiencia en manejo de bases de datos.
.NET 2003 - 2005: Domino total de esta herramienta de Programación, tener nivel Avanzado - Experto.
POWER BUILDER : Conocer y desarrollar en ultimas versiones de este paquete.
Deben poseer EXPERIENCIA COMPROBADA en docencia sobre el tema.
Por favor enviar hoja de vida al correo mherrera@intecap.edu.co , info@intecap.edu.co por favor especificar el cargo en asunto.
--------------------------------------------------------------------------------
Compañía de tecnología ubicada en Bogotá requiere
Ingeniero de Desarrollo Oracle profesional en Ingeniería de Sistemas, con conocimientos en Base de Datos Oracle y Forms. Fecha de grado mayor o igual a cinco años.
Ingeniero de Desarrollo .NET: profesional en Ingeniería de sistemas o carreras afines con conocimientos y experiencia en desarrollo .NET y Base de datos Oracle.
Ingeniero de Desarrollo SQL: profesional en Ingeniería de sistemas o carreras afines con conocimientos en Business Objects y experiencia en desarrollo .NET y SQL Server.
Ingeniero de Desarrollo J2EE: profesional en Ingeniería de sistemas o carreras afines con experiencia en desarrollo J2EE y sistemas operativos Linux Red Hat o Unix.
Favor remitir su hoja de vida UNICAMENTE SI CUMPLE CON EL PERFIL, indicando en el asunto, el cargo al cual aplica.
Correo: recursoshumanos@softmanagement.com.co
Fecha límite: Febrero 02 de 2007

INGENIERO DE SISTEMAS, O, TÉCNICO, O TECNÓLOGO EN SISTEMAS
Se requiere una persona con titulo, y experiencia mínima de tres años.
Descripción: Conocimientos técnicos avanzados y demostrables del paquete office principalmente Excel, experiencia en manejo depuración y migración de bases de datos.
Debe poseer un muy buen manejo de HTML para diseño y o modificación de paginas Web
Competencias: Persona con excelentes habilidades de comunicación, buena expresión y fluidez verbal, proactivo, habilidades de planeación y organización, orientado a resultados, gran capacidad de trabajo en equipo
La sede de la compañía esta en Bogota, pero el trabajo se desarrollara fuera de Bogota, debe tener disponibilidad permanente para viajar.
Enviar hoja de vida indicando aspiración salarial al e-mail enviarofertalaboral@yahoo.com , recibiremos ofertas hasta el día 26 de enero de 2006,

--------------------------------------------------------------------------------
16/01/2007 16:54 Posted by teamexpertnet

SENIOR SOFTWARE DEVELOPER
BOGOTA
Importante Empresa requiere Senior Software Developer. Hombre o Mujer.
Profesional en Ingenieria de Sistemas. Con experiencia mìnima de cinco años en desarrollo de software y mìnimo dos años de experiencia en administraciòn de servidores. Conocimientos avanzados en .NET y SQL Server 2000. Sòlidas bases de seguridad informàtica.
Enviar H.V. indicando el cargo al cual se postula a : acuevas@activos.com.

--------------------------------------------------------------------------------
13/01/2007 16:14 Posted by teamexpertnet

INGENIERO DE SISTEMAS
INGENIERO DE SOPORTE
BOGOTA
El ingeniero de soporte, debe ser profesional en Ingeniería de Sistemas, certificación MCSE (Microsoft Certified System Engineer), inglés mínimo 90% en fluidez conversacional y comprensión, con mínimo dos años de experiencia comprobada en compañías tecnológicas, en soporte a usuarios en aplicativos y ambientes Windows, conocimientos de bases de datos Oracle y Sybase, implementación de aplicativos en ambientes Windows (2000, XP, Windows Server 2000/2003) y Web, manejo de bases de datos Microsoft SQL, redes de comunicaciones, servidores Web e IIS (Internet Information Service), deseable conocimientos en herramientas de gestión electrónica de documentos, digitalización y workflow, spools de impresión y/o sistemas Cold. Excelente presentación personal y relaciones interpersonales, capacidad para trabajar en equipo y bajo presión, liderazgo, capacidad de negociación, disposición al servicio, compromiso, proactividad, estabilidad, orientación a resultados. Preferiblemente que cuente con VISA AMERICANA.
Los interesados deben acercarse a la Cl 42a # 9-63 de 8 a 10 am con Hoja de Vida actualizada preferiblemente ó enviar hoja de vida a la siguiente dirección
administrativos.servimos@gmail.com
Indicando el cargo al que se postulan.
POR FAVOR NO POSTULARSE SINO CUMPLE LOS REQUISITOS

INGENIERO DE SOPORTE-BILINGUE-
BOGOTA
Importante Empresa requiere Ingeniero de Soporte. Hombre o Mujer.
Profesional en Ingenierìa de Sistemas. Con certificaciòn MCSE(Microsoft Certified System Engineer). Experiencia mìnima de dos años en compañìas tecnològicas, en soporte a usuarios en aplicaticos Windows, conocimientos de bases de datos Oracle y Sybase, implementaciòn de aplicativos en ambientes Windows (2000, XP, Windows Server 2000/2003) y Web, manejo de bases de datos Microsoft SQL, redes de comunicaciones, servidores Web e IIS (Internet Information Service). Salario $3.500.000
Enviar H.V. indicando el cargo al cual se postula a : acuevas@activos.com.co

ANALISTA DE INFORMACION-BILINGUE
BOGOTA
Importante Empresa requiere Analista de Informaciòn. Hombre o Mujer.
Profesional en Sistemas de Informaciòn, Documentaciòn o Bibliotecologìa.
Con experiencia mìnima de dos años en compañìas tecnològicas, en levantamiento, anàlisis de informaciòn y tipos documentales. Manejo de proyectos de informaciòn y de tablas de retenciòn documental. Ingles 90%.
Salario $1.800.000
Enviar H.V. indicando el cargo al cual se postula a : acuevas@activos.com.co

jueves, 25 de enero de 2007

Fetchmail: Denial of Service and password disclosure GENTOO

1. Gentoo Linux Security Advisory

Version Information

Advisory Reference GLSA 200701-13 / fetchmail
Release Date January 22, 2007
Latest Revision January 22, 2007: 01
Impact normal
Exploitable remote
Package Vulnerable versions Unaffected versions Architecture(s)
net-mail/fetchmail < 6.3.6 >= 6.3.6 All supported architectures

Related bugreports: #160463

Synopsis

Fetchmail has been found to have numerous vulnerabilities allowing for Denial of Service and password disclosure.
2. Impact Information

Background

Fetchmail is a remote mail retrieval and forwarding utility.

Description

Neil Hoggarth has discovered that when delivering messages to a message delivery agent by means of the "mda" option, Fetchmail passes a NULL pointer to the ferror() and fflush() functions when refusing a message. Isaac Wilcox has discovered numerous means of plain-text password disclosure due to errors in secure connection establishment.

Impact

An attacker could deliver a message via Fetchmail to a message delivery agent configured to refuse the message, and crash the Fetchmail process. SMTP and LMTP delivery modes are not affected by this vulnerability. An attacker could also perform a Man-in-the-Middle attack, and obtain plain-text authentication credentials of users connecting to a Fetchmail process.

3. Resolution Information

Workaround

There is no known workaround at this time.

Resolution

All fetchmail users should upgrade to the latest version:

Code Listing 3.1

# emerge --sync
# emerge --ask --oneshot --verbose ">=net-mail/fetchmail-6.3.6"

4. References

CVE-2006-5867
CVE-2006-5974

Print

Updated January 22, 2007

Summary: This is a Gentoo Linux Security Advisory

security@gentoo.org
Contact Address

Donate to support our development efforts.

VR Hosted

Tek Alchemy

SevenL.net

php|architect

Mod_auth_kerb: Denial of Service GENTOO

1. Gentoo Linux Security Advisory

Version Information

Advisory Reference GLSA 200701-14 / mod_auth_kerb
Release Date January 22, 2007
Latest Revision January 22, 2007: 01
Impact normal
Exploitable remote
Package Vulnerable versions Unaffected versions Architecture(s)
net-www/mod_auth_kerb < 5.0_rc7-r1 >= 5.0_rc7-r1 All supported architectures

Related bugreports: #155782

Synopsis

Mod_auth_kerb is vulnerable to a buffer overflow possibly allowing a Denial of Service.
2. Impact Information

Background

Mod_auth_kerb is an Apache authentication module using Kerberos.

Description

Mod_auth_kerb improperly handles component byte encoding in the der_get_oid() function, allowing for a buffer overflow to occur if there are no components which require more than one byte for encoding.

Impact

An attacker could try to access a Kerberos protected resource on an Apache server with an incorrectly configured service principal and crash the server process. It is important to note that this buffer overflow is not known to allow for the execution of code.

3. Resolution Information

Workaround

There is no known workaround at this time.

Resolution

All mod_auth_kerb users should upgrade to the latest version:

Code Listing 3.1

# emerge --sync
# emerge --ask --oneshot --verbose ">=net-www/mod_auth_kerb-5.0_rc7-r1"

4. References

CVE-2006-5989

Print

Updated January 22, 2007

Summary: This is a Gentoo Linux Security Advisory

security@gentoo.org
Contact Address

Donate to support our development efforts.

VR Hosted

Tek Alchemy

SevenL.net

php|architect

Mod_auth_kerb: Denial of Service GENTOO

Sun JDK/JRE: Multiple vulnerabilities GENTOO

1. Gentoo Linux Security Advisory

Version Information

Advisory Reference GLSA 200701-15 / java
Release Date January 22, 2007
Latest Revision January 22, 2007: 01
Impact normal
Exploitable remote
Package Vulnerable versions Unaffected versions Architecture(s)
dev-java/sun-jdk < 1.4.2.13, < 1.5.0.09 >= 1.4.2.13, >= 1.5.0.09 All supported architectures
dev-java/sun-jre-bin < 1.4.2.13, < 1.5.0.09 >= 1.4.2.13, >= 1.5.0.09 All supported architectures

Related bugreports: #158659

Synopsis

Multiple unspecified vulnerabilities have been identified in Sun Java Development Kit (JDK) and Java Runtime Environment (JRE).
2. Impact Information

Background

The Sun Java Development Kit (JDK) and the Sun Java Runtime Environment (JRE) provide the Sun Java platform.

Description

Chris Evans has discovered multiple buffer overflows in Sun JDK and Sun JRE possibly related to various AWT or font layout functions. Tom Hawtin has discovered an unspecified vulnerability in Sun JDK and Sun JRE relating to unintended applet data access. He has also discovered multiple other unspecified vulnerabilities in Sun JDK and Sun JRE allowing unintended Java applet or application resource acquisition.

Impact

An attacker could entice a user to run a specially crafted Java applet or application that could read, write, or execute local files with the privileges of the user running the JVM; access data maintained in other Java applets; or escalate the privileges of the currently running Java applet or application allowing for unauthorized access to system resources.

3. Resolution Information

Workaround

There is no known workaround at this time.

Resolution

All Sun Java Development Kit users should upgrade to the latest version:

Code Listing 3.1

# emerge --sync
# emerge --ask --oneshot --verbose "dev-java/sun-jdk"

All Sun Java Runtime Environment users should upgrade to the latest version:

Code Listing 3.2

# emerge --sync
# emerge --ask --oneshot --verbose "dev-java/sun-jre-bin"

4. References

CVE-2006-6731
CVE-2006-6736
CVE-2006-6737
CVE-2006-6745

Adobe Acrobat Reader: Multiple vulnerabilities GENTOO

1. Gentoo Linux Security Advisory

Version Information

Advisory Reference GLSA 200701-16 / acroread
Release Date January 22, 2007
Latest Revision January 22, 2007: 01
Impact normal
Exploitable remote
Package Vulnerable versions Unaffected versions Architecture(s)
app-text/acroread < 7.0.9 >= 7.0.9 All supported architectures

Related bugreports: #159874

Synopsis

Adobe Acrobat Reader is vulnerable to remote code execution, Denial of Service, and cross-site scripting attacks.
2. Impact Information

Background

Adobe Acrobat Reader is a PDF reader released by Adobe.

Description

Adobe Acrobat Reader in stand-alone mode is vulnerable to remote code execution via heap corruption when loading a specially crafted PDF file.

The browser plugin released with Adobe Acrobat Reader (nppdf.so) does not properly handle URLs, and crashes if given a URL that is too long. The plugin does not correctly handle JavaScript, and executes JavaScript that is given as a GET variable to the URL of a PDF file. Lastly, the plugin does not properly handle the FDF, xml, xfdf AJAX request parameters following the # character in a URL, allowing for multiple cross-site scripting vulnerabilities.

Impact

An attacker could entice a user to open a specially crafted PDF file and execute arbitrary code with the rights of the user running Adobe Acrobat Reader. An attacker could also entice a user to browse to a specially crafted URL and either crash the Adobe Acrobat Reader browser plugin, execute arbitrary JavaScript in the context of the user's browser, or inject arbitrary HTML or JavaScript into the document being viewed by the user. Note that users who have emerged Adobe Acrobat Reader with the "nsplugin" USE flag disabled are not vulnerable to issues with the Adobe Acrobat Reader browser plugin.

3. Resolution Information

Workaround

There is no known workaround at this time.

Resolution

All Adobe Acrobat Reader users should upgrade to the latest version:

Code Listing 3.1

# emerge --sync
# emerge --ask --oneshot --verbose ">=app-text/acroread-7.0.9"

4. References

CVE-2006-5857
CVE-2007-0044
CVE-2007-0045
CVE-2007-0046
CVE-2007-0048

Print

Updated January 22, 2007

Summary: This is a Gentoo Linux Security Advisory

security@gentoo.org
Contact Address

Donate to support our development efforts.

VR Hosted

Tek Alchemy

SevenL.net

php|architect

libgtop: Privilege escalation GENTOO

1. Gentoo Linux Security Advisory

Version Information

Advisory Reference GLSA 200701-17 / libgtop
Release Date January 23, 2007
Latest Revision January 23, 2007: 01
Impact normal
Exploitable local
Package Vulnerable versions Unaffected versions Architecture(s)
gnome-base/libgtop < 2.14.6 >= 2.14.6 All supported architectures

Related bugreports: #162169

Synopsis

libgtop improperly handles filenames, possibly allowing for the execution of arbitrary code.
2. Impact Information

Background

libgtop facilitates the libgtop_daemon, which is used by GNOME to obtain information about remote systems.

Description

Liu Qishuai discovered that glibtop_get_proc_map_s() in sysdeps/linux/procmap.c does not properly allocate memory for storing a filename, allowing certain filenames to cause the buffer to overflow on the stack.

Impact

By tricking a victim into executing an application that uses the libgtop library (e.g. libgtop_daemon or gnome-system-monitor), a local attacker could specify a specially crafted filename to be used by libgtop causing a buffer overflow and possibly execute arbitrary code with the rights of the user running the application.

3. Resolution Information

Workaround

There is no known workaround at this time.

Resolution

All libgtop users should upgrade to the latest version:

Code Listing 3.1

# emerge --sync
# emerge --ask --oneshot --verbose ">=gnome-base/libgtop-2.14.6"

4. References

CVE-2007-0235

xine-ui: Format string vulnerabilities

1. Gentoo Linux Security Advisory

Version Information

Advisory Reference GLSA 200701-18 / xine-ui
Release Date January 23, 2007
Latest Revision January 23, 2007: 01
Impact normal
Exploitable remote
Package Vulnerable versions Unaffected versions Architecture(s)
media-video/xine-ui < 0.99.5_pre20060716 >= 0.99.5_pre20060716 All supported architectures

Related bugreports: #161558

Synopsis

xine-ui improperly handles format strings, possibly allowing for the execution of arbitrary code.
2. Impact Information

Background

xine-ui is a skin-based user interface for xine. xine is a free multimedia player. It plays CDs, DVDs, and VCDs, and can also decode other common multimedia formats.

Description

Due to the improper handling and use of format strings, the errors_create_window() function in errors.c does not safely write data to memory.

Impact

An attacker could entice a user to open a specially crafted media file with xine-ui, and possibly execute arbitrary code.

3. Resolution Information

Workaround

There is no known workaround at this time.

Resolution

All xine-ui users should upgrade to the latest version:

Code Listing 3.1

# emerge --sync
# emerge --ask --oneshot --verbose ">=media-video/xine-ui-0.99.5_pre20060716"

4. References

CVE-2007-0254

OpenLDAP: Insecure usage of /tmp during installation

1. Gentoo Linux Security Advisory

Version Information

Advisory Reference GLSA 200701-19 / openldap
Release Date January 23, 2007
Latest Revision January 23, 2007: 01
Impact low
Exploitable local
Package Vulnerable versions Unaffected versions Architecture(s)
net-nds/openldap < 2.1.30-r10, < 2.2.28-r7, < 2.3.30-r2 >= 2.1.30-r10, >= 2.2.28-r7, >= 2.3.30-r2 All supported architectures

Related bugreports: #159508

Synopsis

A shell script commonly released with OpenLDAP makes insecure usage of files in /tmp during the emerge process.
2. Impact Information

Background

OpenLDAP Software is an open source implementation of the Lightweight Directory Access Protocol.

Description

Tavis Ormandy of the Gentoo Linux Security Team has discovered that the file gencert.sh distributed with the Gentoo ebuild for OpenLDAP does not exit upon the existence of a directory in /tmp during installation allowing for directory traversal.

Impact

A local attacker could create a symbolic link in /tmp and potentially overwrite arbitrary system files upon a privileged user emerging OpenLDAP.

3. Resolution Information

Workaround

There is no known workaround at this time.

Resolution

All OpenLDAP users should upgrade to the latest version:

Code Listing 3.1

# emerge --sync
# emerge --ask --oneshot --verbose "net-nds/openldap"

Print

Updated January 23, 2007

Summary: This is a Gentoo Linux Security Advisory

security@gentoo.org
Contact Address

Donate to support our development efforts.

VR Hosted

Tek Alchemy

SevenL.net

php|architect

Centericq: Remote buffer overflow in LiveJournal handling

1. Gentoo Linux Security Advisory

Version Information

Advisory Reference GLSA 200701-20 / centericq
Release Date January 24, 2007
Latest Revision January 24, 2007: 01
Impact normal
Exploitable remote
Package Vulnerable versions Unaffected versions Architecture(s)
net-im/centericq <= 4.21.0-r2 All supported architectures

Related bugreports: #160793

Synopsis

Centericq does not properly handle communications with the LiveJournal service, allowing for the remote execution of arbitrary code.
2. Impact Information

Background

Centericq is a text mode menu-driven and window-driven instant messaging interface.

Description

When interfacing with the LiveJournal service, Centericq does not appropriately allocate memory for incoming data, in some cases creating a buffer overflow.

Impact

An attacker could entice a user to connect to an unofficial LiveJournal server causing Centericq to read specially crafted data from the server, which could lead to the execution of arbitrary code with the rights of the user running Centericq.

3. Resolution Information

Workaround

There is no known workaround at this time.

Resolution

Currently, Centericq is unmaintained. As such, Centericq has been masked in Portage until it is again maintained.

Code Listing 3.1

# emerge --ask --verbose --unmerge "net-im/centericq"

4. References

CVE-2007-0160

MIT Kerberos 5: Arbitrary Remote Code Execution

1. Gentoo Linux Security Advisory

Version Information

Advisory Reference GLSA 200701-21 / mit-krb5
Release Date January 24, 2007
Latest Revision January 24, 2007: 01
Impact high
Exploitable remote
Package Vulnerable versions Unaffected versions Architecture(s)
app-crypt/mit-krb5 < 1.5.2 >= 1.5.2 All supported architectures

Related bugreports: #158810

Synopsis

Multiple vulnerabilities in MIT Kerberos 5 could potentially result in the execution of arbitrary code.
2. Impact Information

Background

MIT Kerberos 5 is a suite of applications that implement the Kerberos network protocol.

Description

The Kerberos administration daemon, and possibly other applications using the GSS-API or RPC libraries, could potentially call a function pointer in a freed heap buffer, or attempt to free an uninitialized pointer.

Impact

A remote attacker may be able to crash an affected application, or potentially execute arbitrary code with root privileges.

3. Resolution Information

Workaround

There is no known workaround at this time.

Resolution

All MIT Kerberos 5 users should upgrade to the latest version:

Code Listing 3.1

# emerge --sync
# emerge --ask --oneshot --verbose ">=app-crypt/mit-krb5-1.5.2"

4. References

CVE-2006-6143
CVE-2006-6144

wget (denial of service)

rPSA-2007-0011-1 wget
rPath Update Announcements announce-noreply at rpath.com
Tue Jan 23 03:45:02 EST 2007

Previous message: rPSA-2007-0007-1 kdenetwork
Next message: rPSA-2007-0012-1 ed
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

--------------------------------------------------------------------------------

rPath Security Advisory: 2007-0011-1
Published: 2007-01-23
Products: rPath Linux 1
Rating: Informational
Exposure Level Classification:
Indirect Deterministic Denial of Service
Updated Versions:
wget=/conary.rpath.com at rpl:devel//1/1.10.2-4-0.1

References:
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-6719
https://issues.rpath.com/browse/RPL-930

Description:
Previous versions of the wget package can crash if they contact a
malicious FTP server. No further vulnerability is enabled by this
minor flaw; system security is not threatened in any way.

ed (symlink attack)

rPSA-2007-0012-1 ed
rPath Update Announcements announce-noreply at rpath.com
Tue Jan 23 03:45:58 EST 2007

Previous message: rPSA-2007-0011-1 wget
Next message: rPSA-2007-0013-1 poppler tetex tetex-afm tetex-dvips tetex-fonts tetex-latex tetex-xdvi
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

--------------------------------------------------------------------------------

rPath Security Advisory: 2007-0012-1
Published: 2007-01-23
Products: rPath Linux 1
Rating: Minor
Exposure Level Classification:
Local User Non-deterministic Vulnerability
Updated Versions:
ed=/conary.rpath.com at rpl:devel//1/0.4-1-0.1

References:
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-6939
https://issues.rpath.com/browse/RPL-962

Description:
Previous versions of the ed package are vulnerable to a symlink
attack which allows a local attacker to overwrite arbitrary files
writeable by the user running ed with contents provided by the
user running the ed program.

poppler (denial of service, code execution)

rPSA-2007-0013-1 poppler tetex tetex-afm tetex-dvips tetex-fonts tetex-latex tetex-xdvi
rPath Update Announcements announce-noreply at rpath.com
Tue Jan 23 03:47:10 EST 2007

Previous message: rPSA-2007-0012-1 ed
Next message: rPSA-2007-0014-1 libgtop
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

--------------------------------------------------------------------------------

rPath Security Advisory: 2007-0013-1
Published: 2007-01-23
Products: rPath Linux 1
Rating: Major
Exposure Level Classification:
Indirect User Deterministic Denial of Service
Updated Versions:
poppler=/conary.rpath.com at rpl:devel//1/0.4.5-1.1-1
tetex=/conary.rpath.com at rpl:devel//1/2.0.2-28.4-1
tetex-afm=/conary.rpath.com at rpl:devel//1/2.0.2-28.4-1
tetex-dvips=/conary.rpath.com at rpl:devel//1/2.0.2-28.4-1
tetex-fonts=/conary.rpath.com at rpl:devel//1/2.0.2-28.4-1
tetex-latex=/conary.rpath.com at rpl:devel//1/2.0.2-28.4-1
tetex-xdvi=/conary.rpath.com at rpl:devel//1/2.0.2-28.4-1

References:
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-0104
https://issues.rpath.com/browse/RPL-964

Description:
Previous versions of the poppler and tetex packages are vulnerable to
an attack in which an intentionally malformed PDF file can create at
least a minor Denial of Service attack on the PDF application, and
may possibly allow for directed or arbitrary code execution.

libgtop (denial of service, code execution)

rPSA-2007-0014-2 libgtop
rPath Update Announcements announce-noreply at rpath.com
Wed Jan 24 15:38:41 EST 2007

Previous message: rPSA-2007-0015-1 libsoup
Next message: rPSA-2007-0019-1 gtk
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

--------------------------------------------------------------------------------

rPath Security Advisory: 2007-0014-2
Published: 2007-01-23
Updated:
2007-01-24 locale information restored
Products: rPath Linux 1
Rating: Major
Exposure Level Classification:
Local User Deterministic Denial of Service
Updated Versions:
libgtop=/conary.rpath.com at rpl:devel//1/2.12.0-1.3-1

References:
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-0235
https://issues.rpath.com/browse/RPL-972

Description:
Previous versions of the libgtop package are vulnerable to an attack
in which a local user can at least cause programs that use libgtop
(such as gnome-system-monitor) to crash, and possibly to execute
arbitrary code as the user running the program.

24 January 2007 Update: The initial fix for this vulnerability
inadvertently removed locale information. This has been resolved.

libsoup (denial of service)

rPSA-2007-0015-1 libsoup
rPath Update Announcements announce-noreply at rpath.com
Tue Jan 23 03:49:02 EST 2007

Previous message: rPSA-2007-0014-1 libgtop
Next message: rPSA-2007-0014-2 libgtop
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

--------------------------------------------------------------------------------

rPath Security Advisory: 2007-0015-1
Published: 2007-01-23
Products: rPath Linux 1
Rating: Minor
Exposure Level Classification:
Indirect Denial of Service
Updated Versions:
libsoup=/conary.rpath.com at rpl:devel//1/2.2.99-1-0.1

References:
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-5876
https://issues.rpath.com/browse/RPL-965

Description:
Previous versions of the libsoup package are vulnerable to an indirect
denial of service in which a malicious or faulty server responds to
requests with malformed HTTP headers, causing the application that
uses libsoup to crash.

xine (multiple format string flaws)

Date: Tue, 23 Jan 2007 11:07:59 +0100
From: Thomas Biege
To: suse-security-announce@suse.com
Subject: SUSE Security Announcement: xine (SUSE-SA:2007:013)

-----BEGIN PGP SIGNED MESSAGE-----

______________________________________________________________________________

SUSE Security Announcement

Package: xine-ui,xine-lib,xine-extra,xine-devel
Announcement ID: SUSE-SA:2007:013
Date: Tue, 23 Jan 2007 08:00:00 +0000
Affected Products: SUSE LINUX 9.3
SUSE LINUX 10.0
SUSE LINUX 10.1
openSUSE 10.2
SUSE SLED 10
SLE SDK 10
Vulnerability Type: remote code execution
Severity (1-10): 4
SUSE Default Package: no
Cross-References: CVE-2007-0017

Content of This Advisory:
1) Security Vulnerability Resolved:
format string bug
Problem Description
2) Solution or Work-Around
3) Special Instructions and Notes
4) Package Location and Checksums
5) Pending Vulnerabilities, Solutions, and Work-Arounds:
none
6) Authenticity Verification and Additional Information

______________________________________________________________________________

1) Problem Description and Brief Discussion

This update fixes several format string bugs that can be exploited remotely
with user-assistance to execute arbitrary code.
Since SUSE Linux version 10.1 format string bugs are not exploitable
anymore. (CVE-2007-0017)

2) Solution or Work-Around

No temporary work-around known.

3) Special Instructions and Notes

none

4) Package Location and Checksums

The preferred method for installing security updates is to use the YaST
Online Update (YOU) tool. YOU detects which updates are required and
automatically performs the necessary steps to verify and install them.
Alternatively, download the update packages for your distribution manually
and verify their integrity by the methods listed in Section 6 of this
announcement. Then install the packages using the command

rpm -Fhv

to apply the update, replacing with the filename of the
downloaded RPM package.

x86 Platform:

openSUSE 10.2:
ftp://ftp.suse.com/pub/suse/update/10.2/rpm/i586/xine-devel-1.1.2-40.1.i586.rpm
2cacbb4f4e177362149518481480165a
ftp://ftp.suse.com/pub/suse/update/10.2/rpm/i586/xine-extra-1.1.2-40.1.i586.rpm
73cbdd8d443596547875804bd8e2ca8f
ftp://ftp.suse.com/pub/suse/update/10.2/rpm/i586/xine-lib-1.1.2-40.1.i586.rpm
2114f7c6a4c8351adab588c173419778
ftp://ftp.suse.com/pub/suse/update/10.2/rpm/i586/xine-ui-0.99.4-84.1.i586.rpm
5d4dd945a812ba0b17619c267ec8f2b5

SUSE LINUX 10.1:
ftp://ftp.suse.com/pub/suse/update/10.1/rpm/i586/xine-extra-1.1.1-24.17.i586.rpm
3eb1465401e5e1c6f36d8e2d7ca3e114
ftp://ftp.suse.com/pub/suse/update/10.1/rpm/i586/xine-lib-1.1.1-24.17.i586.rpm
e2fbf53b629e835dbc2558e87fabf926
ftp://ftp.suse.com/pub/suse/update/10.1/rpm/i586/xine-ui-0.99.4-32.14.i586.rpm
d710db4b4d20f7ea4485d16845cb4be2

SUSE LINUX 10.0:
ftp://ftp.suse.com/pub/suse/i386/update/10.0/rpm/i586/xine-extra-1.1.0-0.1.i586.rpm
06753ebd3608223077c95c01f8bc3122
ftp://ftp.suse.com/pub/suse/i386/update/10.0/rpm/i586/xine-lib-1.1.0-0.1.i586.rpm
60ab4fd7c193d687d9484e5691aa3f01
ftp://ftp.suse.com/pub/suse/i386/update/10.0/rpm/i586/xine-ui-0.99.4-84.1.i586.rpm
4bc3f28d7e600fbb78c65f6b0dcfc436

SUSE LINUX 9.3:
ftp://ftp.suse.com/pub/suse/i386/update/9.3/rpm/i586/xine-lib-1.0-10.14.i586.rpm
c944ed72f913771f0c2300883573e111
ftp://ftp.suse.com/pub/suse/i386/update/9.3/rpm/i586/xine-ui-1.0-10.14.i586.rpm
cee2a8a9669b429dde4e465e83aae70f

Power PC Platform:

openSUSE 10.2:
ftp://ftp.suse.com/pub/suse/update/10.2/rpm/ppc/xine-lib-1.1.2-40.1.ppc.rpm
a1fcfa82deed685446a213439639a579
ftp://ftp.suse.com/pub/suse/update/10.2/rpm/ppc/xine-ui-0.99.4-84.1.ppc.rpm
bc2dcf2266dbb56b1a0291209aad2dd7

SUSE LINUX 10.1:
ftp://ftp.suse.com/pub/suse/update/10.1/rpm/ppc/xine-extra-1.1.1-24.17.ppc.rpm
c337440571123263478dd2a64059a4e8
ftp://ftp.suse.com/pub/suse/update/10.1/rpm/ppc/xine-lib-1.1.1-24.17.ppc.rpm
3cf476901522d7b5abd5bf3cb18484a9
ftp://ftp.suse.com/pub/suse/update/10.1/rpm/ppc/xine-ui-0.99.4-32.14.ppc.rpm
a9e762bad246963a7564c1f36a5f0392

SUSE LINUX 10.0:
ftp://ftp.suse.com/pub/suse/i386/update/10.0/rpm/ppc/xine-extra-1.1.0-0.1.ppc.rpm
930dc314de3ab49a8655e6cdb89ff50d
ftp://ftp.suse.com/pub/suse/i386/update/10.0/rpm/ppc/xine-lib-1.1.0-0.1.ppc.rpm
ddd255708abfb433a3497d790491be55
ftp://ftp.suse.com/pub/suse/i386/update/10.0/rpm/ppc/xine-ui-0.99.4-84.1.ppc.rpm
827125d558472b685f0f1843d0eb3850

x86-64 Platform:

openSUSE 10.2:
ftp://ftp.suse.com/pub/suse/update/10.2/rpm/x86_64/xine-devel-1.1.2-40.1.x86_64.rpm
1dac6b23d257670ca7182f018c12a69b
ftp://ftp.suse.com/pub/suse/update/10.2/rpm/x86_64/xine-extra-1.1.2-40.1.x86_64.rpm
11dae8e2ecb5a78eb6b1cd39713f6322
ftp://ftp.suse.com/pub/suse/update/10.2/rpm/x86_64/xine-lib-1.1.2-40.1.x86_64.rpm
519480f44a28d4e3cab37aceca7e7c13
ftp://ftp.suse.com/pub/suse/update/10.2/rpm/x86_64/xine-lib-32bit-1.1.2-40.1.x86_64.rpm
3b5db06dab41a4ff2a53d22b3f6f6238
ftp://ftp.suse.com/pub/suse/update/10.2/rpm/x86_64/xine-ui-0.99.4-84.1.x86_64.rpm
b1a06bf5fd93c905bf5008859c88690d
ftp://ftp.suse.com/pub/suse/update/10.2/rpm/x86_64/xine-ui-32bit-0.99.4-84.1.x86_64.rpm
aa85b56d559aca4960693bad80a451bd

SUSE LINUX 10.1:
ftp://ftp.suse.com/pub/suse/update/10.1/rpm/x86_64/xine-extra-1.1.1-24.17.x86_64.rpm
72f6cfc29f428a5d7dc40fbcb285cfe6
ftp://ftp.suse.com/pub/suse/update/10.1/rpm/x86_64/xine-lib-1.1.1-24.17.x86_64.rpm
34382ef5b0ec94524678bdf842a21ecb
ftp://ftp.suse.com/pub/suse/update/10.1/rpm/x86_64/xine-lib-32bit-1.1.1-24.17.x86_64.rpm
316fd37892ef25073cf9d6ae11fb510b
ftp://ftp.suse.com/pub/suse/update/10.1/rpm/x86_64/xine-ui-0.99.4-32.14.x86_64.rpm
ee0a3ce52f3bf431ced82dbd0148890c

SUSE LINUX 10.0:
ftp://ftp.suse.com/pub/suse/i386/update/10.0/rpm/x86_64/xine-extra-1.1.0-0.1.x86_64.rpm
83094481db18fb55447a19b86db281ff
ftp://ftp.suse.com/pub/suse/i386/update/10.0/rpm/x86_64/xine-lib-1.1.0-0.1.x86_64.rpm
0e1b36454127be6815d1f52325ee1a70
ftp://ftp.suse.com/pub/suse/i386/update/10.0/rpm/x86_64/xine-lib-32bit-1.1.0-0.1.x86_64.rpm
45829c44efd83afaefe570d81f8a7568
ftp://ftp.suse.com/pub/suse/i386/update/10.0/rpm/x86_64/xine-ui-0.99.4-84.1.x86_64.rpm
bfe5d54a07d28cb9fef528c0257d4db7

SUSE LINUX 9.3:
ftp://ftp.suse.com/pub/suse/i386/update/9.3/rpm/x86_64/xine-lib-1.0-10.14.x86_64.rpm
e829f9cbd5e02a0498f03a2180b57963
ftp://ftp.suse.com/pub/suse/i386/update/9.3/rpm/x86_64/xine-lib-32bit-9.3-0.1.x86_64.rpm
064665c8b3ac38f71634734c101f1602
ftp://ftp.suse.com/pub/suse/i386/update/9.3/rpm/x86_64/xine-ui-1.0-10.14.x86_64.rpm
8e7011003db37a1799bbd531ae957a28

Sources:

openSUSE 10.2:
ftp://ftp.suse.com/pub/suse/update/10.2/rpm/src/xine-lib-1.1.2-40.1.src.rpm
f92b96c21a6e45ede2faa81c9efade83
ftp://ftp.suse.com/pub/suse/update/10.2/rpm/src/xine-ui-0.99.4-84.1.src.rpm
ed0382a57f117bcf04236ca660092afe

SUSE LINUX 10.1:
ftp://ftp.suse.com/pub/suse/update/10.1/rpm/src/xine-lib-1.1.1-24.17.src.rpm
1d347a598b2e8dfc5eaa4f7b9c951242

SUSE LINUX 10.0:
ftp://ftp.suse.com/pub/suse/i386/update/10.0/rpm/src/xine-lib-1.1.0-0.1.nosrc.rpm
d1d2036b46056a00b3c5a0cee5371ad8

SUSE LINUX 9.3:
ftp://ftp.suse.com/pub/suse/i386/update/9.3/rpm/src/xine-lib-1.0-10.14.nosrc.rpm
02ae3f6c9a88ec0aabcce701bba20542

Our maintenance customers are notified individually. The packages are
offered for installation from the maintenance web:

SLE SDK 10
http://support.novell.com/techcenter/psdb/3850f4cb30959892275d84ebf0b1dfc6.html

SUSE SLED 10
http://support.novell.com/techcenter/psdb/3850f4cb30959892275d84ebf0b1dfc6.html

______________________________________________________________________________

5) Pending Vulnerabilities, Solutions, and Work-Arounds:

none
______________________________________________________________________________

6) Authenticity Verification and Additional Information

- Announcement authenticity verification:

SUSE security announcements are published via mailing lists and on Web
sites. The authenticity and integrity of a SUSE security announcement is
guaranteed by a cryptographic signature in each announcement. All SUSE
security announcements are published with a valid signature.

To verify the signature of the announcement, save it as text into a file
and run the command

gpg --verify

replacing with the name of the file where you saved the
announcement. The output for a valid signature looks like:

gpg: Signature made using RSA key ID 3D25D3D9
gpg: Good signature from "SuSE Security Team "

where is replaced by the date the document was signed.

If the security team's key is not contained in your key ring, you can
import it from the first installation CD. To import the key, use the
command

gpg --import gpg-pubkey-3d25d3d9-36e12d04.asc

- Package authenticity verification:

SUSE update packages are available on many mirror FTP servers all over the
world. While this service is considered valuable and important to the free
and open source software community, the authenticity and the integrity of
a package needs to be verified to ensure that it has not been tampered
with.

There are two verification methods that can be used independently from
each other to prove the authenticity of a downloaded file or RPM package:

1) Using the internal gpg signatures of the rpm package
2) MD5 checksums as provided in this announcement

1) The internal rpm package signatures provide an easy way to verify the
authenticity of an RPM package. Use the command

rpm -v --checksig

to verify the signature of the package, replacing with the
filename of the RPM package downloaded. The package is unmodified if it
contains a valid signature from build@suse.de with the key ID 9C800ACA.

This key is automatically imported into the RPM database (on
RPMv4-based distributions) and the gpg key ring of 'root' during
installation. You can also find it on the first installation CD and at
the end of this announcement.

2) If you need an alternative means of verification, use the md5sum
command to verify the authenticity of the packages. Execute the command

md5sum

after you downloaded the file from a SUSE FTP server or its mirrors.
Then compare the resulting md5sum with the one that is listed in the
SUSE security announcement. Because the announcement containing the
checksums is cryptographically signed (by security@suse.de), the
checksums show proof of the authenticity of the package if the
signature of the announcement is valid. Note that the md5 sums
published in the SUSE Security Announcements are valid for the
respective packages only. Newer versions of these packages cannot be
verified.

- SUSE runs two security mailing lists to which any interested party may
subscribe:

opensuse-security@opensuse.org
- General Linux and SUSE security discussion.
All SUSE security announcements are sent to this list.
To subscribe, send an e-mail to
.

suse-security-announce@suse.com
- SUSE's announce-only mailing list.
Only SUSE's security announcements are sent to this list.
To subscribe, send an e-mail to
.

=====================================================================
SUSE's security contact is or .
The public key is listed below.
=====================================================================
______________________________________________________________________________

The information in this advisory may be distributed or reproduced,
provided that the advisory is not modified in any way. In particular, the
clear text signature should show proof of the authenticity of the text.

SUSE Linux Products GmbH provides no warranties of any kind whatsoever
with respect to the information contained in this security advisory.

squid (denial of service)

Date: Tue, 23 Jan 2007 11:07:29 +0100
From: Thomas Biege
To: suse-security-announce@suse.com
Subject: SUSE Security Announcement: squid (SUSE-SA:2007:012)

-----BEGIN PGP SIGNED MESSAGE-----

______________________________________________________________________________

SUSE Security Announcement

Package: squid
Announcement ID: SUSE-SA:2007:012
Date: Tue, 23 Jan 2007 09:00:00 +0000
Affected Products: SUSE LINUX 9.3
SUSE LINUX 10.0
SUSE LINUX 10.1
openSUSE 10.2
UnitedLinux 1.0
SuSE Linux Enterprise Server 8
SuSE Linux Openexchange Server 4
SuSE Linux Standard Server 8
SuSE Linux School Server
SUSE LINUX Retail Solution 8
SUSE SLES 9
Open Enterprise Server
Novell Linux POS 9
SUSE SLED 10
SUSE SLES 10
Vulnerability Type: remote denial of service
Severity (1-10): 4
SUSE Default Package: no
Cross-References: CVE-2007-0247
CVE-2007-0248

Content of This Advisory:
1) Security Vulnerability Resolved:
remote denial of service
Problem Description
2) Solution or Work-Around
3) Special Instructions and Notes
4) Package Location and Checksums
5) Pending Vulnerabilities, Solutions, and Work-Arounds:
none
6) Authenticity Verification and Additional Information

______________________________________________________________________________

1) Problem Description and Brief Discussion

This update fixes a remotely exploitable denial-of-service
bug in squid that can be triggered by using special ftp://
URLs. (CVE-2007-0247)
Additionally the 10.2 package needed a fix for another DoS
bug (CVE-2007-0248) and for max_user_ip handling in
ntlm_auth.

2) Solution or Work-Around

No temporary work-around known.

3) Special Instructions and Notes

Restart squid.

4) Package Location and Checksums

The preferred method for installing security updates is to use the YaST
Online Update (YOU) tool. YOU detects which updates are required and
automatically performs the necessary steps to verify and install them.
Alternatively, download the update packages for your distribution manually
and verify their integrity by the methods listed in Section 6 of this
announcement. Then install the packages using the command

rpm -Fhv

to apply the update, replacing with the filename of the
downloaded RPM package.

x86 Platform:

openSUSE 10.2:
ftp://ftp.suse.com/pub/suse/update/10.2/rpm/i586/squid-2.6.STABLE6-0.4.i586.rpm
c1a38e8dc8301158fe717a9115e60001

SUSE LINUX 10.1:
ftp://ftp.suse.com/pub/suse/update/10.1/rpm/i586/squid-2.5.STABLE12-18.6.i586.rpm
b390a43cd014988f3444fc8a3f89af7d

SUSE LINUX 10.0:
ftp://ftp.suse.com/pub/suse/i386/update/10.0/rpm/i586/squid-2.5.STABLE10-5.5.i586.rpm
171ae4d1ae9941da3641391f0cbb020e

SUSE LINUX 9.3:
ftp://ftp.suse.com/pub/suse/i386/update/9.3/rpm/i586/squid-2.5.STABLE9-4.9.i586.rpm
5abca23e37cee2bf20085951b8a59953

Power PC Platform:

openSUSE 10.2:
ftp://ftp.suse.com/pub/suse/update/10.2/rpm/ppc/squid-2.6.STABLE6-0.4.ppc.rpm
ffb0c8fe4086a913fede3cba0f1b473c

SUSE LINUX 10.1:
ftp://ftp.suse.com/pub/suse/update/10.1/rpm/ppc/squid-2.5.STABLE12-18.6.ppc.rpm
bec76f3f1c4a445801117f696d438925

SUSE LINUX 10.0:
ftp://ftp.suse.com/pub/suse/i386/update/10.0/rpm/ppc/squid-2.5.STABLE10-5.5.ppc.rpm
87fc216ed79eee0d5eecf2ba24d4adfe

x86-64 Platform:

openSUSE 10.2:
ftp://ftp.suse.com/pub/suse/update/10.2/rpm/x86_64/squid-2.6.STABLE6-0.4.x86_64.rpm
6b37f676418485c52d262cc8f17347f0

SUSE LINUX 10.1:
ftp://ftp.suse.com/pub/suse/update/10.1/rpm/x86_64/squid-2.5.STABLE12-18.6.x86_64.rpm
ddc9aaba2e99eeb2d8215acf799b8ecb

SUSE LINUX 10.0:
ftp://ftp.suse.com/pub/suse/i386/update/10.0/rpm/x86_64/squid-2.5.STABLE10-5.5.x86_64.rpm
100ed655a1fbdcf4a8ed1bd98598e2bb

SUSE LINUX 9.3:
ftp://ftp.suse.com/pub/suse/i386/update/9.3/rpm/x86_64/squid-2.5.STABLE9-4.9.x86_64.rpm
599d0bb6f1cd872816eb371abf24a44e

Sources:

openSUSE 10.2:
ftp://ftp.suse.com/pub/suse/update/10.2/rpm/src/squid-2.6.STABLE6-0.4.src.rpm
8467df81f96919f3a1c6d55905581735

SUSE LINUX 10.1:
ftp://ftp.suse.com/pub/suse/update/10.1/rpm/src/squid-2.5.STABLE12-18.6.src.rpm
5da1a897fdb953cb3f9801d0eda1899b

SUSE LINUX 10.0:
ftp://ftp.suse.com/pub/suse/i386/update/10.0/rpm/src/squid-2.5.STABLE10-5.5.src.rpm
794090e751edceb8355c4706a28c2aa5

SUSE LINUX 9.3:
ftp://ftp.suse.com/pub/suse/i386/update/9.3/rpm/src/squid-2.5.STABLE9-4.9.src.rpm
6c6c1a9a0e0db47a3336d51551a859e9

Our maintenance customers are notified individually. The packages are
offered for installation from the maintenance web:

UnitedLinux 1.0
http://support.novell.com/techcenter/psdb/e4f5424c0eb495e52b8739b57f62405b.html

SuSE Linux Openexchange Server 4
http://support.novell.com/techcenter/psdb/e4f5424c0eb495e52b8739b57f62405b.html

Open Enterprise Server
http://support.novell.com/techcenter/psdb/e4f5424c0eb495e52b8739b57f62405b.html

Novell Linux POS 9
http://support.novell.com/techcenter/psdb/e4f5424c0eb495e52b8739b57f62405b.html

SuSE Linux Enterprise Server 8
http://support.novell.com/techcenter/psdb/e4f5424c0eb495e52b8739b57f62405b.html

SuSE Linux Standard Server 8
http://support.novell.com/techcenter/psdb/e4f5424c0eb495e52b8739b57f62405b.html

SuSE Linux School Server
http://support.novell.com/techcenter/psdb/e4f5424c0eb495e52b8739b57f62405b.html

SUSE LINUX Retail Solution 8
http://support.novell.com/techcenter/psdb/e4f5424c0eb495e52b8739b57f62405b.html

SUSE SLES 10
http://support.novell.com/techcenter/psdb/e4f5424c0eb495e52b8739b57f62405b.html

SUSE SLED 10
http://support.novell.com/techcenter/psdb/e4f5424c0eb495e52b8739b57f62405b.html

SUSE SLES 9
http://support.novell.com/techcenter/psdb/e4f5424c0eb495e52b8739b57f62405b.html

______________________________________________________________________________

5) Pending Vulnerabilities, Solutions, and Work-Arounds:

none
______________________________________________________________________________

6) Authenticity Verification and Additional Information

- Announcement authenticity verification:

SUSE security announcements are published via mailing lists and on Web
sites. The authenticity and integrity of a SUSE security announcement is
guaranteed by a cryptographic signature in each announcement. All SUSE
security announcements are published with a valid signature.

To verify the signature of the announcement, save it as text into a file
and run the command

gpg --verify

replacing with the name of the file where you saved the
announcement. The output for a valid signature looks like:

gpg: Signature made using RSA key ID 3D25D3D9
gpg: Good signature from "SuSE Security Team "

where is replaced by the date the document was signed.

If the security team's key is not contained in your key ring, you can
import it from the first installation CD. To import the key, use the
command

gpg --import gpg-pubkey-3d25d3d9-36e12d04.asc

- Package authenticity verification:

SUSE update packages are available on many mirror FTP servers all over the
world. While this service is considered valuable and important to the free
and open source software community, the authenticity and the integrity of
a package needs to be verified to ensure that it has not been tampered
with.

There are two verification methods that can be used independently from
each other to prove the authenticity of a downloaded file or RPM package:

1) Using the internal gpg signatures of the rpm package
2) MD5 checksums as provided in this announcement

1) The internal rpm package signatures provide an easy way to verify the
authenticity of an RPM package. Use the command

rpm -v --checksig

to verify the signature of the package, replacing with the
filename of the RPM package downloaded. The package is unmodified if it
contains a valid signature from build@suse.de with the key ID 9C800ACA.

This key is automatically imported into the RPM database (on
RPMv4-based distributions) and the gpg key ring of 'root' during
installation. You can also find it on the first installation CD and at
the end of this announcement.

2) If you need an alternative means of verification, use the md5sum
command to verify the authenticity of the packages. Execute the command

md5sum

after you downloaded the file from a SUSE FTP server or its mirrors.
Then compare the resulting md5sum with the one that is listed in the
SUSE security announcement. Because the announcement containing the
checksums is cryptographically signed (by security@suse.de), the
checksums show proof of the authenticity of the package if the
signature of the announcement is valid. Note that the md5 sums
published in the SUSE Security Announcements are valid for the
respective packages only. Newer versions of these packages cannot be
verified.

- SUSE runs two security mailing lists to which any interested party may
subscribe:

opensuse-security@opensuse.org
- General Linux and SUSE security discussion.
All SUSE security announcements are sent to this list.
To subscribe, send an e-mail to
.

suse-security-announce@suse.com
- SUSE's announce-only mailing list.
Only SUSE's security announcements are sent to this list.
To subscribe, send an e-mail to
.

=====================================================================
SUSE's security contact is or .
The public key is listed below.
=====================================================================
______________________________________________________________________________

The information in this advisory may be distributed or reproduced,
provided that the advisory is not modified in any way. In particular, the
clear text signature should show proof of the authenticity of the text.

SUSE Linux Products GmbH provides no warranties of any kind whatsoever
with respect to the information contained in this security advisory.

Type Bits/KeyID Date User ID
pub 2048R/3D25D3D9 1999-03-06 SuSE Security Team
pub 1024D/9C800ACA 2000-10-19 SuSE Package Signing Key

Cisco Security Advisory: IPv6 Routing Header Vulnerability

Document ID: 72372
Advisory ID: cisco-sa-20070124-IOS-IPv6
http://www.cisco.com/warp/public/707/cisco-sa-20070124-IOS-IPv6.shtml
1.0
For Public Release 2007 January 24 1600 UTC (GMT)

--------------------------------------------------------------------------------

Please provide your feedback on this document.

--------------------------------------------------------------------------------

Contents
Summary
Affected Products
Details
Impact
Software Version and Fixes
Workarounds
Obtaining Fixed Software
Exploitation and Public Announcements
Status of this Notice:FINAL
Distribution
Revision History
Cisco Security Procedures

--------------------------------------------------------------------------------

Summary
Processing a specially crafted IPv6 Type 0 Routing header can crash a device running Cisco IOS software. This vulnerability does not affect IPv6 Type 2 Routing header which is used in mobile IPv6. IPv6 is not enabled by default in Cisco IOS.

Cisco has made free software available to address this vulnerability for affected customers.

There are workarounds available to mitigate the effects of the vulnerability. The workaround depends on if Mobile IPv6 is used and what version on Cisco IOS is being currently used.

This vulnerability was initially reported by a customer and further trigger vector was discovered during developing the fix for this vulnerability.

This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20070124-IOS-IPv6.shtml.

Affected Products
Devices running Cisco IOS and having IPv6 enabled on, at least, one of their interface may be affected by this vulnerability.

Vulnerable Products
To determine the software running on a Cisco product, log in to the device and issue the show version command to display the system banner. Cisco IOS software will identify itself as "Internetwork Operating System Software" or simply "IOS". On the next line of output, the image name will be displayed between parentheses, followed by "Version" and the IOS release name. Other Cisco devices will not have the show version command or will give different output.

The following example identifies a Cisco product running IOS release 12.4(9.10):

Cisco IOS Software, 7200 Software (C7200-JK9O3S-M), Version 12.4(9.10), INTERIM SOFTWARE
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2006 by Cisco Systems, Inc.
Compiled Mon 29-May-06 04:42 by prod_rel_teamAdditional information about Cisco IOS release naming can be found at http://www.cisco.com/warp/public/620/1.html.

Products Confirmed Not Vulnerable
No other Cisco products are known to be vulnerable to the issue described in this Advisory. In particular Cisco IOS XR, Cisco PIX Appliance and Cisco MDS 9000 Series devices are not affected by this vulnerability.

Details
This vulnerability can be triggered only when Cisco IOS processes specifically crafted IPv6 Type 0 Routing headers, which are used for source routing. Source routing is when an originator node explicitly specifies the exact path that a packet must take to reach the destination. Source routing is enabled by default on Cisco IOS if IPv6 is configured on the device. In order to trigger this vulnerability the packet must be destined to any of the IPv6 addresses defined on the device. The exact packet type is not relevant (e.g., TCP, ICMP, UDP) as the vulnerability is on the IP layer. For this reason care must be taken when implementing a workaround as this vulnerability can be triggered by a spoofed packet.

IPv6 multicast packets can not be used to trigger this vulnerability.

In addition to Type 0 Routing headers, IPv6 also supports Type 2 Routing that is used in Mobile IPv6 implementation. Type 2 Routing headers can not be used to trigger the vulnerability described in this Advisory.

A router running vulnerable Cisco IOS software will process Type 0 Routing headers only if the destination address in the IPv6 packet is one of the IPv6 addresses defined on any of the interfaces. The address may be either a global (i.e., routable), loopback or link local address. Link local addresses are not supposed to be routable and they are valid only among directly connected devices.

A device may also be susceptible in scenarios where IPv6 packets are tunneled over IPv4 networks provided that the IPv6 destination address (after de-encapsulation) is one of the IPv6 addresses defined on the device. This is independent of the exact encapsulation method used (e.g., MPLS, GRE or IPv6-in-IPv4).

This vulnerability is documented in Cisco Bug IDs CSCsd40334 ( registered customers only) and CSCsd58381 ( registered customers only) .

Vulnerability Scoring Details
Cisco is providing scores for the vulnerabilities in this advisory based on the Common Vulnerability Scoring System (CVSS).

Cisco will provide a base and temporal score. Customers can then compute environmental scores to assist in determining the impact of the vulnerability in individual networks.

Cisco PSIRT will set the bias in all cases to normal. Customers are encouraged to apply the bias parameter when determining the environmental impact of a particular vulnerability.

CVSS is a standards based scoring method that conveys vulnerability severity and helps determine urgency and priority of response.

Cisco has provided an FAQ to answer additional questions regarding CVSS at http://www.cisco.com/web/about/security/intelligence/cvss-qandas.html.

Cisco has also provided a CVSS calculator to help compute the environmental impact for individual networks at http://intellishield.cisco.com/security/alertmanager/cvss.

CSCsd40334 - IPv6 packet can cause crash ( registered customers only)

CVSS Base Score - 10

Access Vector
Access Complexity
Authentication
Confidentiality Impact
Integrity Impact
Availability Impact
Impact Bias

Remote
Low
Not Required
Complete
Complete
Complete
Normal

CVSS Temporal Score - 8.3

Exploitability
Remediation Level
Report Confidence

Functional
Official Fix
Confirmed

CSCsd58381 - IPv6 routing header limitation ( registered customers only)

CVSS Base Score - 10

Access Vector
Access Complexity
Authentication
Confidentiality Impact
Integrity Impact
Availability Impact
Impact Bias

Remote
Low
Not Required
Complete
Complete
Complete
Normal

CVSS Temporal Score - 8.3

Exploitability
Remediation Level
Report Confidence

Functional
Official Fix
Confirmed

Impact
Successful exploitation of the vulnerability listed in this Advisory can corrupt some memory structures. In most cases this will cause the affected device to crash and repeated exploitation could result in a sustained DoS attack. However, due to memory corruption, there is a potential to execute an arbitrary code. In the event of a successful remote code execution, device integrity will have been completely compromised.

Software Version and Fixes
When considering software upgrades, also consult http://www.cisco.com/go/psirt and any subsequent advisories to determine exposure and a complete upgrade solution.

In all cases, customers should exercise caution to be certain the devices to be upgraded contain sufficient memory and that current hardware and software configurations will continue to be supported properly by the new release. If the information is not clear, contact the Cisco Technical Assistance Center ("TAC") or your contracted maintenance provider for assistance.

Each row of the Cisco IOS software table (below) describes a release train and the platforms or products for which it is intended. If a given release train is vulnerable, then the earliest possible releases that contain the fix (the "First Fixed Release") and the anticipated date of availability for each are listed in the "Rebuild" and "Maintenance" columns. A device running a release in the given train that is earlier than the release in a specific column (less than the First Fixed Release) is known to be vulnerable. The release should be upgraded at least to the indicated release or a later version (greater than or equal to the First Fixed Release label).

For more information on the terms "Rebuild" and "Maintenance," consult the following URL: http://www.cisco.com/warp/public/620/1.html.

Note: There are three IOS security advisories and one field notice being published on January 24, 2007. Each advisory only lists the releases which fix the issue described in the advisory. A combined software table is available at http://www.cisco.com/warp/public/707/cisco-sa-20070124-bundle.shtml and can be used to choose a software release which fixes all security vulnerabilities published as of January 24, 2007. The advisories and field notice published on January 24 are listed here.

http://www.cisco.com/warp/public/707/cisco-air-20070124-IOS-ipv6.shtml

http://www.cisco.com/warp/public/707/cisco-sa-20070124-crafted-tcp.shtml

http://www.cisco.com/warp/public/707/cisco-sa-20070124-crafted-ip-option.shtml

http://www.cisco.com/warp/public/770/fn62613.shtml

Requests for software rebuilds to include the change for Daylight Savings Time (DST) that will be implemented in March 2007 should be directed through the Technical Assistance Center (TAC) and this advisory should be used as reference.

Major Release
Availability of Repaired Releases

Affected 12.0-Based Release
Rebuild
Maintenance

12.0
Not vulnerable

12.0DA
Not vulnerable

12.0DB
Not vulnerable

12.0DC
Not vulnerable

12.0S
12.0(32)S3

12.0SC
Not vulnerable

12.0SL
Not vulnerable

12.0SP
Not vulnerable

12.0ST
Vulnerable; migrate to 12.0(32)S3 or later

12.0SX
Vulnerable for only 12.0(30)SX; contact TAC

12.0SY
12.0(32)SY

12.0SZ
Vulnerable; migrate to 12.0(32)S3 or later

12.0T
Not vulnerable

12.0W
Not vulnerable

12.0WC
Not vulnerable

12.0WT
Not vulnerable

12.0XA
Not vulnerable

12.0XB
Not vulnerable

12.0XC
Not vulnerable

12.0XD
Not vulnerable

12.0XE
Not vulnerable

12.0XF
Not vulnerable

12.0XG
Not vulnerable

12.0XH
Not vulnerable

12.0XI
Not vulnerable

12.0XJ
Not vulnerable

12.0XK
Not vulnerable

12.0XL
Not vulnerable

12.0XM
Not vulnerable

12.0XN
Not vulnerable

12.0XQ
Not vulnerable

12.0XR
Not vulnerable

12.0XS
Not vulnerable

12.0XV
Not vulnerable

12.0XW
Not vulnerable

Affected 12.1-Based Release
Rebuild
Maintenance

12.1
Not vulnerable

12.1AA
Not vulnerable

12.1AX
Not vulnerable

12.1AY
Not vulnerable

12.1AZ
Not vulnerable

12.1CX
Not vulnerable

12.1DA
Not vulnerable

12.1DB
Not vulnerable

12.1DC
Not vulnerable

12.1E
Not vulnerable

12.1EA
Not vulnerable

12.1EB
Not vulnerable

12.1EC
Not vulnerable

12.1EO
Not vulnerable

12.1EU
Not vulnerable

12.1EV
Not vulnerable

12.1EW
Not vulnerable

12.1EX
Not vulnerable

12.1EY
Not vulnerable

12.1EZ
Not vulnerable

12.1T
Not vulnerable

12.1XA
Not vulnerable

12.1XB
Not vulnerable

12.1XC
Not vulnerable

12.1XD
Not vulnerable

12.1XE
Not vulnerable

12.1XF
Not vulnerable

12.1XG
Not vulnerable

12.1XH
Not vulnerable

12.1XI
Not vulnerable

12.1XJ
Not vulnerable

12.1XL
Not vulnerable

12.1XM
Not vulnerable

12.1XP
Not vulnerable

12.1XQ
Not vulnerable

12.1XR
Not vulnerable

12.1XS
Not vulnerable

12.1XT
Not vulnerable

12.1XU
Vulnerable; migrate to 12.3(18) or later

12.1XV
Vulnerable; migrate to 12.3(18) or later

12.1XW
Not vulnerable

12.1XX
Not vulnerable

12.1XY
Not vulnerable

12.1XZ
Not vulnerable

12.1YA
Not vulnerable

12.1YB
Vulnerable; migrate to 12.3(18) or later

12.1YC
Vulnerable; migrate to 12.3(18) or later

12.1YD
Vulnerable; migrate to 12.3(18) or later

12.1YE
Not vulnerable

12.1YF
Not vulnerable

12.1YH
Not vulnerable

12.1YI
Not vulnerable

12.1YJ
Not vulnerable

Affected 12.2-Based Release
Rebuild
Maintenance

12.2
Not vulnerable

12.2B
Vulnerable; migrate to 12.3(4)T13 or later

12.2BC
Vulnerable; migrate to 12.3(17b)BC3 or later

12.2BW
Vulnerable; migrate to 12.3(18) or later

12.2BY
Vulnerable; migrate to 12.3(4)T13 or later

12.2BZ
Not vulnerable

12.2CX
Vulnerable; migrate to 12.3(17b)BC3 or later

12.2CY
Not vulnerable

12.2CZ
Not vulnerable

12.2DA
Not vulnerable

12.2DD
Vulnerable; migrate to 12.3(4)T13 or later

12.2DX
Vulnerable; migrate to 12.3(4)T13 or later

12.2EU
Vulnerable; migrate to 12.2(25)EWA6 or later

12.2EW
Vulnerable; migrate to 12.2(25)EWA6 or later

12.2EWA
12.2(25)EWA6

12.2EX
Not vulnerable

12.2EY
Not vulnerable

12.2EZ
Vulnerable; migrate to 12.2(25)SEE1 or later

12.2FX
Not vulnerable

12.2FY
Not vulnerable

12.2FZ
Not vulnerable

12.2IXA
Vulnerable; migrate to 12.2(18)IXB or later

12.2IXB
All 12.2IXB releases are fixed

12.2IXC
All 12.2IXC releases are fixed

12.2JA
Not vulnerable

12.2JK
Not vulnerable

12.2MB
Not vulnerable

12.2MC
12.2(15)MC2h

12.2S
12.2(25)S11
12.2(30)S

12.2SB
12.2(28)SB2
12.2(31)SB

12.2SBC
12.2(27)SBC4

12.2SEA
Vulnerable; migrate to 12.2(25)SEE1 or later

12.2SEB
Vulnerable; migrate to 12.2(25)SEE1 or later

12.2SEC
Vulnerable; migrate to 12.2(25)SEE1 or later

12.2SED
Vulnerable; migrate to 12.2(25)SEE1 or later

12.2SEE
12.2(25)SEE1

12.2SEF
12.2(25)SEF1

12.2SEG
All 12.2SEG releases are fixed

12.2SG
12.2(25)SG1
12.2(31)SG

12.2SGA
All 12.2SGA releases are fixed

12.2SO
Not vulnerable

12.2SRA
All 12.2SRA releases are fixed

12.2SRB
All 12.2SRB releases are fixed

12.2SU
Vulnerable; migrate to 12.3(14)T7 or later

12.2SV
12.2(25)SV3
12.2(26)SV

12.2SW
12.2(25)SW7

12.2SX
Vulnerable; migrate to 12.2(18)SXD7a or later

12.2SXA
Vulnerable; migrate to 12.2(18)SXD7a or later

12.2SXB
Vulnerable; migrate to 12.2(18)SXD7a or later

12.2SXD
12.2(18)SXD7a

12.2SXE
12.2(18)SXE6

12.2SXF
12.2(18)SXF5

12.2SY
Vulnerable; migrate to 12.2(18)SXD7a or later

12.2SZ
Vulnerable; migrate to 12.2(25)S11 or later

12.2T
Vulnerable; migrate to 12.3(18) or later

12.2TPC
Vulnerable; contact TAC

12.2XA
Vulnerable; migrate to 12.3(18) or later

12.2XB
Vulnerable; migrate to 12.3(18) or later

12.2XC
Vulnerable; migrate to 12.3(4)T13 or later

12.2XD
Vulnerable; migrate to 12.3(18) or later

12.2XE
Not vulnerable

12.2XF
Vulnerable; migrate to 12.3(17b)BC3 or later

12.2XG
Vulnerable; migrate to 12.3(18) or later

12.2XH
Vulnerable; migrate to 12.3(18) or later

12.2XI
Vulnerable; migrate to 12.3(18) or later

12.2XJ
Vulnerable; migrate to 12.3(18) or later

12.2XK
Vulnerable; migrate to 12.3(18) or later

12.2XL
Vulnerable; migrate to 12.3(18) or later

12.2XM
Vulnerable; migrate to 12.3(18) or later

12.2XN
12.2(31)XN

12.2XQ
Vulnerable; migrate to 12.3(18) or later

12.2XR
Not vulnerable

12.2XS
Vulnerable; migrate to 12.3(18) or later

12.2XT
Vulnerable; migrate to 12.3(18) or later

12.2XU
Vulnerable; migrate to 12.3(18) or later

12.2XV
Vulnerable; migrate to 12.3(18) or later

12.2XW
Vulnerable; migrate to 12.3(18) or later

12.2YA
Vulnerable; migrate to 12.3(18) or later

12.2YB
Vulnerable; migrate to 12.3(18) or later

12.2YC
Not vulnerable

12.2YD
Vulnerable; migrate to 12.3(11)T10 or later

12.2YE
Vulnerable; migrate to 12.2(25)S11 or later

12.2YF
Vulnerable; migrate to 12.3(18) or later

12.2YG
Not vulnerable

12.2YH
Vulnerable; migrate to 12.3(18) or later

12.2YJ
Vulnerable; migrate to 12.3(18) or later

12.2YK
Not vulnerable

12.2YL
Vulnerable; migrate to 12.3(4)T13 or later

12.2YM
Vulnerable; migrate to 12.3(4)T13 or later

12.2YN
Vulnerable; migrate to 12.3(4)T13 or later

12.2YO
Not vulnerable

12.2YP
Not vulnerable

12.2YQ
Vulnerable; migrate to 12.3(4)T13 or later

12.2YR
Vulnerable; migrate to 12.3(4)T13 or later

12.2YT
Vulnerable; migrate to 12.3(18) or later

12.2YU
Vulnerable; migrate to 12.3(4)T13 or later

12.2YV
Vulnerable; migrate to 12.3(4)T13 or later

12.2YW
Vulnerable; migrate to 12.3(4)T13 or later

12.2YX
Vulnerable; migrate to 12.3(14)T7 or later

12.2YY
Vulnerable; migrate to 12.3(4)T13 or later

12.2YZ
Vulnerable; migrate to 12.2(25)S11 or later

12.2ZA
Vulnerable; migrate to 12.2(18)SXD7a or later

12.2ZB
Vulnerable; migrate to 12.3(4)T13 or later

12.2ZC
Not vulnerable

12.2ZD
Vulnerable; contact TAC

12.2ZE
Vulnerable; migrate to 12.3(18) or later

12.2ZF
Vulnerable; migrate to 12.3(4)T13 or later

12.2ZG
Not vulnerable

12.2ZH
Vulnerable; contact TAC

12.2ZJ
Vulnerable; migrate to 12.3(4)T13 or later

12.2ZL
Vulnerable; contact TAC

12.2ZN
Vulnerable; migrate to 12.3(4)T13 or later

12.2ZP
Not vulnerable

Affected 12.3-Based Release
Rebuild
Maintenance

12.3
12.3(17b)
12.3(18)

12.3B
Vulnerable; migrate to 12.3(11)T10 or later

12.3BC
12.3(17b)BC3

12.3BW
Vulnerable; migrate to 12.3(11)T10 or later

12.3JA
Not vulnerable

12.3JEA
All 12.3JEA releases are fixed

12.3JEB
All 12.3JEA releases are fixed

12.3JK
Not vulnerable

12.3JX
Not vulnerable

12.3T
12.3(4)T13

12.3(11)T10

12.3(14)T7

12.3TPC
Not vulnerable

12.3XA
Vulnerable; contact TAC

12.3XB
Vulnerable; migrate to 12.3(11)T10 or later

12.3XC
Vulnerable; contact TAC

12.3XD
Vulnerable; migrate to 12.3(11)T10 or later

12.3XE
Vulnerable; contact TAC

12.3XF
Vulnerable; migrate to 12.3(11)T10 or later

12.3XG
Vulnerable; contact TAC

12.3XH
Vulnerable; migrate to 12.3(11)T10 or later

12.3XI
12.3(7)XI8a
12.3(7)XI9

12.3XJ
Vulnerable; migrate to 12.3(14)YX2 or later

12.3XK
Vulnerable; migrate to 12.3(14)T7 or later

12.3XQ
Vulnerable; migrate to 12.4(8) or later

12.3XR
Vulnerable; contact TAC

12.3XS
Vulnerable; migrate to 12.4(8) or later

12.3XU
Vulnerable; migrate to 12.4(2)T4 or later

12.3XW
Vulnerable; migrate to 12.3(14)YX2 or later

12.3XX
Vulnerable; migrate to 12.4(8) or later

12.3XY
Not vulnerable

12.3YA
Vulnerable; contact TAC

12.3YD
Vulnerable; migrate to 12.4(2)T4 or later

12.3YF
Vulnerable; migrate to 12.3(14)YX2 or later

12.3YG
Vulnerable; migrate to 12.4(2)T4 or later

12.3YH
Vulnerable; migrate to 12.4(2)T4 or later

12.3YI
Vulnerable; migrate to 12.4(2)T4 or later

12.3YJ
Vulnerable; migrate to 12.4(6)T1 or later

12.3YK
Vulnerable; migrate to 12.4(4)T2 or later

12.3YM
12.3(14)YM8

12.3YQ
Vulnerable; migrate to 12.4(6)T1 or later

12.3YS
Vulnerable; migrate to 12.4(4)T2 or later

12.3YT
Vulnerable; migrate to 12.4(4)T2 or later

12.3YU
Vulnerable; migrate to 12.4(2)XB2 or later

12.3YX
12.3(14)YX2

12.3YZ
12.3(11)YZ1

Affected 12.4-Based Release
Rebuild
Maintenance

12.4
12.4(3d)

12.4(5b)

12.4(7a)
12.4(8)

12.4MR
Not vulnerable

12.4SW
All 12.4SW releases are fixed

12.4T
12.4(2)T4

12.4(4)T2

12.4(6)T1
12.4(9)T

12.4XA
Vulnerable; migrate to 12.4(6)T1 or later

12.4XB
12.4(2)XB2

12.4XC
12.4(4)XC5

12.4XD
12.4(4)XD2

12.4XE
All 12.4XE releases are fixed

12.4XG
All 12.4XG releases are fixed

12.4XJ
All 12.4XJ releases are fixed

12.4XP
All 12.4XP releases are fixed

12.4XT
All 12.4XT releases are fixed

Workarounds
The workaround consists of filtering packets that contain Type 0 Routing header(s). Special attention must be paid not to filter packets with Type 2 Routing headers as that would break Mobile IPv6 deployment. Depending on what Cisco IOS software release is used and if Mobile IPv6 is deployed or not we have the following workarounds. As any packet type can be used to trigger this vulnerability the care must be taken when implementing a workaround to account for a spoofed packet.

Additional mitigations that can be deployed on Cisco devices within the network are available in the Cisco Applied Intelligence companion document for this advisory: http://www.cisco.com/warp/public/707/cisco-air-20070124-IOS-IPv6.shtml

Mobile IPv6 is not deployed
For IOS releases before 12.3(4)T the workaround is to use ACLs to filter all packets that contain Routing headers. This method can not distinguish between Type 0 and Type 2 Routing headers so it is not suitable if Mobile IPv6 is deployed.

The following example shows how to configure such ACLs.

Router(config)#ipv6 access-list deny-sourcerouted
Router(config-ipv6-acl)#deny ipv6 any routing
Router(config-ipv6-acl)#deny ipv6 any routing
Router(config-ipv6-acl)#permit ipv6 any any
Router(config-ipv6-acl)#exit
Router(config)#interface Ethernet0
Router(config-if)#ipv6 traffic-filter deny-sourcerouted in
In this example is an IPv6 address. One example of such address is 3ffe:ffff::/64. The ACL must be applied to all interfaces and all IPv6 addresses that are configured. If an interface has more than one IPv6 address configured then all addresses must be covered by the ACLs. This also includes all loopback and "link local" addresses for each interface.

The alternative of enumerating all IPv6 addresses is to use statement deny ipv6 any any routing. While that simplifies the resulting ACL it will also filter all transit IPv6 traffic with Routing headers 0 and 2. The example where all configured IPv6 addresses are enumerated will not affect transit traffic. This comment is applicable to all other examples in this Advisory.

Starting from the IOS release 12.2(15)T a new command ipv6 source-route was introduced. If applied, it will block any IPv6 packet with any IPv6 routing headers (both types 0 and 2). The configuration is given in the following example.

Router(config)#no ipv6 source-route
This is a global command and it applies to all interfaces. The command is applicable on all defined IPv6 addresses, including the link local and loopback address, and on all interfaces.

Mobile IPv6 is deployed
There is no workaround if you are running a Cisco IOS release prior to 12.4(2)T. In IOS 12.4(2)T a new keyword routing-type is added to IPv6 ACLs. It can be used to selectively permit or deny specific routing types.

Router(config)#ipv6 access-list deny-sourcerouted
Router(config-ipv6-acl)#deny ipv6 any routing-type 0
Router(config-ipv6-acl)#permit ipv6 any any
Router(config)#interface Ethernet0
Router(config-if)#ipv6 source-route
Router(config-if)#ipv6 traffic-filter deny-sourcerouted in
The filter must be applied to all interfaces that have IPv6 configured.

Obtaining Fixed Software
Cisco will make free software available to address this vulnerability for affected customers. This advisory will be updated as fixed software becomes available. Prior to deploying software, customers should consult their maintenance provider or check the software for feature set compatibility and known issues specific to their environment.

Customers may only install and expect support for the feature sets they have purchased. By installing, downloading, accessing or otherwise using such software upgrades, customers agree to be bound by the terms of Cisco's software license terms found at http://www.cisco.com/public/sw-license-agreement.html, or as otherwise set forth at Cisco.com Downloads at http://www.cisco.com/public/sw-center/sw-usingswc.shtml.

Do not contact either "psirt@cisco.com" or "security-alert@cisco.com" for software upgrades.

Customers with Service Contracts
Customers with contracts should obtain upgraded software through their regular update channels. For most customers, this means that upgrades should be obtained through the Software Center on Cisco's worldwide website at http://www.cisco.com.

Customers using Third Party Support Organizations
Customers whose Cisco products are provided or maintained through prior or existing agreement with third-party support organizations such as Cisco Partners, authorized resellers, or service providers should contact that support organization for guidance and assistance with the appropriate course of action in regards to this advisory.

The effectiveness of any workaround or fix is dependent on specific customer situations such as product mix, network topology, traffic behavior, and organizational mission. Due to the variety of affected products and releases, customers should consult with their service provider or support organization to ensure any applied workaround or fix is the most appropriate for use in the intended network before it is deployed.

Customers without Service Contracts
Customers who purchase direct from Cisco but who do not hold a Cisco service contract and customers who purchase through third-party vendors but are unsuccessful at obtaining fixed software through their point of sale should get their upgrades by contacting the Cisco Technical Assistance Center (TAC). TAC contacts are as follows.

+1 800 553 2447 (toll free from within North America)

+1 408 526 7209 (toll call from anywhere in the world)

e-mail: tac@cisco.com

Have your product serial number available and give the URL of this notice as evidence of your entitlement to a free upgrade. Free upgrades for non-contract customers must be requested through the TAC.

Refer to http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml for additional TAC contact information, including special localized telephone numbers and instructions and e-mail addresses for use in various languages.

Exploitation and Public Announcements
The Cisco PSIRT is not aware of any public announcements or malicious use of the vulnerability described in this advisory.

This vulnerability was initially reported to Cisco by Arnaud Ebalard from EADS Corporate Research Center. An additional vector to trigger it was discovered internally while fixing the vulnerability.

Status of this Notice:FINAL
THIS DOCUMENT IS PROVIDED ON AN "AS IS" BASIS AND DOES NOT IMPLY ANY KIND OF GUARANTEE OR WARRANTY, INCLUDING THE WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR USE. YOUR USE OF THE INFORMATION ON THE DOCUMENT OR MATERIALS LINKED FROM THE DOCUMENT IS AT YOUR OWN RISK. CISCO RESERVES THE RIGHT TO CHANGE OR UPDATE THIS DOCUMENT AT ANY TIME.

A stand-alone copy or Paraphrase of the text of this document that omits the distribution URL in the following section is an uncontrolled copy, and may lack important information or contain factual errors.

Distribution
This advisory is posted on Cisco's worldwide website at: http://www.cisco.com/warp/public/707/cisco-sa-20070124-IOS-IPv6.shtml

In addition to worldwide web posting, a text version of this notice is clear-signed with the Cisco PSIRT PGP key and is posted to the following e-mail and Usenet news recipients.

cust-security-announce@cisco.com

first-teams@first.org

bugtraq@securityfocus.com

vulnwatch@vulnwatch.org

cisco@spot.colorado.edu

cisco@spot.colorado.edu

cisco-nsp@puck.nether.net

full-disclosure@lists.grok.org.uk

comp.dcom.sys.cisco@newsgate.cisco.com

Cisco Security Advisory: Crafted IP Option Vulnerability

Document ID: 81734
Advisory ID: cisco-sa-20070124-crafted-ip-option
http://www.cisco.com/warp/public/707/cisco-sa-20070124-crafted-ip-option.shtml
Revision 1.1
Last Updated 2007 January 25 1600 UTC (GMT)
For Public Release 2007 January 24 1600 UTC (GMT)

--------------------------------------------------------------------------------

Please provide your feedback on this document.

--------------------------------------------------------------------------------

Contents
Summary
Affected Products
Details
Vulnerability Scoring Details
Impact
Software Version and Fixes
Workarounds
Obtaining Fixed Software
Exploitation and Public Announcements
Status of this Notice: FINAL
Distribution
Revision History
Cisco Security Procedures

--------------------------------------------------------------------------------

Summary
Cisco routers and switches running Cisco IOS® or Cisco IOS XR software may be vulnerable to a remotely exploitable crafted IP option Denial of Service (DoS) attack. Exploitation of the vulnerability may potentially allow for arbitrary code execution. The vulnerability may be exploited after processing an Internet Control Message Protocol (ICMP) packet, Protocol Independent Multicast version 2 (PIMv2) packet, Pragmatic General Multicast (PGM) packet, or URL Rendezvous Directory (URD) packet containing a specific crafted IP option in the packet's IP header. No other IP protocols are affected by this issue.

Cisco has made free software available to address this vulnerability for affected customers.

There are workarounds available to mitigate the effects of the vulnerability.

This vulnerability was discovered during internal testing.

This advisory is available at http://www.cisco.com/warp/public/707/cisco-sa-20070124-crafted-ip-option.shtml.

Affected Products
Vulnerable Products
This issue affects all Cisco devices running Cisco IOS or Cisco IOS XR software and configured to process Internet Protocol version 4 (IPv4) packets. Devices which run only Internet Protocol version 6 (IPv6) are not affected.

This vulnerability is present in all unfixed versions of Cisco IOS software, including versions 9.x, 10.x, 11.x and 12.x.

This vulnerability is present in all unfixed versions of Cisco IOS XR software, including versions 2.0.X, 3.0.X, and 3.2.X.

All versions of Cisco IOS or Cisco IOS XR prior to the versions listed in the Fixed Software table below may be susceptible to this vulnerability.

To determine the software running on a Cisco product, log in to the device and issue the show version command to display the system banner. Cisco IOS software will identify itself as "Internetwork Operating System Software" or simply "IOS". On the next line of output, the image name will be displayed between parentheses, followed by "Version" and the IOS release name. Cisco IOS XR software will identify itself as "Cisco IOS XR Software" followed by "Version" and the version number. Other Cisco devices will not have the show version command or will give different output.

The following example identifies a Cisco product running Cisco IOS release 12.2(14)S16 with an installed image name of C7200-IS-M:

Cisco Internetwork Operating System Software
IOS (tm) 7200 Software (C7200-IS-M), Version 12.2(14)S16, RELEASE SOFTWARE (fc1)The release train label is "12.2".

The next example shows a product running IOS release 12.3(7)T12 with an image name of C7200-IK9S-M:

Cisco IOS Software, 7200 Software (C7200-IK9S-M), Version 12.3(7)T12, RELEASE SOFTWARE (fc1)Additional information about Cisco IOS Banners is available at http://www.cisco.com/en/US/products/sw/iosswrel/ps1828/products_white_paper09186a008018305e.shtml#3.

Cisco IOS XR Software is a member of the Cisco IOS software family that uses a microkernel-based distributed operating system infrastructure. Cisco IOS XR runs only on Cisco Carrier Routing System 1 (CRS-1) and Cisco XR 12000 series routers.

Additional information about Cisco IOS XR is available at http://www.cisco.com/en/US/products/ps5845/index.html

The following example shows partial output from the show version command which identifies a Cisco product running Cisco IOS XR release 3.3.0:

RP/0/RP0/CPU0:router#show version
Cisco IOS XR Software, Version 3.3.0
Copyright (c) 2006 by cisco Systems, Inc.
ROM: System Bootstrap, Version 1.32(20050525:193559) [CRS-1 ROMMON]Products Confirmed Not Vulnerable
Cisco devices that do not run Cisco IOS or Cisco IOS XR software are not affected. CatOS software is not affected by this issue.

No other Cisco products are currently known to be affected by this vulnerability.

Details
This vulnerability may be exploited when an affected device processes a packet that meets all three of the following conditions:

1. The packet contains a specific crafted IP option.

AND

2. The packet is one of the following protocols:

ICMP - Echo (Type 8) - 'ping'

ICMP - Timestamp (Type 13)

ICMP - Information Request (Type 15)

ICMP - Address Mask Request (Type 17)

PIMv2 - IP protocol 103

PGM - IP protocol 113

URD - TCP Port 465

AND

3. The packet is sent to a physical or virtual IPv4 address configured on the affected device.

No other ICMP message types are affected by this issue.

No other IP protocols are affected by this issue.

No other TCP services are affected by this issue.

The packet can be sent from a local network or from a remote network.

The source IP address of the packet can be spoofed or non-spoofed.

Packets which transit the device (packets not sent to one of the device's IP addresses) do not trigger the vulnerability and the device is not affected.

This vulnerability is documented in these Bug IDs:

Cisco Bug ID CSCec71950 ( registered customers only) for Cisco IOS

Cisco Bug ID CSCeh52410 ( registered customers only) for Cisco IOS XR

Cisco IOS
A crafted packet addressed directly to a vulnerable device running Cisco IOS software may result in the device reloading or may allow execution of arbitrary code.

Cisco IOS XR
A crafted packet addressed directly to a vulnerable device running Cisco IOS XR software may result in the ipv4_io process restarting or may allow execution of arbitrary code. CRS-1 Nodes that run the ipv4_io process include Route Processors (RP), Distributed Route Processors (DRP), Modular Services Cards (MSC), and XR 12000 Line Cards. While the ipv4_io process is restarting, all ICMP traffic destined for the device itself and exception punts will be dropped. Examples of exception punts include packets having IP header information that requires further processing such as IP options, Time-to-Live equal to 0 or 1, and layer-2 keepalives. CLNS traffic to the Node or Line Card is not affected. If the ipv4_io process is restarted several times consecutively, the CRS-1 Node or XR 12000 Line Card may reload, causing a Denial of Service (DoS) condition for the transit traffic switched on that Node or Line card.

Devices Configured for ICMP Message Types
ICMP Type 8
By default, devices running all Cisco IOS and Cisco IOS XR versions will process ICMP echo-request (Type 8) packets. This behavior cannot be modified.

ICMP Type 13
By default, devices running all Cisco IOS versions will process ICMP timestamp (Type 13) packets. This behavior cannot be modified.

By default, devices running all Cisco IOS XR versions will NOT process ICMP timestamp (Type 13) packets. This behavior cannot be modified.

ICMP Type 15
With the introduction of CSCdz50424, by default routers will NOT process ICMP information request (Type 15) packets. Releases of Cisco IOS that contain CSCdz50424 include 12.3, 12.3T, 12.4, 12.4T, later 12.0S and later 12.2S. See CSCdz50424 ( registered customers only) for complete release information.

A router running a Cisco IOS release containing CSCdz50424 that has been modified to process ICMP information request packets will have the interface configuration statement ip information-reply, which can be seen by issuing the command show running-config as shown in the following examples:

router#show running-config | include information-reply
ip information-replyor

router#show running-config

interface FastEthernet0/0
ip address 192.0.2.1 255.255.255.0
ip information-replyBy default, devices running all other Cisco IOS versions will process ICMP information request (Type 15) packets. This behavior cannot be modified. Since this is the default behavior, ip information-reply will not be visible in the device's configuration.

By default, devices running all Cisco IOS XR versions will NOT process ICMP information request (Type 15) packets. This behavior cannot be modified.

ICMP Type 17
Beginning in Cisco IOS version 10.0, by default devices will NOT process ICMP address mask request (Type 17) packets. A router that has been modified to process ICMP address mask request packets will have the interface configuration statement ip mask-reply, which can be seen by issuing the command show running-config as shown in the following examples:

router#show running-config | include mask-reply
ip mask-replyor

router#show running-config

interface FastEthernet0/0
ip address 192.0.2.1 255.255.255.0
ip mask-replyBy default, devices running all Cisco IOS XR versions will NOT process ICMP address mask request (Type 17) packets. A router that has been modified to process ICMP address mask request packets will have the interface configuration statement ipv4 mask-reply, which can be seen by issuing the command show running-config as shown in the following examples:

RP/0/RP0/CPU0:router#show running-config | include mask-reply
Building configuration...
ipv4 mask-replyor

RP/0/RP0/CPU0:router#show running-config
interface POS0/1/3/0
ipv4 address 192.0.2.1 255.255.255.252
ipv4 mask-replyDevices Configured for Protocol Independent Multicast Version 2 (PIMv2)
Cisco IOS
A router running Cisco IOS that is configured to process PIMv2 packets will have an interface configuration statement that begins with ip pim, which can be seen by issuing the command show running-config as shown in the following examples:

router#show running-config | include ip pim
ip pim sparse-modeor

router#show running-config

interface FastEthernet0/0
ip address 192.0.2.1 255.255.255.0
ip pim sparse-dense-modeThe command show ip pim interface can also be used to determine if a router is configured to process PIMv2 packets, as shown in the following example:

router#show ip pim interface
Address Interface Ver/ Nbr Query DR DR
Mode Count Intvl Prior
192.0.2.1 FastEthernet0/0 v1/S 0 30 1 0.0.0.0
192.168.1.1 FastEthernet1/0 v2/SD 0 30 1 0.0.0.0Interfaces running PIMv2 will show "v2/" under the Ver/Mode column. Interfaces without PIM configured will not be shown in the command output.

PIMv2 is the default PIM version. Routers configured to process only PIMv1 messages are not vulnerable to the PIMv2 exploit. Routers that do not have PIM configured are not vulnerable to the PIMv2 exploit. PIM is not enabled by default.

Additional information about PIM is available at http://www.cisco.com/en/US/products/sw/iosswrel/ps1835/products_configuration_guide_chapter09186a00800ca794.html.

Cisco IOS XR
The command show pim interface can be used to determine if a router running Cisco IOS XR is configured to process PIMv2 packets, as shown in the following example:

RP/0/0/CPU0:router#show pim interface
Address Interface PIM Nbr Hello DR DR
Count Intvl Prior
192.168.1.1 Loopback0 on 1 30 1 this system
192.168.2.1 MgmtEth0/0/CPU0/0 off 0 30 1 not elected
192.168.3.1 Loopback1 on 1 30 1 this system
192.168.4.1 Loopback3 on 1 30 1 this system
192.168.5.1 POS0/4/0/0 on 1 30 1 this system
192.0.2.1 POS0/4/0/1 on 1 30 1 this systemInterfaces running PIMv2 will show on under the PIM column. Interfaces without PIM configured will show "off" under the PIM column.

Cisco IOS XR does not support PIMv1. PIM is not enabled by default on Cisco IOS XR.

Additional information about PIM on Cisco IOS XR is available at http://www.cisco.com/en/US/products/ps5845/products_configuration_guide_chapter09186a008069a8a2.html.

Devices Configured for Pragmatic General Multicast (PGM)
A router that is configured to process PGM packets will have the interface configuration statement ip pgm router, which can be seen by issuing the command show running-config as shown in the following examples:

router#show running-config | include ip pgm
ip pgm routeror

router#show running-config

interface FastEthernet1/0
ip address 192.0.2.1 255.255.255.0
ip pim sparse-dense-mode
ip pgm routeror

router#show running-config

interface FastEthernet1/0
ip address 192.0.2.1 255.255.255.0
ip pgm routerRouters that do not have PGM configured are not vulnerable to the PGM exploit. PGM is not enabled by default.

Additional information about PGM is available at http://www.cisco.com/en/US/products/sw/iosswrel/ps1835/products_configuration_guide_chapter09186a00800ca798.html.

Cisco IOS XR does not support PGM and is not affected by PGM packets that exploit this vulnerability.

Devices Configured for URL Rendezvous Directory (URD)
A router that is configured to process URD packets will have the interface configuration statement ip urd or ip urd proxy, which can be seen by issuing the command show running-config as shown in the following examples:

router#show running-config | include ip urd
ip urdor

router#show running-config | include ip urd
ip urd proxyor

router#show running-config

interface FastEthernet1/0
ip address 192.0.2.1 255.255.255.0
ip pim sparse-mode
ip urdor

router#show running-config

interface FastEthernet1/0
ip address 192.0.2.1 255.255.255.0
ip pim sparse-dense-mode
ip urd proxyor

router#show running-config

interface FastEthernet1/0
ip address 192.0.2.1 255.255.255.0
ip urdRouters that do not have URD configured are not vulnerable to the URD exploit. URD is not enabled by default.

Additional information about URD is available at http://www.cisco.com/en/US/products/sw/iosswrel/ps1835/products_configuration_guide_chapter09186a00800ca795.html.

Cisco IOS XR does not support URD and is not affected by URD packets that exploit this vulnerability.

Vulnerability Scoring Details
Cisco is providing scores for the vulnerabilities in this advisory based on the Common Vulnerability Scoring System (CVSS). Cisco will provide a base and temporal score. Customers can then compute environmental scores to assist in determining the impact of the vulnerability in individual networks.

Cisco PSIRT will set the bias in all cases to normal. Customers are encouraged to apply the bias parameter when determining the environmental impact of a particular vulnerability.

CVSS is a standards-based scoring method that conveys vulnerability severity and helps determine urgency and priority of response.

Cisco has provided an FAQ to answer additional questions regarding CVSS at http://www.cisco.com/web/about/security/intelligence/cvss-qandas.html.

Cisco has also provided a CVSS calculator to help compute the environmental impact for individual networks at http://intellishield.cisco.com/security/alertmanager/cvss.

CSCec71950 ( registered customers only) - Crafted IP Option may cause DoS or code execution

Calculate the environmental score of CSCec71950

CVSS Base Score - 10

Access Vector
Access Complexity
Authentication
Confidentiality Impact
Integrity Impact
Availability Impact
Impact Bias

Remote
Low
Not Required
Complete
Complete
Complete
Normal

CVSS Temporal Score - 8.3

Exploitability
Remediation Level
Report Confidence

Functional
Official Fix
Confirmed

CSCeh52410 ( registered customers only) - Crafted IP Option may cause ipv4-io DoS or code execution

Calculate the environmental score of CSCeh52410

CVSS Base Score - 10

Access Vector
Access Complexity
Authentication
Confidentiality Impact
Integrity Impact
Availability Impact
Impact Bias

Remote
Low
Not Required
Complete
Complete
Complete
Normal

CVSS Temporal Score - 8.3

Exploitability
Remediation Level
Report Confidence

Functional
Official Fix
Confirmed

Impact
Cisco IOS
Successful exploitation of the vulnerability on Cisco IOS may result in a reload of the device or execution of arbitrary code. Repeated exploitation could result in a sustained DoS attack.

Cisco IOS XR
Successful exploitation of the vulnerability on Cisco IOS XR may result in the ipv4_io process restarting or execution of arbitrary code. Repeated exploitation could result in a CRS-1 Node or XR 12000 Line Card reload and sustained DoS attack.

Software Version and Fixes
When considering software upgrades, also consult http://www.cisco.com/go/psirt and any subsequent advisories to determine exposure and a complete upgrade solution.

In all cases, customers should exercise caution to be certain the devices to be upgraded contain sufficient memory and that current hardware and software configurations will continue to be supported properly by the new release. If the information is not clear, contact the Cisco Technical Assistance Center ("TAC") or your contracted maintenance provider for assistance.

Each row of the Cisco IOS software table (below) describes a release train and the platforms or products for which it is intended. If a given release train is vulnerable, then the earliest possible releases that contain the fix (the "First Fixed Release") and the anticipated date of availability for each are listed in the "Rebuild" and "Maintenance" columns. A device running a release in the given train that is earlier than the release in a specific column (less than the First Fixed Release) is known to be vulnerable. The release should be upgraded at least to the indicated release or a later version (greater than or equal to the First Fixed Release label).

For more information on the terms "Rebuild" and "Maintenance," consult the following URL: http://www.cisco.com/en/US/products/sw/iosswrel/ps1828/products_white_paper09186a008018305e.shtml.

Note: There are three IOS security advisories and one field notice being published on January 24, 2007. Each advisory lists only the releases which fix the issue described in the advisory. A combined software table is available at http://www.cisco.com/warp/public/707/cisco-sa-20070124-bundle.shtml and can be used to choose a software release which fixes all security vulnerabilities published as of January 24, 2007. Links for the advisories and field notice are listed here.

http://www.cisco.com/warp/public/707/cisco-sa-20070124-IOS-IPv6.shtml

http://www.cisco.com/warp/public/707/cisco-sa-20070124-crafted-tcp.shtml

http://www.cisco.com/warp/public/707/cisco-sa-20070124-crafted-ip-option.shtml

http://www.cisco.com/warp/public/770/fn62613.shtml

Requests for software rebuilds to include the change for Daylight Savings Time (DST) that will be implemented in March 2007 should be directed through the Technical Assistance Center (TAC), and this advisory should be used as reference.

Major Release
Availability of Repaired Releases

Affected 12.0-Based Release
Rebuild
Maintenance

12.0
Vulnerable; migrate to 12.2(37)or later

12.0DA
Vulnerable; migrate to 12.2(10)DA5 or later

12.0DB
Vulnerable; migrate to 12.3(4)T13 or later

12.0DC
Vulnerable; migrate to 12.3(4)T13 or later

12.0S
12.0(27)S3
12.0(28)S

12.0SC
Vulnerable; migrate to 12.3(9a)BC or later

12.0SL
Vulnerable; migrate to 12.0(28)S or later

12.0SP
Vulnerable; migrate to 12.0(28)S or later

12.0ST
Vulnerable; migrate to 12.0(28)S or later

12.0SX
12.0(25)SX11
12.0(30)SX

12.0SY
12.0(27)SY

12.0SZ
12.0(30)SZ

12.0T
Vulnerable; migrate to 12.2(37)or later

12.0W
12.0(28)W5(32c); available 31-Jan-07

12.0WC
12.0(5)WC15

12.0WT
Vulnerable; contact TAC

12.0XA
Vulnerable; migrate to 12.2(37)or later

12.0XB
Vulnerable; migrate to 12.2(37)or later

12.0XC
Vulnerable; migrate to 12.2(37)or later

12.0XD
Vulnerable; migrate to 12.2(37)or later

12.0XE
Vulnerable; migrate to 12.1(23)E or later

12.0XF
Not vulnerable

12.0XG
Vulnerable; migrate to 12.2(37)or later

12.0XH
Vulnerable; migrate to 12.2(37)or later

12.0XI
Vulnerable; migrate to 12.2(37)or later

12.0XJ
Vulnerable; migrate to 12.2(37)or later

12.0XK
Vulnerable; migrate to 12.2(37)or later

12.0XL
Vulnerable; migrate to 12.2(37)or later

12.0XM
Vulnerable; migrate to 12.2(37)or later

12.0XN
Vulnerable; migrate to 12.2(37)or later

12.0XQ
Vulnerable; migrate to 12.2(37)or later

12.0XR
Vulnerable; migrate to 12.2(37)or later

12.0XS
Vulnerable; migrate to 12.1(23)E or later

12.0XV
Vulnerable; migrate to 12.2(37)or later

12.0XW
Vulnerable; migrate to 12.0(5)WC15 or later

Affected 12.1-Based Release
Rebuild
Maintenance

12.1
Vulnerable; migrate to 12.2(37)or later

12.1AA
Vulnerable; migrate to 12.2(37)or later

12.1AX
Vulnerable; for c3750-ME, migrate to 12.2(25)EY or later. For c2970 and 3750, migrate to 12.2(25)SE or later.

12.1AY
Vulnerable; migrate to 12.1(22)EA8

12.1AZ
Vulnerable; migrate to 12.1(22)EA8

12.1CX
Vulnerable; migrate to 12.2(37)or later

12.1DA
Vulnerable; migrate to 12.2(10)DA5 or later

12.1DB
Vulnerable; migrate to 12.3(4)T13 or later

12.1DC
Vulnerable; migrate to 12.3(4)T13 or later

12.1E
12.1(23)E

12.1EA
12.1(22)EA8

12.1EB
12.1(23)EB

12.1EC
Vulnerable; migrate to 12.3(9a)BC or later

12.1EO
12.1(19)EO6, available 31-Jan-07

12.1(20)EO3

12.1EU
Vulnerable; migrate to 12.2(25)EWA or later

12.1EV
Vulnerable; migrate to 12.2(26)SV1 or later

12.1EW
Vulnerable; migrate to 12.2(18)EW3 or later

12.1EX
Vulnerable; migrate to 12.1(23)E or later

12.1EY
Vulnerable; migrate to 12.1(23)E or later

12.1EZ
Vulnerable; migrate to 12.1(23)E or later

12.1T
Vulnerable; migrate to 12.2(37)or later

12.1XA
Vulnerable; migrate to 12.2(37)or later

12.1XB
Vulnerable; migrate to 12.2(37)or later

12.1XC
Vulnerable; migrate to 12.2(37)or later

12.1XD
Vulnerable; migrate to 12.2(37)or later

12.1XE
Vulnerable; migrate to 12.1(23)E or later

12.1XF
Vulnerable; migrate to 12.3(8) or later

12.1XG
Vulnerable; migrate to 12.3(8) or later

12.1XH
Vulnerable; migrate to 12.2(37)or later

12.1XI
Vulnerable; migrate to 12.2(37)or later

12.1XJ
Vulnerable; migrate to 12.3(8) or later

12.1XL
Vulnerable; migrate to 12.3(8) or later

12.1XM
Vulnerable; migrate to 12.3(8) or later

12.1XP
Vulnerable; migrate to 12.3(8) or later

12.1XQ
Vulnerable; migrate to 12.3(8) or later

12.1XR
Vulnerable; migrate to 12.3(8) or later

12.1XS
Vulnerable; migrate to 12.2(37)or later

12.1XT
Vulnerable; migrate to 12.3(8) or later

12.1XU
Vulnerable; migrate to 12.3(8) or later

12.1XV
Vulnerable; migrate to 12.3(8) or later

12.1XW
Vulnerable; migrate to 12.2(37)or later

12.1XX
Vulnerable; migrate to 12.2(37)or later

12.1XY
Vulnerable; migrate to 12.2(37)or later

12.1XZ
Vulnerable; migrate to 12.2(37)or later

12.1YA
Vulnerable; migrate to 12.3(8) or later

12.1YB
Vulnerable; migrate to 12.3(8) or later

12.1YC
Vulnerable; migrate to 12.3(8) or later

12.1YD
Vulnerable; migrate to 12.3(8) or later

12.1YE
Vulnerable; migrate to 12.3(8) or later

12.1YF
Vulnerable; migrate to 12.3(8) or later

12.1YH
Vulnerable; migrate to 12.3(8) or later

12.1YI
Vulnerable; migrate to 12.3(8) or later

12.1YJ
Vulnerable; migrate to 12.1(22)EA8

Affected 12.2-Based Release
Rebuild
Maintenance

12.2
12.2(34a)
12.2(37)

12.2B
Vulnerable; migrate to 12.3(4)T13 or later

12.BC
Vulnerable; migrate to 12.3(9a)BC or later

12.2BW
Vulnerable; migrate to 12.3(8) or later

12.2BY
Vulnerable; migrate to 12.3(4)T13 or later

12.2BZ
Vulnerable; migrate to 12.3(7)XI8 or later

12.2CX
Vulnerable; migrate to 12.3(9a)BC or later

12.2CY
Vulnerable; migrate to 12.3(9a)BC or later

12.2CZ
Vulnerable; contact TAC

12.2DA
12.2(10)DA5

12.2(12)DA10

12.2DD
Vulnerable; migrate to 12.3(4)T13 or later

12.2DX
Vulnerable; migrate to 12.3(4)T13 or later

12.2EU
Vulnerable; migrate to 12.2(25)EWA5 or later

12.2EW
12.2(18)EW3

12.2(20)EW4
12.2(25)EW

12.2EWA
12.2(20)EWA4
12.2(25)EWA

12.2EX
12.2(25)EX

12.2EY
All 12.2EY releases are fixed

12.2EZ
All 12.2EZ releases are fixed

12.2FX
All 12.2FX releases are fixed

12.2FY
All 12.2FY releases are fixed

12.2FZ
All 12.2FZ releases are fixed

12.2IXA
All 12.2IXA releases are fixed

12.2IXB
All 12.2IXB releases are fixed

12.2IXC
All 12.2IXC releases are fixed

12.2JA
Vulnerable; migrate to 12.3(8)JA or later

12.2JK
Vulnerable; migrate to 12.4(4)T or later

12.2MB
Vulnerable; migrate to 12.2(25)SW1 or later

12.2MC
12.2(15)MC2h

12.2S
12.2(25)S

12.2SB
12.2(28)SB

12.2SBC
All 12.2SBC releases are fixed

12.2SE
12.2(25)SE

12.2SEA
All 12.2SEA releases are fixed

12.2SEB
All 12.2SEB releases are fixed

12.2SEC
All 12.2SEC releases are fixed

12.2SED
All 12.2SED releases are fixed

12.2SEE
All 12.2SEE releases are fixed

12.2SEF
All 12.2SEF releases are fixed

12.2SEG
All 12.2SEG releases are fixed

12.2SG
All 12.2SG releases are fixed

12.2SGA
All 12.2SGA releases are fixed

12.2SO
12.2(18)SO7

12.2SRA
All 12.2SRA releases are fixed

12.2SRB
All 12.2SRB releases are fixed

12.2SU
Vulnerable; migrate to 12.3(14)T or later

12.2SV
12.2(23)SV

12.2SW
12.2(25)SW1

12.2SX
Vulnerable; migrate to 12.2(17d)SXB11a or later

12.2SXA
Vulnerable; migrate to 12.2(17d)SXB11a or later

12.2SXB
12.2(17d)SXB11a

12.2SXD
12.2(18)SXD7a

12.2SXE
All 12.2SXE releases are fixed

12.2SXF
All 12.2SXF releases are fixed

12.2SY
Vulnerable; migrate to 12.2(17d)SXB11a or later

12.2SZ
Vulnerable; migrate to 12.2(25)S or later

12.2T
Vulnerable; migrate to 12.3(8) or later

12.2TPC
Vulnerable; contact TAC

12.2XA
Vulnerable; migrate to 12.3(8) or later

12.2XB
Vulnerable; migrate to 12.3(8) or later

12.2XC
Vulnerable; migrate to 12.3(8)T or later

12.2XD
Vulnerable; migrate to 12.3(8) or later

12.2XE
Vulnerable; migrate to 12.3(8) or later

12.2XF
Vulnerable; migrate to 12.3(9a)BC or later

12.2XG
Vulnerable; migrate to 12.3(8) or later

12.2XH
Vulnerable; migrate to 12.3(8) or later

12.2XI
Vulnerable; migrate to 12.3(8) or later

12.2XJ
Vulnerable; migrate to 12.3(8) or later

12.2XK
Vulnerable; migrate to 12.3(8) or later

12.2XL
Vulnerable; migrate to 12.3(8) or later

12.2XM
Vulnerable; migrate to 12.3(8) or later

12.2XN
Vulnerable; migrate to 12.3(8) or later

12.2XQ
Vulnerable; migrate to 12.3(8) or later

12.2XR
Vulnerable; migrate to 12.3(8) or later

12.2XS
Vulnerable; migrate to 12.3(8) or later

12.2XT
Vulnerable; migrate to 12.3(8) or later

12.2XU
Vulnerable; migrate to 12.3(12) or later

12.2XV
Vulnerable; migrate to 12.3(8) or later

12.2XW
Vulnerable; migrate to 12.3(8) or later

12.2YA
Vulnerable; migrate to 12.3(8) or later

12.2YB
Vulnerable; migrate to 12.3(8) or later

12.2YC
Vulnerable; migrate to 12.3(8) or later

12.2YD
Vulnerable; migrate to 12.3(8)T or later

12.2YE
Vulnerable; migrate to 12.2(25)S or later

12.2YF
Vulnerable; migrate to 12.3(8) or later

12.2YG
Vulnerable; migrate to 12.3(8) or later

12.2YH
Vulnerable; migrate to 12.3(8) or later

12.2YJ
Vulnerable; migrate to 12.3(8) or later

12.2YK
Vulnerable; migrate to 12.3(8)T or later

12.2YL
Vulnerable; migrate to 12.3(8)T or later

12.2YM
Vulnerable; migrate to 12.3(8)T or later

12.2YN
Vulnerable; migrate to 12.3(8)T or later

12.2YO
Not vulnerable

12.2YP
Vulnerable; migrate to 12.3(8) or later

12.2YQ
Vulnerable; migrate to 12.3(4)T13 or later

12.2YR
Vulnerable; migrate to 12.3(4)T13 or later

12.2YS
Vulnerable; migrate to 12.3(8)T or later

12.2YT
Vulnerable; migrate to 12.3(8) or later

12.2YU
Vulnerable; migrate to 12.3(8)T or later

12.2YV
Vulnerable; migrate to 12.3(4)T13 or later

12.2YW
Vulnerable; migrate to 12.3(8)T or later

12.2YX
Vulnerable; migrate to 12.3(14)T or later

12.2YY
Vulnerable; migrate to 12.3(4)T13 or later

12.2YZ
Vulnerable; migrate to 12.2(25)S or later

12.2ZA
Vulnerable; migrate to 12.2(17d)SXBa or later

12.2ZB
Vulnerable; migrate to 12.3(8)T or later

12.2ZC
Vulnerable; migrate to 12.3(8)T or later

12.2ZD
Vulnerable; contact TAC

12.2ZE
Vulnerable; migrate to 12.3(8) or laer

12.2ZF
Vulnerable; migrate to 12.3(4)T13 or later

12.2ZG
Vulnerable; for SOHO9x, migrate to 12.3(8)YG2 or later. For c83x, migrate to 12.3(2)XA3 or later

12.2ZH
Vulnerable; contact TAC

12.2ZJ
Vulnerable; migrate to 12.3(8)T or later

12.2ZL
Vulnerable; contact TAC

12.2ZN
Vulnerable; migrate to 12.3(4)T13 or later

12.2ZP
Vulnerable; migrate to 12.3(8)XY or later

Affected 12.3-Based Release
Rebuild
Maintenance

12.3
12.3(8)

12.3B
Vulnerable; migrate to 12.3(8)T7 or later

12.3BC
12.3(9a)BC

12.3BW
Vulnerable; migrate to 12.3(8)T or later

12.3JA
12.3(8)JA

12.3JEA
All 12.3JEA releases are fixed

12.3JEB
All 12.3JEA releases are fixed

12.3JK
12.3(2)JK2
12.3(8)JK

12.3JX
12.3(7)JX6
12.3(11)JX

12.3T
12.3(4)T13
12.3(8)T

12.3TPC
12.3(4)TPC11b

12.3XA
12.3(2)XA6

12.3XB
Vulnerable; migrate to 12.3(8)T or later

12.3XC
Vulnerable; contact TAC

12.3XD
Vulnerable; migrate to 12.3(8)T7 or later

12.3XE
Vulnerable; contact TAC

12.3XF
Vulnerable; migrate to 12.3(11)T or later

12.3XG
Vulnerable; contact TAC

12.3XH
Vulnerable; migrate to 12.3(11)T or later

12.3XI
12.3(7)XI8

12.3XJ
Vulnerable; migrate to 12.3(8)XW or later

12.3XK
Vulnerable; migrate to 12.3(14)T or later

12.3XQ
Vulnerable; migrate to 12.4(1) or later

12.3XR
All 12.3XR releases are fixed

12.3XS
All 12.3XS releases are fixed

12.3XU
All 12.3XU releases are fixed

12.3XW
All 12.3XW releases are fixed

12.3XX
All 12.3XX releases are fixed

12.3XY
All 12.3XR releases are fixed

12.3YA
All 12.3YA releases are fixed

12.3YD
All 12.3YD releases are fixed

12.3YF
All 12.3YF releases are fixed

12.3YG
All 12.3YG releases are fixed

12.3YH
All 12.3YH releases are fixed

12.3YI
All 12.3YI releases are fixed

12.3YJ
All 12.3YJ releases are fixed

12.3YK
All 12.3YK releases are fixed

12.3YM
All 12.3YM releases are fixed

12.3YQ
All 12.3YQ releases are fixed

12.3YS
All 12.3YS releases are fixed

12.3YT
All 12.3YT releases are fixed

12.3YU
All 12.3YU releases are fixed

12.3YX
All 12.3YX releases are fixed

12.3YZ
All 12.3YZ releases are fixed

Affected 12.4-Based Release
Rebuild
Maintenance

All 12.4 releases are fixed

Cisco IOS XR Version
SMU ID
Package Installation Envelopes

3.2.2 for CRS-1
AA01482
hfr-base-3.2.2.CSCeh52410.pie

3.2.3 for CRS-1
AA01483
hfr-base-3.2.3.CSCeh52410.pie

3.2.4 for CRS-1
AA01484
hfr-base-3.2.4.CSCeh52410.pie

3.2.6 for CRS-1
AA01727
hfr-base-3.2.6.CSCeh52410.pie

3.3.x for CRS-1 and XR12000
Fixed

3.4.x for CRS-1 and XR12000
Fixed

IOS XR Package Installation Envelopes (PIE) can be downloaded from: http://www.cisco.com/pcgi-bin/tablebuild.pl/iosxr-smu?sort=release ( registered customers only) . Installation instructions are included in the accompanying .txt files.

Workarounds
Additional mitigations that can be deployed on Cisco devices within the network are available in the Cisco Applied Intelligence companion document for this advisory:

http://www.cisco.com/warp/public/707/cisco-air-20070124-crafted-ip-option.shtml

IP Options Selective Drop
The IP Options Selective Drop feature allows Cisco routers to mitigate the effects of IP options by dropping packets containing them or by not processing (ignoring) IP options in a packet.

The most effective workaround is using the "drop" option of this global configuration command: ip options drop. This command will drop all IP packets containing IP options that are both destined to the router itself or transiting through the router before they are processed, preventing exploitation locally and downstream.

The IP Options Selective Drop feature is available beginning in Cisco IOS software version 12.0(23)S for 12000, 12.0(32)S for 10720, and 12.3(4)T, 12.2(25)S, and 12.2(27)SBC for other hardware platforms.

Please note that deploying this command will drop legitimate packets containing IP options as well. Protocols this may impact include RSVP (used by Microsoft NetMeeting), MPLS TE, MPLS OAM, DVMRP, IGMPv3, IGMPv2, and legitimate PGM.

Note: The ignore option of the global command ip options ignore, available only on the Cisco 12000 router beginning in 12.0(23)S, is NOT a workaround for this issue.

Additional information about IP Options Selective Drop feature is available at http://www.cisco.com/en/US/products/sw/iosswrel/ps1829/products_feature_guide09186a00801d4a94.html.

Transit Access Control Lists (ACLs)
Configure an interface ACL that blocks traffic of these types:

Echo (Ping) ICMP type 8

Timestamp ICMP type 13

Information Request ICMP type 15

Address Mask Request ICMP Type 17

Protocol Independent Multicast (PIM) IP protocol 103

Pragmatic General Multicast (PGM) IP protocol 113

URL Rendezvous Directory (URD) TCP port 465

The Internet Control Message Protocol is an integral part of the Transmission Control Protocol/Internet Protocol (TCP/IP) protocol suite that is used to report error conditions and provide diagnostic information. Filtering ICMP messages may impact this error condition and diagnostic reporting including "ping" and Windows traceroute which uses ICMP ping.

If the device is configured to process PIM, PGM, or URD, blocking those packets will prevent legitimate operation of the protocols.

Since the source IP address of these packets can be easily spoofed, the affected traffic should be blocked on all of the device's IPv4 interfaces.

The following ACL is specifically designed to block attack traffic and should be applied to all IPv4 interfaces of the device and should include topology-specific filters:

access-list 150 deny icmp any any echo
access-list 150 deny icmp any any information-request
access-list 150 deny icmp any any timestamp-request
access-list 150 deny icmp any any mask-request
access-list 150 deny tcp any any eq 465
access-list 150 deny 103 any any
access-list 150 deny 113 any any
access-list 150 permit ip any any

interface serial 2/0
ip access-group 150 inThese ACL statements should be deployed at the network edge as part of a transit access list which will protect the router where the ACL is configured as well as other devices behind it. Further information about transit ACLs is available in the white paper "Transit Access Control Lists: Filtering at Your Edge", available at http://www.cisco.com/en/US/tech/tk648/tk361/technologies_white_paper09186a00801afc76.shtml.

The following Cisco IOS XR ACL is specifically designed to block attack traffic and should be applied to all IPv4 interfaces of the device and should include topology-specific filters:

ipv4 access-list ios-xr-transit-acl
10 deny icmp any any echo
20 deny icmp any any information-request
30 deny icmp any any timestamp-request
40 deny icmp any any mask-request
50 deny tcp any any eq 465
60 deny 103 any any
70 deny 113 any any
80 permit ip any any

interface POS 0/2/0/
ipv4 access-group ios-xr-transit-acl ingressInformation about configuring access lists on Cisco IOS XR is available at http://www.cisco.com/en/US/products/ps5763/products_command_reference_chapter09186a00803e01ae.html.

Infrastructure ACLs
Although it is often difficult to block traffic transiting your network, it is possible to identify traffic which should never be allowed to target your infrastructure devices and block that traffic at the border of your network. Infrastructure ACLs are considered a network security best practice and should be considered as a long-term addition to good network security as well as a workaround for this specific vulnerability. The ACL example shown below should be included as part of the deployed infrastructure access list which will protect all devices with IP addresses in the infrastructure IP address range.

Cisco IOS
access-list 150 deny icmp any INFRASTRUCTURE_ADDRESSES echo
access-list 150 deny icmp any INFRASTRUCTURE_ADDRESSES information-request
access-list 150 deny icmp any INFRASTRUCTURE_ADDRESSES timestamp-request
access-list 150 deny icmp any INFRASTRUCTURE_ADDRESSES mask-request
access-list 150 deny tcp any INFRASTRUCTURE_ADDRESSES eq 465
access-list 150 deny 103 any INFRASTRUCTURE_ADDRESSES
access-list 150 deny 113 any INFRASTRUCTURE_ADDRESSES
access-list 150 permit ip any any

interface serial 2/0
ip access-group 150 inCisco IOS XR
ipv4 access-list ios-xr-infrastructure-acl
10 deny icmp any INFRASTRUCTURE_ADDRESSES echo
20 deny icmp any INFRASTRUCTURE_ADDRESSES information-request
30 deny icmp any INFRASTRUCTURE_ADDRESSES timestamp-request
40 deny icmp any INFRASTRUCTURE_ADDRESSES mask-request
50 deny tcp any INFRASTRUCTURE_ADDRESSES eq 465
60 deny 103 any INFRASTRUCTURE_ADDRESSES
70 deny 113 any INFRASTRUCTURE_ADDRESSES
80 permit ip any any

interface POS 0/2/0/2
ipv4 access-group ios-xr-infrastructure-acl ingressThe white paper entitled "Protecting Your Core: Infrastructure Protection Access Control Lists" presents guidelines and recommended deployment techniques for infrastructure protection access lists and is available at http://www.cisco.com/en/US/tech/tk648/tk361/technologies_white_paper09186a00801a1a55.shtml.

Information about configuring access lists on Cisco IOS XR is available at http://www.cisco.com/en/US/products/ps5763/products_command_reference_chapter09186a00803e01ae.html.

Receive ACLs
For distributed platforms, receive ACLs may be an option starting in Cisco IOS Software Versions 12.0(21)S2 for the 12000 (GSR), 12.0(24)S for the 7500, and 12.0(31)S for the 10720. The receive ACL protects the device from harmful traffic before the traffic can impact the route processor. A receive ACL is designed to protect only the device on which it is configured. On the 12000, transit traffic is never affected by a receive ACL. Because of this, the destination IP address "any" used in the example ACL entries below only refer to the router's own physical or virtual IP addresses. On the 7500 and 10720, transit traffic with IP options set will be subject to the receive ACL and permitted or denied accordingly. Receive ACLs are considered a network security best practice and should be considered as a long-term addition to good network security as well as a workaround for this specific vulnerability.

The white paper entitled "GSR: Receive Access Control Lists" will help you identify and allow legitimate traffic to your device and deny all unwanted packets and is available at http://www.cisco.com/en/US/tech/tk648/tk361/technologies_white_paper09186a00801a0a5e.shtml

The following receive path ACL is designed specifically to block this attack traffic:

access-list 101 deny icmp any any echo
access-list 101 deny icmp any any information-request
access-list 101 deny icmp any any timestamp-request
access-list 101 deny icmp any any mask-request
access-list 101 deny tcp any any eq 465
access-list 101 deny 103 any any
access-list 101 deny 113 any any
access-list 101 permit ip any any
!
ip receive access-list 101Control Plane Policing
The Control Plane Policing (CoPP) feature may be used to mitigate this vulnerability. In the following example, any packets that can exploit the vulnerability are denied while all other IP traffic is permitted. Because of the way routers process packets with IP options, CoPP will be applied to attack packets destined for the router itself and packets transiting through the router to other destination IP addresses. This applies to all platforms except the 12000 where only attack packets destined for the router itself will be dropped.

access-list 100 permit icmp any any echo
access-list 100 permit icmp any any information-request
access-list 100 permit icmp any any timestamp-request
access-list 100 permit icmp any any mask-request
access-list 100 permit tcp any any eq 465
access-list 100 permit 103 any any
access-list 100 permit 113 any any
access-list 100 deny ip any any
!
class-map match-all drop-options-class
match access-group 100
!
!
policy-map drop-options-policy
class drop-options-class
drop
!
control-plane
service-policy input drop-options-policyPlease note that in the 12.0S, 12.2S, and 12.2SX Cisco IOS trains, the policy-map syntax is different:

policy-map drop-options-policy
class drop-options-class
police 32000 1500 1500 conform-action drop exceed-action dropBecause of the way routers process packets with IP options, CoPP will be applied to attack packets destined for the router itself and packets transiting through the router to other destination IP addresses. In the following example, only packets with IP options that can exploit the vulnerability and that are destined for the router or that transit through the router are denied while all other IP traffic is permitted.

ip access-list extended drop-affected-options
permit icmp any any echo option any-options
permit icmp any any information-request option any-options
permit icmp any any timestamp-request option any-options
permit icmp any any mask-request option any-options
permit pim any any option any-options
permit 113 any any option any-options
permit tcp any any eq 465 option any-options
deny ip any any
!
class-map match-all drop-options-class
match access-group name drop-affected-options
!
!
policy-map drop-opt-policy
class drop-options-class
drop
!
control-plane
service-policy input drop-opt-policyPlease note that in the 12.2S Cisco IOS train, the policy-map syntax is different:

policy-map drop-opt-policy
class drop-options-class
police 32000 1500 1500 conform-action drop exceed-action dropCoPP is available in Cisco IOS release trains 12.0S, 12.2SX, 12.2S, 12.3T, 12.4, and 12.4T.

ACL support for filtering IP options requires named ACLs. ACL support for filtering IP options is not available in 12.0S or 12.2SX.

Please note that PGM packets typically use the "Router Alert" Option, and dropping PGM packets with IP options will affect legitimate PGM packets.

In the above CoPP examples, the ACL entries that match the exploit packets with the "permit" action result in these packets being discarded by the policy-map drop function, while packets that match the "deny" action are not affected by the policy-map drop function.

Additional information on the configuration and use of the CoPP feature can be found at http://www.cisco.com/en/US/products/ps6642/products_white_paper0900aecd804fa16a.shtml and http://www.cisco.com/en/US/products/sw/iosswrel/ps1838/products_feature_guide09186a008052446b.html.

Additional information for filtering IP Options with access lists can be found at http://www.cisco.com/en/US/products/sw/iosswrel/ps5207/products_feature_guide09186a00801d4a7d.html.

Obtaining Fixed Software
Cisco will make free software available to address this vulnerability for affected customers. This advisory will be updated as fixed software becomes available. Prior to deploying software, customers should consult their maintenance provider or check the software for feature set compatibility and known issues specific to their environment.

Customers may only install and expect support for the feature sets they have purchased. By installing, downloading, accessing or otherwise using such software upgrades, customers agree to be bound by the terms of Cisco's software license terms found at http://www.cisco.com/public/sw-license-agreement.html, or as otherwise set forth at Cisco.com Downloads at http://www.cisco.com/public/sw-center/sw-usingswc.shtml.

Do not contact either "psirt@cisco.com" or "security-alert@cisco.com" for software upgrades.

Customers with Service Contracts
Customers with contracts should obtain upgraded software through their regular update channels. For most customers, this means that upgrades should be obtained through the Software Center on Cisco's worldwide website at http://www.cisco.com.

Customers using Third Party Support Organizations
Customers whose Cisco products are provided or maintained through prior or existing agreement with third-party support organizations such as Cisco Partners, authorized resellers, or service providers should contact that support organization for guidance and assistance with the appropriate course of action in regards to this advisory.

The effectiveness of any workaround or fix is dependent on specific customer situations such as product mix, network topology, traffic behavior, and organizational mission. Due to the variety of affected products and releases, customers should consult with their service provider or support organization to ensure any applied workaround or fix is the most appropriate for use in the intended network before it is deployed.

Customers without Service Contracts
Customers who purchase direct from Cisco but who do not hold a Cisco service contract and customers who purchase through third-party vendors but are unsuccessful at obtaining fixed software through their point of sale should get their upgrades by contacting the Cisco Technical Assistance Center (TAC). TAC contacts are as follows.

+1 800 553 2447 (toll free from within North America)

+1 408 526 7209 (toll call from anywhere in the world)

e-mail: tac@cisco.com

Have your product serial number available and give the URL of this notice as evidence of your entitlement to a free upgrade. Free upgrades for non-contract customers must be requested through the TAC.

Refer to http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml for additional TAC contact information, including special localized telephone numbers and instructions and e-mail addresses for use in various languages.

Exploitation and Public Announcements
The Cisco PSIRT is not aware of any public announcements or malicious use of the vulnerability described in this advisory. This vulnerability was discovered during internal testing.

Status of this Notice: FINAL
THIS DOCUMENT IS PROVIDED ON AN "AS IS" BASIS AND DOES NOT IMPLY ANY KIND OF GUARANTEE OR WARRANTY, INCLUDING THE WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR USE. YOUR USE OF THE INFORMATION ON THE DOCUMENT OR MATERIALS LINKED FROM THE DOCUMENT IS AT YOUR OWN RISK. CISCO RESERVES THE RIGHT TO CHANGE OR UPDATE THIS DOCUMENT AT ANY TIME.

A stand-alone copy or Paraphrase of the text of this document that omits the distribution URL in the following section is an uncontrolled copy, and may lack important information or contain factual errors.

Distribution
This advisory is posted on Cisco's worldwide website at :

http://www.cisco.com/warp/public/707/cisco-sa-20070124-crafted-ip-option.shtml

In addition to worldwide web posting, a text version of this notice is clear-signed with the Cisco PSIRT PGP key and is posted to the following e-mail and Usenet news recipients.

cust-security-announce@cisco.com

first-teams@first.org

bugtraq@securityfocus.com

vulnwatch@vulnwatch.org

cisco@spot.colorado.edu

cisco-nsp@puck.nether.net

full-disclosure@lists.grok.org.uk

comp.dcom.sys.cisco@newsgate.cisco.com