ID CVE-2018-5388
Summary In stroke_socket.c in strongSwan before 5.6.3, a missing packet length check could allow a buffer underflow, which may lead to resource exhaustion and denial of service while reading from the socket.
References
Vulnerable Configurations
  • StrongSwan strongSwan 2.0.0
    cpe:2.3:a:strongswan:strongswan:2.0.0
  • StrongSwan strongSwan 2.0.1
    cpe:2.3:a:strongswan:strongswan:2.0.1
  • StrongSwan strongSwan 2.0.2
    cpe:2.3:a:strongswan:strongswan:2.0.2
  • StrongSwan strongSwan 2.1.0
    cpe:2.3:a:strongswan:strongswan:2.1.0
  • StrongSwan strongSwan 2.1.1
    cpe:2.3:a:strongswan:strongswan:2.1.1
  • StrongSwan strongSwan 2.1.2
    cpe:2.3:a:strongswan:strongswan:2.1.2
  • StrongSwan strongSwan 2.1.3
    cpe:2.3:a:strongswan:strongswan:2.1.3
  • StrongSwan strongSwan 2.1.4
    cpe:2.3:a:strongswan:strongswan:2.1.4
  • StrongSwan strongSwan 2.1.5
    cpe:2.3:a:strongswan:strongswan:2.1.5
  • StrongSwan strongSwan 2.3.0
    cpe:2.3:a:strongswan:strongswan:2.3.0
  • StrongSwan strongSwan 2.3.1
    cpe:2.3:a:strongswan:strongswan:2.3.1
  • StrongSwan strongSwan 2.3.2
    cpe:2.3:a:strongswan:strongswan:2.3.2
  • StrongSwan strongSwan 2.4.0
    cpe:2.3:a:strongswan:strongswan:2.4.0
  • StrongSwan strongSwan 2.4.0a
    cpe:2.3:a:strongswan:strongswan:2.4.0:a
  • StrongSwan strongSwan 2.4.1
    cpe:2.3:a:strongswan:strongswan:2.4.1
  • StrongSwan strongSwan 2.4.2
    cpe:2.3:a:strongswan:strongswan:2.4.2
  • StrongSwan strongSwan 2.4.3
    cpe:2.3:a:strongswan:strongswan:2.4.3
  • StrongSwan strongSwan 2.4.4
    cpe:2.3:a:strongswan:strongswan:2.4.4
  • StrongSwan strongSwan 2.5.0
    cpe:2.3:a:strongswan:strongswan:2.5.0
  • StrongSwan strongSwan 2.5.1
    cpe:2.3:a:strongswan:strongswan:2.5.1
  • StrongSwan strongSwan 2.5.2
    cpe:2.3:a:strongswan:strongswan:2.5.2
  • StrongSwan strongSwan 2.5.3
    cpe:2.3:a:strongswan:strongswan:2.5.3
  • StrongSwan strongSwan 2.5.4
    cpe:2.3:a:strongswan:strongswan:2.5.4
  • StrongSwan strongSwan 2.5.5
    cpe:2.3:a:strongswan:strongswan:2.5.5
  • StrongSwan strongSwan 2.5.6
    cpe:2.3:a:strongswan:strongswan:2.5.6
  • StrongSwan strongSwan 2.5.7
    cpe:2.3:a:strongswan:strongswan:2.5.7
  • StrongSwan strongSwan 2.6.0
    cpe:2.3:a:strongswan:strongswan:2.6.0
  • StrongSwan strongSwan 2.6.1
    cpe:2.3:a:strongswan:strongswan:2.6.1
  • StrongSwan strongSwan 2.6.2
    cpe:2.3:a:strongswan:strongswan:2.6.2
  • StrongSwan strongSwan 2.6.3
    cpe:2.3:a:strongswan:strongswan:2.6.3
  • StrongSwan strongSwan 2.6.4
    cpe:2.3:a:strongswan:strongswan:2.6.4
  • StrongSwan strongSwan 2.6.14
    cpe:2.3:a:strongswan:strongswan:2.6.14
  • StrongSwan strongSwan 2.6.16
    cpe:2.3:a:strongswan:strongswan:2.6.16
  • StrongSwan strongSwan 2.6.20
    cpe:2.3:a:strongswan:strongswan:2.6.20
  • StrongSwan strongSwan 2.6.21
    cpe:2.3:a:strongswan:strongswan:2.6.21
  • StrongSwan strongSwan 2.7.0
    cpe:2.3:a:strongswan:strongswan:2.7.0
  • StrongSwan strongSwan 2.7.2
    cpe:2.3:a:strongswan:strongswan:2.7.1
  • StrongSwan strongSwan 2.7.2
    cpe:2.3:a:strongswan:strongswan:2.7.2
  • StrongSwan strongSwan 2.7.3
    cpe:2.3:a:strongswan:strongswan:2.7.3
  • StrongSwan strongSwan 2.8.0
    cpe:2.3:a:strongswan:strongswan:2.8.0
  • StrongSwan strongSwan 2.8.1
    cpe:2.3:a:strongswan:strongswan:2.8.1
  • StrongSwan strongSwan 2.8.2
    cpe:2.3:a:strongswan:strongswan:2.8.2
  • StrongSwan strongSwan 2.8.3
    cpe:2.3:a:strongswan:strongswan:2.8.3
  • StrongSwan strongSwan 2.8.4
    cpe:2.3:a:strongswan:strongswan:2.8.4
  • StrongSwan strongSwan 2.8.5
    cpe:2.3:a:strongswan:strongswan:2.8.5
  • StrongSwan strongSwan 2.8.6
    cpe:2.3:a:strongswan:strongswan:2.8.6
  • StrongSwan strongSwan 2.8.7
    cpe:2.3:a:strongswan:strongswan:2.8.7
  • StrongSwan strongSwan 2.8.8
    cpe:2.3:a:strongswan:strongswan:2.8.8
  • StrongSwan strongSwan 2.8.9
    cpe:2.3:a:strongswan:strongswan:2.8.9
  • StrongSwan strongSwan 2.8.10
    cpe:2.3:a:strongswan:strongswan:2.8.10
  • StrongSwan strongSwan 2.8.11
    cpe:2.3:a:strongswan:strongswan:2.8.11
  • StrongSwan strongSwan 4.0.0
    cpe:2.3:a:strongswan:strongswan:4.0.0
  • StrongSwan strongSwan 4.0.1
    cpe:2.3:a:strongswan:strongswan:4.0.1
  • StrongSwan strongSwan 4.0.2
    cpe:2.3:a:strongswan:strongswan:4.0.2
  • StrongSwan strongSwan 4.0.3
    cpe:2.3:a:strongswan:strongswan:4.0.3
  • StrongSwan strongSwan 4.0.4
    cpe:2.3:a:strongswan:strongswan:4.0.4
  • StrongSwan strongSwan 4.0.5
    cpe:2.3:a:strongswan:strongswan:4.0.5
  • StrongSwan strongSwan 4.0.6
    cpe:2.3:a:strongswan:strongswan:4.0.6
  • StrongSwan strongSwan 4.0.7
    cpe:2.3:a:strongswan:strongswan:4.0.7
  • StrongSwan strongSwan 4.1.0
    cpe:2.3:a:strongswan:strongswan:4.1.0
  • StrongSwan strongSwan 4.1.1
    cpe:2.3:a:strongswan:strongswan:4.1.1
  • StrongSwan strongSwan 4.1.2
    cpe:2.3:a:strongswan:strongswan:4.1.2
  • StrongSwan strongSwan 4.1.3
    cpe:2.3:a:strongswan:strongswan:4.1.3
  • StrongSwan strongSwan 4.1.4
    cpe:2.3:a:strongswan:strongswan:4.1.4
  • StrongSwan strongSwan 4.1.5
    cpe:2.3:a:strongswan:strongswan:4.1.5
  • StrongSwan strongSwan 4.1.6
    cpe:2.3:a:strongswan:strongswan:4.1.6
  • StrongSwan strongSwan 4.1.7
    cpe:2.3:a:strongswan:strongswan:4.1.7
  • StrongSwan strongSwan 4.1.8
    cpe:2.3:a:strongswan:strongswan:4.1.8
  • StrongSwan strongSwan 4.1.9
    cpe:2.3:a:strongswan:strongswan:4.1.9
  • StrongSwan strongSwan 4.1.10
    cpe:2.3:a:strongswan:strongswan:4.1.10
  • StrongSwan strongSwan 4.1.11
    cpe:2.3:a:strongswan:strongswan:4.1.11
  • StrongSwan strongSwan 4.2.0
    cpe:2.3:a:strongswan:strongswan:4.2.0
  • StrongSwan strongSwan 4.2.1
    cpe:2.3:a:strongswan:strongswan:4.2.1
  • StrongSwan strongSwan 4.2.2
    cpe:2.3:a:strongswan:strongswan:4.2.2
  • StrongSwan strongSwan 4.2.3
    cpe:2.3:a:strongswan:strongswan:4.2.3
  • StrongSwan strongSwan 4.2.4
    cpe:2.3:a:strongswan:strongswan:4.2.4
  • StrongSwan strongSwan 4.2.5
    cpe:2.3:a:strongswan:strongswan:4.2.5
  • StrongSwan strongSwan 4.2.6
    cpe:2.3:a:strongswan:strongswan:4.2.6
  • StrongSwan strongSwan 4.2.7
    cpe:2.3:a:strongswan:strongswan:4.2.7
  • StrongSwan strongSwan 4.2.8
    cpe:2.3:a:strongswan:strongswan:4.2.8
  • StrongSwan strongSwan 4.2.9
    cpe:2.3:a:strongswan:strongswan:4.2.9
  • StrongSwan strongSwan 4.2.10
    cpe:2.3:a:strongswan:strongswan:4.2.10
  • StrongSwan strongSwan 4.2.11
    cpe:2.3:a:strongswan:strongswan:4.2.11
  • StrongSwan strongSwan 4.2.12
    cpe:2.3:a:strongswan:strongswan:4.2.12
  • StrongSwan strongSwan 4.2.13
    cpe:2.3:a:strongswan:strongswan:4.2.13
  • StrongSwan strongSwan 4.2.14
    cpe:2.3:a:strongswan:strongswan:4.2.14
  • StrongSwan strongSwan 4.2.15
    cpe:2.3:a:strongswan:strongswan:4.2.15
  • StrongSwan strongSwan 4.2.16
    cpe:2.3:a:strongswan:strongswan:4.2.16
  • StrongSwan strongSwan 4.3.0
    cpe:2.3:a:strongswan:strongswan:4.3.0
  • StrongSwan strongSwan 4.3.1
    cpe:2.3:a:strongswan:strongswan:4.3.1
  • StrongSwan strongSwan 4.3.2
    cpe:2.3:a:strongswan:strongswan:4.3.2
  • StrongSwan strongSwan 4.3.3
    cpe:2.3:a:strongswan:strongswan:4.3.3
  • StrongSwan strongSwan 4.3.4
    cpe:2.3:a:strongswan:strongswan:4.3.4
  • StrongSwan 4.3.5
    cpe:2.3:a:strongswan:strongswan:4.3.5
  • StrongSwan 4.3.6
    cpe:2.3:a:strongswan:strongswan:4.3.6
  • StrongSwan 4.3.7
    cpe:2.3:a:strongswan:strongswan:4.3.7
  • StrongSwan 4.4.0
    cpe:2.3:a:strongswan:strongswan:4.4.0
  • StrongSwan strongSwan 4.4.1
    cpe:2.3:a:strongswan:strongswan:4.4.1
  • StrongSwan strongSwan 4.5.0
    cpe:2.3:a:strongswan:strongswan:4.5.0
  • StrongSwan strongSwan 4.5.1
    cpe:2.3:a:strongswan:strongswan:4.5.1
  • StrongSwan strongSwan 4.5.2
    cpe:2.3:a:strongswan:strongswan:4.5.2
  • StrongSwan strongSwan 4.5.3
    cpe:2.3:a:strongswan:strongswan:4.5.3
  • StrongSwan strongSwan 4.6.0
    cpe:2.3:a:strongswan:strongswan:4.6.0
  • StrongSwan strongSwan 4.6.1
    cpe:2.3:a:strongswan:strongswan:4.6.1
  • StrongSwan strongSwan 4.6.2
    cpe:2.3:a:strongswan:strongswan:4.6.2
  • StrongSwan strongSwan 4.6.3
    cpe:2.3:a:strongswan:strongswan:4.6.3
  • StrongSwan 4.6.4
    cpe:2.3:a:strongswan:strongswan:4.6.4
  • StrongSwan 5.0.0
    cpe:2.3:a:strongswan:strongswan:5.0.0
  • StrongSwan 5.0.1
    cpe:2.3:a:strongswan:strongswan:5.0.1
  • StrongSwan 5.0.2
    cpe:2.3:a:strongswan:strongswan:5.0.2
  • StrongSwan 5.0.3
    cpe:2.3:a:strongswan:strongswan:5.0.3
  • StrongSwan 5.0.4
    cpe:2.3:a:strongswan:strongswan:5.0.4
  • StrongSwan strongSwan 5.1.0
    cpe:2.3:a:strongswan:strongswan:5.1.0
  • StrongSwan strongSwan 5.1.1
    cpe:2.3:a:strongswan:strongswan:5.1.1
  • StrongSwan strongSwan 5.1.2
    cpe:2.3:a:strongswan:strongswan:5.1.2
  • StrongSwan strongSwan 5.1.3
    cpe:2.3:a:strongswan:strongswan:5.1.3
  • StrongSwan 5.2.0
    cpe:2.3:a:strongswan:strongswan:5.2.0
  • strongSwan 5.2.1
    cpe:2.3:a:strongswan:strongswan:5.2.1
  • strongSwan 5.2.2
    cpe:2.3:a:strongswan:strongswan:5.2.2
  • strongSwan 5.2.3
    cpe:2.3:a:strongswan:strongswan:5.2.3
  • strongSwan 5.3.0
    cpe:2.3:a:strongswan:strongswan:5.3.0
  • strongSwan 5.3.1
    cpe:2.3:a:strongswan:strongswan:5.3.1
  • StrongSwan strongSwan 5.3.2
    cpe:2.3:a:strongswan:strongswan:5.3.2
  • StrongSwan strongSwan 5.3.3
    cpe:2.3:a:strongswan:strongswan:5.3.3
  • strongSwan 5.3.4
    cpe:2.3:a:strongswan:strongswan:5.3.4
  • strongSwan 5.3.5
    cpe:2.3:a:strongswan:strongswan:5.3.5
  • strongSwan 5.4.0
    cpe:2.3:a:strongswan:strongswan:5.4.0
  • strongSwan 5.5.0
    cpe:2.3:a:strongswan:strongswan:5.5.0
  • strongSwan 5.5.1
    cpe:2.3:a:strongswan:strongswan:5.5.1
  • strongSwan 5.5.2
    cpe:2.3:a:strongswan:strongswan:5.5.2
  • strongSwan 5.5.3
    cpe:2.3:a:strongswan:strongswan:5.5.3
  • strongSwan 5.6.0
    cpe:2.3:a:strongswan:strongswan:5.6.0
  • strongSwan 5.6.1
    cpe:2.3:a:strongswan:strongswan:5.6.1
  • strongSwan 5.6.2
    cpe:2.3:a:strongswan:strongswan:5.6.2
  • Debian Linux 8.0 (Jessie)
    cpe:2.3:o:debian:debian_linux:8.0
  • Debian Linux 9.0
    cpe:2.3:o:debian:debian_linux:9.0
  • Canonical Ubuntu Linux 14.04 LTS (Long-Term Support)
    cpe:2.3:o:canonical:ubuntu_linux:14.04:-:-:-:lts
  • Canonical Ubuntu Linux 16.04 LTS (Long-Term Support)
    cpe:2.3:o:canonical:ubuntu_linux:16.04:-:-:-:lts
  • Canonical Ubuntu Linux 18.04 LTS Edition
    cpe:2.3:o:canonical:ubuntu_linux:18.04:-:-:-:lts
