A vulnerability, which was classified asproblematic, was found in Libreswan up to 4.14. Affected is some unknown processing of the component IKEv1 Handler. Upgrading to version 5.0 eliminates this vulnerability.
The Libreswan Project was notified of anissue causing libreswan to restart when using IKEv1 without specifying an esp= line. When the peer requests AES-GMAC, libreswan s default proposal handler causes an assertion failure and crashes and restarts. IKEv2 connections are not affected.
The Libreswan Project was notified of an issue causing libreswan to restart when using IKEv1 without specifying an esp= line. When the peer requests AES-GMAC, libreswan s default proposal handler causes an assertion failure and crashes and restarts. IKEv2 connections are not affected.
The Libreswan Project was notified of an issue causing libreswan to restart when using IKEv1 without specifying an esp= line. When the peer requests AES-GMAC, libreswan s default proposal handler causes an assertion failure and crashes and restarts. IKEv2 connections are not affected.
The Libreswan Project was notified of an issue causing libreswan to restart when using IKEv1 without specifying an esp= line. When the peer requests AES-GMAC, libreswan s default proposal handler causes an assertion failure and crashes and restarts. IKEv2 connections are not affected.
The Libreswan Project was notified of an issue causing libreswan to restart when using IKEv1 without specifying an esp= line. When the peer requests AES-GMAC, libreswan s default proposal handler causes an assertion failure and crashes and restarts. IKEv2 connections are not affected.
The Libreswan Project was notified of an issue causing libreswan to restart when using IKEv1 without specifying an esp= line. When the peer requests AES-GMAC, libreswan s default proposal handler causes an assertion failure and crashes and restarts. IKEv2 connections are not affected.
The Libreswan Project was notified of an issue causing libreswan to restart when using IKEv1 without specifying an esp= line. When the peer requests AES-GMAC, libreswan s default proposal handler causes an assertion failure and crashes and restarts. IKEv2 connections are not affected.
The Libreswan Project was notified of an issue causing libreswan to restart when using IKEv1 without specifying an esp= line. When the peer requests AES-GMAC, libreswan s default proposal handler causes an assertion failure and crashes and restarts. IKEv2 connections are not affected.
The Libreswan Project was notified of an issue causing libreswan to restart when using IKEv1 without specifying an esp= line. When the peer requests AES-GMAC, libreswan s default proposal handler causes an assertion failure and crashes and restarts. IKEv2 connections are not affected.
The Libreswan Project was notified of an issue causing libreswan to restart when using IKEv1 without specifying an esp= line. When the peer requests AES-GMAC, libreswan s default proposal handler causes an assertion failure and crashes and restarts. IKEv2 connections are not affected.
The Libreswan Project was notified of an issue causing libreswan to restart when using IKEv1 without specifying an esp= line. When the peer requests AES-GMAC, libreswan s default proposal handler causes an assertion failure and crashes and restarts. IKEv2 connections are not affected.
The Libreswan Project was notified of an issue causing libreswan to restart when using IKEv1 without specifying an esp= line. When the peer requests AES-GMAC, libreswan s default proposal handler causes an assertion failure and crashes and restarts. IKEv2 connections are not affected.
The Libreswan Project was notified of an issue causing libreswan to restart when using IKEv1 without specifying an esp= line. When the peer requests AES-GMAC, libreswan s default proposal handler causes an assertion failure and crashes and restarts. IKEv2 connections are not affected.
The Libreswan Project was notified of an issue causing libreswan to restart when using IKEv1 without specifying an esp= line. When the peer requests AES-GMAC, libreswan s default proposal handler causes an assertion failure and crashes and restarts. IKEv2 connections are not affected.
The Libreswan Project was notified of an issue causing libreswan to restart when using IKEv1 without specifying an esp= line. When the peer requests AES-GMAC, libreswan s default proposal handler causes an assertion failure and crashes and restarts. IKEv2 connections are not affected.
The Libreswan Project was notified of an issue causing libreswan to restart when using IKEv1 without specifying an esp= line. When the peer requests AES-GMAC, libreswan s default proposal handler causes an assertion failure and crashes and restarts. IKEv2 connections are not affected.
The Libreswan Project was notified of an issue causing libreswan to restart when using IKEv1 without specifying an esp= line. When the peer requests AES-GMAC, libreswan s default proposal handler causes an assertion failure and crashes and restarts. IKEv2 connections are not affected.
The Libreswan Project was notified of an issue causing libreswan to restart when using IKEv1 without specifying an esp= line. When the peer requests AES-GMAC, libreswan s default proposal handler causes an assertion failure and crashes and restarts. IKEv2 connections are not affected.
The Libreswan Project was notified of an issue causing libreswan to restart when using IKEv1 without specifying an esp= line. When the peer requests AES-GMAC, libreswan s default proposal handler causes an assertion failure and crashes and restarts. IKEv2 connections are not affected.
The Libreswan Project was notified of an issue causing libreswan to restart when using IKEv1 without specifying an esp= line. When the peer requests AES-GMAC, libreswan s default proposal handler causes an assertion failure and crashes and restarts. IKEv2 connections are not affected.
The Libreswan Project was notified of an issue causing libreswan to restart when using IKEv1 without specifying an esp= line. When the peer requests AES-GMAC, libreswan s default proposal handler causes an assertion failure and crashes and restarts. IKEv2 connections are not affected.
The Libreswan Project was notified of an issue causing libreswan to restart when using IKEv1 without specifying an esp= line. When the peer requests AES-GMAC, libreswan s default proposal handler causes an assertion failure and crashes and restarts. IKEv2 connections are not affected.
The Libreswan Project was notified of an issue causing libreswan to restart when using IKEv1 without specifying an esp= line. When the peer requests AES-GMAC, libreswan s default proposal handler causes an assertion failure and crashes and restarts. IKEv2 connections are not affected.
The Libreswan Project was notified of an issue causing libreswan to restart when using IKEv1 without specifying an esp= line. When the peer requests AES-GMAC, libreswan s default proposal handler causes an assertion failure and crashes and restarts. IKEv2 connections are not affected.
The Libreswan Project was notified of an issue causing libreswan to restart when using IKEv1 without specifying an esp= line. When the peer requests AES-GMAC, libreswan s default proposal handler causes an assertion failure and crashes and restarts. IKEv2 connections are not affected.
TheLibreswanProject was notified of an issue causing libreswan to restart when using IKEv1 without specifying an esp= line. When the peer requests AES-GMAC, libreswan s default proposal handler causes an assertion failure and crashes and restarts. IKEv2 connections are not affected.
The Libreswan Project was notified of an issue causing libreswan to restart when using IKEv1 without specifying an esp= line. When the peer requests AES-GMAC, libreswan s default proposal handler causes an assertion failure and crashes and restarts. IKEv2 connections are not affected.
The Libreswan Project was notified of an issue causing libreswan to restart when using IKEv1 without specifying an esp= line. When the peer requests AES-GMAC, libreswan s default proposal handler causes an assertion failure and crashes and restarts. IKEv2 connections are not affected.
The Libreswan Project was notified of an issue causing libreswan to restart when using IKEv1 without specifying an esp= line. When the peer requests AES-GMAC, libreswan s default proposal handler causes an assertion failure and crashes and restarts. IKEv2 connections are not affected.
The Libreswan Project was notified of an issue causing libreswan to restart when using IKEv1 without specifying an esp= line. When the peer requests AES-GMAC, libreswan s default proposal handler causes an assertion failure and crashes and restarts. IKEv2 connections are not affected.
The Libreswan Project was notified of an issue causing libreswan to restart when using IKEv1 without specifying an esp= line. When the peer requests AES-GMAC, libreswan s default proposal handler causes an assertion failure and crashes and restarts. IKEv2 connections are not affected.
The Libreswan Project was notified of an issue causing libreswan to restart when using IKEv1 without specifying an esp= line. When the peer requests AES-GMAC, libreswan s default proposal handler causes an assertion failure and crashes and restarts. IKEv2 connections are not affected.
The Libreswan Project was notified of an issue causing libreswan to restart when using IKEv1 without specifying an esp= line. When the peer requests AES-GMAC, libreswan s default proposal handler causes an assertion failure and crashes and restarts. IKEv2 connections are not affected.
The Libreswan Project was notified of an issue causing libreswan to restart when using IKEv1 without specifying an esp= line. When the peer requests AES-GMAC, libreswan s default proposal handler causes an assertion failure and crashes and restarts. IKEv2 connections are not affected.