The is_asn1 function in strongSwan 4.1.11 through 5.0.4 does not properly validate the return value of the asn1_length function, which allows remote attackers to cause a denial of service (segmentation fault) via a (1) XAuth username, (2) EAP identity, or (3) PEM encoded file that starts with a 0x04, 0x30, or 0x31 character followed by an ASN.1 length value that triggers an integer overflow.
The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary. This may result in read or write operations on unexpected memory locations that could be linked to other variables, data structures, or internal program data.
| Link | Tags |
|---|---|
| http://secunia.com/advisories/54315 | third party advisory vendor advisory |
| http://www.securityfocus.com/bid/61564 | vdb entry |
| http://secunia.com/advisories/54524 | third party advisory vendor advisory |
| http://strongswan.org/blog/2013/08/01/strongswan-5.1.0-released.html | vendor advisory |
| http://lists.opensuse.org/opensuse-updates/2013-08/msg00022.html | vendor advisory |
| http://strongswan.org/blog/2013/08/01/strongswan-denial-of-service-vulnerability-%28cve-2013-5018%29.html | vendor advisory |
| http://lists.opensuse.org/opensuse-updates/2013-08/msg00021.html | vendor advisory |
| https://lists.strongswan.org/pipermail/users/2013-July/009540.html | mailing list exploit |
| http://lists.opensuse.org/opensuse-updates/2013-08/msg00050.html | vendor advisory |