CVSS
Base: 4.0
Impact:
Exploitability:
CWE CWE-119
CAPEC
  • Buffer Overflow via Environment Variables
    This attack pattern involves causing a buffer overflow through manipulation of environment variables. Once the attacker finds that they can modify an environment variable, they may try to overflow associated buffers. This attack leverages implicit trust often placed in environment variables.
  • Overflow Buffers
    Buffer Overflow attacks target improper or missing bounds checking on buffer operations, typically triggered by input injected by an attacker. As a consequence, an attacker is able to write past the boundaries of allocated buffer regions in memory, causing a program crash or potentially redirection of execution as per the attackers' choice.
  • Client-side Injection-induced Buffer Overflow
    This type of attack exploits a buffer overflow vulnerability in targeted client software through injection of malicious content from a custom-built hostile service.
  • Filter Failure through Buffer Overflow
    In this attack, the idea is to cause an active filter to fail by causing an oversized transaction. An attacker may try to feed overly long input strings to the program in an attempt to overwhelm the filter (by causing a buffer overflow) and hoping that the filter does not fail securely (i.e. the user input is let into the system unfiltered).
  • MIME Conversion
    An attacker exploits a weakness in the MIME conversion routine to cause a buffer overflow and gain control over the mail server machine. The MIME system is designed to allow various different information formats to be interpreted and sent via e-mail. Attack points exist when data are converted to MIME compatible format and back.
  • Overflow Binary Resource File
    An attack of this type exploits a buffer overflow vulnerability in the handling of binary resources. Binary resources may include music files like MP3, image files like JPEG files, and any other binary file. These attacks may pass unnoticed to the client machine through normal usage of files, such as a browser loading a seemingly innocent JPEG file. This can allow the attacker access to the execution stack and execute arbitrary code in the target process. This attack pattern is a variant of standard buffer overflow attacks using an unexpected vector (binary files) to wrap its attack and open up a new attack vector. The attacker is required to either directly serve the binary content to the victim, or place it in a locale like a MP3 sharing application, for the victim to download. The attacker then is notified upon the download or otherwise locates the vulnerability opened up by the buffer overflow.
  • Buffer Overflow via Symbolic Links
    This type of attack leverages the use of symbolic links to cause buffer overflows. An attacker can try to create or manipulate a symbolic link file such that its contents result in out of bounds data. When the target software processes the symbolic link file, it could potentially overflow internal buffers with insufficient bounds checking.
  • Overflow Variables and Tags
    This type of attack leverages the use of tags or variables from a formatted configuration data to cause buffer overflow. The attacker crafts a malicious HTML page or configuration file that includes oversized strings, thus causing an overflow.
  • Buffer Overflow via Parameter Expansion
    In this attack, the target software is given input that the attacker knows will be modified and expanded in size during processing. This attack relies on the target software failing to anticipate that the expanded data may exceed some internal limit, thereby creating a buffer overflow.
  • Buffer Overflow in an API Call
    This attack targets libraries or shared code modules which are vulnerable to buffer overflow attacks. An attacker who has access to an API may try to embed malicious code in the API function call and exploit a buffer overflow vulnerability in the function's implementation. All clients that make use of the code library thus become vulnerable by association. This has a very broad effect on security across a system, usually affecting more than one software process.
  • Buffer Overflow in Local Command-Line Utilities
    This attack targets command-line utilities available in a number of shells. An attacker can leverage a vulnerability found in a command-line utility to escalate privilege to root.
