CVE Vulnerabilities

CVE-2018-5389

Weak Password Requirements

Published: Sep 06, 2018 | Modified: Nov 21, 2024
CVSS 3.x
5.9
MEDIUM
Source:
NVD
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
CVSS 2.x
4.3 MEDIUM
AV:N/AC:M/Au:N/C:P/I:N/A:N
RedHat/V2
RedHat/V3
5.9 MODERATE
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
Ubuntu
LOW
root.io logo minimus.io logo echo.ai logo

The Internet Key Exchange v1 main mode is vulnerable to offline dictionary or brute force attacks. Reusing a key pair across different versions and modes of IKE could lead to cross-protocol authentication bypasses. It is well known, that the aggressive mode of IKEv1 PSK is vulnerable to offline dictionary or brute force attacks. For the main mode, however, only an online attack against PSK authentication was thought to be feasible. This vulnerability could allow an attacker to recover a weak Pre-Shared Key or enable the impersonation of a victim host or network.

Weakness

The product does not require that users should have strong passwords.

Affected Software

NameVendorStart VersionEnd Version
Internet_key_exchangeIetf1.0 (including)1.0 (including)
Ipsec-toolsUbuntubionic*
Ipsec-toolsUbuntucosmic*
Ipsec-toolsUbuntudisco*
Ipsec-toolsUbuntuesm-apps/bionic*
Ipsec-toolsUbuntuesm-apps/xenial*
Ipsec-toolsUbuntuprecise/esm*
Ipsec-toolsUbuntutrusty*
Ipsec-toolsUbuntuxenial*
IsakmpdUbuntubionic*
IsakmpdUbuntucosmic*
IsakmpdUbuntudevel*
IsakmpdUbuntudisco*
IsakmpdUbuntueoan*
IsakmpdUbuntuesm-apps/bionic*
IsakmpdUbuntuesm-apps/focal*
IsakmpdUbuntuesm-apps/jammy*
IsakmpdUbuntuesm-apps/xenial*
IsakmpdUbuntufocal*
IsakmpdUbuntugroovy*
IsakmpdUbuntuhirsute*
IsakmpdUbuntuimpish*
IsakmpdUbuntujammy*
IsakmpdUbuntutrusty*
IsakmpdUbuntuxenial*
LibreswanUbuntubionic*
LibreswanUbuntucosmic*
LibreswanUbuntudevel*
LibreswanUbuntudisco*
LibreswanUbuntueoan*
LibreswanUbuntuesm-apps/bionic*
LibreswanUbuntuesm-apps/focal*
LibreswanUbuntuesm-apps/jammy*
LibreswanUbuntufocal*
LibreswanUbuntugroovy*
LibreswanUbuntuhirsute*
LibreswanUbuntuimpish*
LibreswanUbuntujammy*
StrongswanUbuntubionic*
StrongswanUbuntucosmic*
StrongswanUbuntudevel*
StrongswanUbuntudisco*
StrongswanUbuntueoan*
StrongswanUbuntuesm-infra-legacy/trusty*
StrongswanUbuntuesm-infra/bionic*
StrongswanUbuntuesm-infra/focal*
StrongswanUbuntuesm-infra/xenial*
StrongswanUbuntufips-updates/bionic*
StrongswanUbuntufips-updates/focal*
StrongswanUbuntufips-updates/xenial*
StrongswanUbuntufips/bionic*
StrongswanUbuntufips/focal*
StrongswanUbuntufips/xenial*
StrongswanUbuntufocal*
StrongswanUbuntugroovy*
StrongswanUbuntuhirsute*
StrongswanUbuntuimpish*
StrongswanUbuntujammy*
StrongswanUbuntutrusty*
StrongswanUbuntutrusty/esm*
StrongswanUbuntuxenial*

Potential Mitigations

  • A product’s design should require adherance to an appropriate password policy. Specific password requirements depend strongly on contextual factors, but it is recommended to contain the following attributes:

  • Depending on the threat model, the password policy may include several additional attributes.

  • See NIST 800-63B [REF-1053] for further information on password requirements.

References