bugtraq - Re: multiple payload handling flaws in isakmpd, again

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date: Thu, 1 Jan 2004 21:20:18 +0100
From: Thomas Walpuski <thomas@...nknerd.de>
To: bugtraq@...urityfocus.com
Subject: Re: multiple payload handling flaws in isakmpd, again

There is one important thing I forgot to mention. In isakmpd deleting an
IPsec SA also means deleting the appropriate IPsec policy in almost any
case. Take a look at pf_key_v2_delete_spi() in pf_key_v2.c. It calls
pf_key_v2_disable_sa(), the policy eraser ;-), if the SA was not
acquired through the kernel:

  if (!(sa->flags & SA_FLAG_REPLACED)
      && !(sa->flags & SA_FLAG_ONDEMAND))
    pf_key_v2_disable_sa (sa, incoming);

Now imagine an IPsec tunnel between two security gateways running
isakmpd. Both gateways are attacked, IPsec SAs and policies get removed,
...

Thomas Walpuski