nessus via4
  • NASL family Ubuntu Local Security Checks
    NASL id UBUNTU_USN-3771-1.NASL
    description It was discovered that strongSwan incorrectly handled IKEv2 key derivation. A remote attacker could possibly use this issue to cause strongSwan to crash, resulting in a denial of service. (CVE-2018-10811) Sze Yiu Chau discovered that strongSwan incorrectly handled parsing OIDs in the gmp plugin. A remote attacker could possibly use this issue to bypass authorization. (CVE-2018-16151) Sze Yiu Chau discovered that strongSwan incorrectly handled certain parameters fields in the gmp plugin. A remote attacker could possibly use this issue to bypass authorization. (CVE-2018-16152) It was discovered that strongSwan incorrectly handled the stroke plugin. A local administrator could use this issue to cause a denial of service, or possibly execute arbitrary code. (CVE-2018-5388). Note that Tenable Network Security has extracted the preceding description block directly from the Ubuntu security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.
    last seen 2019-02-21
    modified 2018-12-01
    plugin id 117805
    published 2018-09-27
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=117805
    title Ubuntu 14.04 LTS / 16.04 LTS / 18.04 LTS : strongswan vulnerabilities (USN-3771-1)
  • NASL family PhotonOS Local Security Checks
    NASL id PHOTONOS_PHSA-2018-2_0-0075_STRONGSWAN.NASL
    description An update of the strongswan package has been released.
    last seen 2019-02-08
    modified 2019-02-07
    plugin id 121970
    published 2019-02-07
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=121970
    title Photon OS 2.0: Strongswan PHSA-2018-2.0-0075
  • NASL family FreeBSD Local Security Checks
    NASL id FREEBSD_PKG_7FC3E82764A511E8AEDB00224D821998.NASL
    description strongSwan security team reports : - A denial-of-service vulnerability in the IKEv2 key derivation was fixed if the openssl plugin is used in FIPS mode and HMAC-MD5 is negotiated as PRF (which is not FIPS-compliant). So this should only affect very specific setups, but in such configurations all strongSwan versions since 5.0.1 may be affected. - A denial-of-service vulnerability in the stroke plugin was fixed. When reading a message from the socket the plugin did not check the received length. Unless a group is configured, root privileges are required to access that socket, so in the default configuration this shouldn't be an issue, but all strongSwan versions may be affected.
    last seen 2019-02-21
    modified 2018-11-10
    plugin id 110274
    published 2018-06-01
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=110274
    title FreeBSD : strongswan -- Fix Denial-of-Service Vulnerability strongSwan (CVE-2018-10811, CVE-2018-5388) (7fc3e827-64a5-11e8-aedb-00224d821998)
  • NASL family Gentoo Local Security Checks
    NASL id GENTOO_GLSA-201811-16.NASL
    description The remote host is affected by the vulnerability described in GLSA-201811-16 (strongSwan: Multiple vulnerabilities) Multiple vulnerabilities have been discovered in strongSwan. Please review the CVE identifiers referenced below for details. Impact : A remote attacker could cause a Denial of Service condition or impersonate a user. Workaround : There is no known workaround at this time.
    last seen 2019-02-21
    modified 2018-11-27
    plugin id 119161
    published 2018-11-27
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=119161
    title GLSA-201811-16 : strongSwan: Multiple vulnerabilities
  • NASL family PhotonOS Local Security Checks
    NASL id PHOTONOS_PHSA-2018-2_0-0075.NASL
    description An update of 'libmspack', 'strongswan' packages of Photon OS has been released.
    last seen 2019-02-21
    modified 2019-02-07
    plugin id 111959
    published 2018-08-17
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=111959
    title Photon OS 2.0: Libmspack / Strongswan PHSA-2018-2.0-0075 (deprecated)
  • NASL family PhotonOS Local Security Checks
    NASL id PHOTONOS_PHSA-2018-1_0-0164.NASL
    description An update of 'ncurses', 'strongswan' packages of Photon OS has been released.
    last seen 2019-02-21
    modified 2019-02-07
    plugin id 111944
    published 2018-08-17
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=111944
    title Photon OS 1.0: Ncurses / Strongswan PHSA-2018-1.0-0164 (deprecated)
  • NASL family Fedora Local Security Checks
    NASL id FEDORA_2018-3731A89E20.NASL
    description Resolves rhbz#1581868 CVE-2018-5388 strongswan: buffer underflow in stroke_socket.c Note that Tenable Network Security has extracted the preceding description block directly from the Fedora update system website. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.
    last seen 2019-02-21
    modified 2019-01-03
    plugin id 120348
    published 2019-01-03
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=120348
    title Fedora 28 : strongswan (2018-3731a89e20)
  • NASL family PhotonOS Local Security Checks
    NASL id PHOTONOS_PHSA-2018-1_0-0164_STRONGSWAN.NASL
    description An update of the strongswan package has been released.
    last seen 2019-02-08
    modified 2019-02-07
    plugin id 121859
    published 2019-02-07
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=121859
    title Photon OS 1.0: Strongswan PHSA-2018-1.0-0164
  • NASL family Debian Local Security Checks
    NASL id DEBIAN_DSA-4229.NASL
    description Two vulnerabilities were discovered in strongSwan, an IKE/IPsec suite. - CVE-2018-5388 The stroke plugin did not verify the message length when reading from its control socket. This vulnerability could lead to denial of service. On Debian write access to the socket requires root permission on default configuration. - CVE-2018-10811 A missing variable initialization in IKEv2 key derivation could lead to a denial of service (crash of the charon IKE daemon) if the openssl plugin is used in FIPS mode and the negotiated PRF is HMAC-MD5.
    last seen 2019-02-21
    modified 2018-11-13
    plugin id 110570
    published 2018-06-18
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=110570
    title Debian DSA-4229-1 : strongswan - security update
  • NASL family Fedora Local Security Checks
    NASL id FEDORA_2018-BAB8CABE2A.NASL
    description Resolves rhbz#1581868 CVE-2018-5388 strongswan: buffer underflow in stroke_socket.c Note that Tenable Network Security has extracted the preceding description block directly from the Fedora update system website. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.
    last seen 2019-02-21
    modified 2018-09-05
    plugin id 110302
    published 2018-06-04
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=110302
    title Fedora 27 : strongswan (2018-bab8cabe2a)
refmap via4
bid 104263
cert-vn VU#338343
confirm https://git.strongswan.org/?p=strongswan.git;a=commitdiff;h=0acd1ab4
debian DSA-4229
gentoo GLSA-201811-16
ubuntu USN-3771-1
Last major update 31-05-2018 - 09:29
Published 31-05-2018 - 09:29
Last modified 05-03-2019 - 11:53
Back to Top