search menu icon-carat-right cmu-wordmark

CERT Coordination Center

IPComp encapsulation nested payload vulnerability

Vulnerability Note VU#668220

Original Release Date: 2011-04-01 | Last Revised: 2011-08-16

Overview

Some IPComp implementations may contain a kernel memory corruption vulnerability in their handling of nested encapsulation of IPComp payloads.

Description

RFC 3173 defines the IP Payload Compression Protocol (IPComp) as:

IP payload compression is a protocol to reduce the size of IP datagrams. This protocol will increase the overall communication performance between a pair of communicating hosts/gateways ("nodes") by compressing the datagrams, provided the nodes have sufficient computation power, through either CPU capacity or a compression coprocessor, and the communication is over slow or congested links.

IPComp is commonly used in conjunction with IPsec implementations.

Some network stack implementations, particularly those incorporating the KAME project or NetBSD project IPComp and IPsec implementations, may fail to check for stack overflow in their recursive handling of nested IPComp-encapsulated payloads. Exploitation of this vulnerability could allow a remote attacker to cause kernel memory corruption.

Impact

A remote attacker can cause a kernel stack overflow leading to a denial of service or possibly execute arbitrary code.

Solution

Apply a Patch from Your Vendor
Please see the Vendor Information below for specific vendor information and patches.


Workarounds

    • Filter IPComp (protocol number 108) at network borders if it is not required
    • Utilize packet filtering on workstations or servers to prevent the vulnerable code from being executed
    • Recompile affected software to disallow nested encapulation of IPComp payloads if possible

Vendor Information

Note that any systems derived from the KAME or NetBSD IPComp implementations may be vulnerable.

668220
 

View all 93 vendors View less vendors


CVSS Metrics

Group Score Vector
Base
Temporal
Environmental

References

Acknowledgements

Thanks to Tavis Ormandy of Google for reporting this vulnerability.

This document was written by Michael Orlando.

Other Information

CVE IDs: CVE-2011-1547
Severity Metric: 54.77
Date Public: 2011-04-01
Date First Published: 2011-04-01
Date Last Updated: 2011-08-16 15:10 UTC
Document Revision: 38

Sponsored by CISA.