Red Hat Bugzilla – Bug 189878
Racoon uses incorrect source address on interfaces with multiple addresses
Last modified: 2008-05-01 11:38:06 EDT
Description of problem:
The bug and behaviour is documented here:
The patch was accepted and the change is still present in the latest 0.6.5 release.
Applying the patch and rebuilding 0.2.5-0.7 fixed this exact same issue for me
where racoon was using the wrong address on an interface with multiple addresses
configured. This broke identity protection ("verify_identifier yes" in
racoon.conf) which was using the IP address as the identifier.
I'll attach the patch for completeness.
Version-Release number of selected component (if applicable):
(0.3.3-6 in RHEL4 doesn't contain the fix either so I suspect is also vulnerable)
Always on a particular machine, although some machines weren't affected,
possibly due to the order the addresses were configured on the interface. Not
Steps to Reproduce:
1. Assign multiple addresses to an interface used by racoon to establish IPSEC
connection, preferably with identify protection enabled
2. Watch UDP/500 packets leave the interface
Packets have an incorrect source address which leads to them not matching any
known configuration on the remote peer, which can cause identify protection to fail.
Packets should have the correct source address
Created attachment 128202 [details]
Patch to fix behaviour
change the owner of ipsec-tools
This bug is filed against RHEL 3, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products. Since
this bug does not meet that criteria, it is now being closed.
For more information of the RHEL errata support policy, please visit:
If you feel this bug is indeed mission critical, please contact your
support representative. You may be asked to provide detailed
information on how this bug is affecting you.