Important CentOS openswan Update
|openswan-2.6.32-20.el6_4.i686.rpm, openswan-2.6.32-20.el6_4.src.rpm, openswan-2.6.32-20.el6_4.x86_64.rpm, openswan-2.6.32-5.el5_9.i386.rpm, openswan-2.6.32-5.el5_9.src.rpm, openswan-2.6.32-5.el5_9.x86_64.rpm, openswan-doc-2.6.32-20.el6_4.i686.rpm, openswan-doc-2.6.32-20.el6_4.x86_64.rpm, openswan-doc-2.6.32-5.el5_9.i386.rpm, openswan-doc-2.6.32-5.el5_9.x86_64.rpm|
|rhn.redhat.com, lists.centos.org, lists.centos.org|
Updated openswan packages that fix one security issue are now available for
Red Hat Enterprise Linux 5 and 6.
The Red Hat Security Response Team has rated this update as having
important security impact. A Common Vulnerability Scoring System (CVSS)
base score, which gives a detailed severity rating, is available from the
CVE link in the References section.
Openswan is a free implementation of Internet Protocol Security (IPsec)
and Internet Key Exchange (IKE). IPsec uses strong cryptography to provide
both authentication and encryption services. These services allow you to
build secure tunnels through untrusted networks. When using Opportunistic
Encryption, Openswan's pluto IKE daemon requests DNS TXT records to obtain
public RSA keys of itself and its peers.
A buffer overflow flaw was found in Openswan. If Opportunistic Encryption
were enabled ("oe=yes" in "/etc/ipsec.conf") and an RSA key configured, an
attacker able to cause a system to perform a DNS lookup for an
attacker-controlled domain containing malicious records (such as by sending
an email that triggers a DKIM or SPF DNS record lookup) could cause
Openswan's pluto IKE daemon to crash or, potentially, execute arbitrary
code with root privileges. With "oe=yes" but no RSA key configured, the
issue can only be triggered by attackers on the local network who can
control the reverse DNS entry of the target system. Opportunistic
Encryption is disabled by default. (CVE-2013-2053)
This issue was discovered by Florian Weimer of the Red Hat Product Security
All users of openswan are advised to upgrade to these updated packages,
which contain backported patches to correct this issue. After installing
this update, the ipsec service will be restarted automatically.
Please see https://www.redhat.com/footer/terms-of-use.html
Am I vulnerable?
The constraints below list the versions that this vulnerability is patched in, and versions that are unaffected. If a patch is ready but unrealeased, then it is pending.
Or, you can just let us figure it out for you! Appcanary continously monitor your installed packages, and tell you if any of them are vulnerable.Sign up for monitoring
Affected package information