{"id":2368,"date":"2005-05-12T00:00:00","date_gmt":"2005-05-12T00:00:00","guid":{"rendered":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2005\/05\/12\/government-warns-of-ipsec-vpn-flaw\/"},"modified":"2021-12-30T11:41:10","modified_gmt":"2021-12-30T11:41:10","slug":"government-warns-of-ipsec-vpn-flaw","status":"publish","type":"post","link":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2005\/05\/12\/government-warns-of-ipsec-vpn-flaw\/","title":{"rendered":"Government warns of IPsec VPN flaw"},"content":{"rendered":"<p>The UK&#8217;s National Infrastructure Security Coordination Centre (NISCC) has issued a serious warning over the safety of IPsec virtual private networks (VPNs).<\/p>\n","protected":false},"excerpt":{"rendered":"<p>On its Web site, NISCC said a flaw in the IPsec VPN protocol could allow hackers to obtain a text version of encrypted communications with only &#8220;moderate effort&#8221;.<\/p>\n<p>The flaw, which NISCC rated as &#8216;high risk&#8217;, makes it possible for an attacker to intercept IP packets travelling between two IPsec devices and modify the encapsulation security payload &#8212; a sub-protocol that encrypts the data being transported.  This could ultimately expose this data to an unauthorised third party.<\/p>\n<p>On its Web site, NISCC wrote: &#8220;By making careful modifications to selected portions of the payload of the outer packet, an attacker can effect controlled changes to the header of the inner (encrypted) packet&#8230;If these messages can be intercepted by an attacker, then plaintext data is revealed.&#8221;<\/p>\n<p>NISCC has published a number of solutions to this issue.<\/p>\n<p>http:\/\/news.zdnet.co.uk\/internet\/security\/0,39020375,39198102,00.htm<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[13],"tags":[],"class_list":["post-2368","post","type-post","status-publish","format-standard","hentry","category-warnings"],"_links":{"self":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/2368","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/comments?post=2368"}],"version-history":[{"count":1,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/2368\/revisions"}],"predecessor-version":[{"id":4855,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/2368\/revisions\/4855"}],"wp:attachment":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=2368"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=2368"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=2368"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}