The sctp_auth_asoc_get_hmac function in net/sctp/auth.c in the Linux kernel before 2.6.36 does not properly validate the hmac_ids array of an SCTP peer, which allows remote attackers to cause a denial of service (memory corruption and panic) via a crafted value in the last element of this array.
The product does not properly control the allocation and maintenance of a limited resource.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Linux_kernel | Linux | * | 2.6.36 (excluding) |
| MRG for RHEL-5 | RedHat | kernel-rt-0:2.6.33.7-rt29.47.el5rt | * |
| Red Hat Enterprise Linux 6 | RedHat | kernel-0:2.6.32-71.7.1.el6 | * |
| Linux | Ubuntu | hardy | * |
| Linux | Ubuntu | jaunty | * |
| Linux | Ubuntu | karmic | * |
| Linux | Ubuntu | lucid | * |
| Linux | Ubuntu | maverick | * |
| Linux | Ubuntu | upstream | * |
| Linux-ec2 | Ubuntu | karmic | * |
| Linux-ec2 | Ubuntu | lucid | * |
| Linux-ec2 | Ubuntu | maverick | * |
| Linux-fsl-imx51 | Ubuntu | karmic | * |
| Linux-fsl-imx51 | Ubuntu | lucid | * |
| Linux-lts-backport-maverick | Ubuntu | lucid | * |
| Linux-mvl-dove | Ubuntu | karmic | * |
| Linux-mvl-dove | Ubuntu | lucid | * |
| Linux-mvl-dove | Ubuntu | maverick | * |
| Linux-ti-omap4 | Ubuntu | maverick | * |
Mitigation of resource exhaustion attacks requires that the target system either:
The first of these solutions is an issue in itself though, since it may allow attackers to prevent the use of the system by a particular valid user. If the attacker impersonates the valid user, they may be able to prevent the user from accessing the server in question.
The second solution is simply difficult to effectively institute – and even when properly done, it does not provide a full solution. It simply makes the attack require more resources on the part of the attacker.