idn2_to_ascii_4i in lib/lookup.c in GNU libidn2 before 2.1.1 has a heap-based buffer overflow via a long domain string.

According to the version of the libidn2 package installed, the EulerOS Virtualization for ARM 64 installation on the remote host is affected by the following vulnerability :

  - idn2_to_ascii_4i in lib/lookup.c in GNU libidn2 before     2.1.1 has a heap-based buffer overflow via a long     domain string.(CVE-2019-18224)

Note that Tenable Network Security has extracted the preceding description block directly from the EulerOS security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

The remote host is affected by the vulnerability described in GLSA-202003-63 (GNU IDN Library 2: Multiple vulnerabilities)

    Multiple vulnerabilities have been discovered in GNU IDN Library 2.
      Please review the CVE identifiers referenced below for details.
  Impact :

    A remote attacker could send specially crafted input, possibly resulting       in execution of arbitrary code with the privileges of the process,       impersonation of domains or a Denial of Service condition.
  Workaround :

    There is no known workaround at this time.

A heap-based buffer overflow vulnerability was discovered in the idn2_to_ascii_4i() function in libidn2, the GNU library for Internationalized Domain Names (IDNs), which could result in denial of service, or the execution of arbitrary code when processing a long domain string.

idn2_to_ascii_4i in lib/lookup.c in GNU libidn2 before 2.1.1 has a heap-based buffer overflow via a long domain string. (CVE-2019-18224)

GNU libidn2 before 2.2.0 fails to perform the roundtrip checks specified in RFC3490 Section 4.2 when converting A-labels to U-labels.
This makes it possible in some circumstances for one domain to impersonate another. By creating a malicious domain that matches a target domain except for the inclusion of certain punycoded Unicode characters (that would be discarded when converted first to a Unicode label and then back to an ASCII label), arbitrary domains can be impersonated.(CVE-2019-12290)

heap-based buffer overflow in idn2_to_ascii_4i in lib/lookup.c idn2_to_ascii_4i in lib/lookup.c in GNU libidn2 before 2.1.1 has a heap-based buffer overflow via a long domain string.(CVE-2019-18224)

This update for libidn2 to version 2.2.0 fixes the following issues :

  - CVE-2019-12290: Fixed an improper round-trip check when     converting A-labels to U-labels (bsc#1154884).

  - CVE-2019-18224: Fixed a heap-based buffer overflow that     was caused by long domain strings (bsc#1154887).

This update was imported from the SUSE:SLE-15:Update update project.

This update for libidn2 to version 2.2.0 fixes the following issues :

CVE-2019-12290: Fixed an improper round-trip check when converting A-labels to U-labels (bsc#1154884).

CVE-2019-18224: Fixed a heap-based buffer overflow that was caused by long domain strings (bsc#1154887).

Note that Tenable Network Security has extracted the preceding description block directly from the SUSE security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

Libidn 2.2.0 (released 2019-05-23) ==================================

  - Perform A-Label roundtrip for lookup functions by     default

  - Stricter check of input to punycode decoder

  - Fix punycode decoding with no ASCII chars but given     delimiter

  - Fix `idn2 --no-tr64` (was a no-op)

  - Allow `_` as a basic code point in domain labels

  - Fail building documentation if `ronn` isn't installed

  - git tag changed to reflect https://semver.org/

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.

It was discovered that Libidn2 incorrectly handled certain inputs. A attacker could possibly use this issue to impersonate domains.
(CVE-2019-12290)

It was discovered that Libidn2 incorrectly handled certain inputs. An attacker could possibly use this issue to execute arbitrary code.
(CVE-2019-18224).

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.

ID	Name	Product	Family	Severity
140346	EulerOS Virtualization for ARM 64 3.0.2.0 : libidn2 (EulerOS-SA-2020-1976)	Nessus	Huawei Local Security Checks	critical
135018	GLSA-202003-63 : GNU IDN Library 2: Multiple vulnerabilities	Nessus	Gentoo Local Security Checks	critical
133416	Debian DSA-4613-1 : libidn2 - security update	Nessus	Debian Local Security Checks	critical
132322	Amazon Linux AMI : libidn2 (ALAS-2019-1327)	Nessus	Amazon Linux Local Security Checks	critical
132261	Amazon Linux 2 : libidn2 (ALAS-2019-1373)	Nessus	Amazon Linux Local Security Checks	critical
131684	openSUSE Security Update : libidn2 (openSUSE-2019-2613)	Nessus	SuSE Local Security Checks	critical
131682	openSUSE Security Update : libidn2 (openSUSE-2019-2611)	Nessus	SuSE Local Security Checks	critical
131548	SUSE SLED15 / SLES15 Security Update : libidn2 (SUSE-SU-2019:3086-1)	Nessus	SuSE Local Security Checks	critical
130492	Fedora 30 : mingw-libidn2 (2019-d3221d69e0)	Nessus	Fedora Local Security Checks	critical
130489	Fedora 29 : mingw-libidn2 (2019-a8d35fcf7c)	Nessus	Fedora Local Security Checks	critical
130393	Ubuntu 18.04 LTS : Libidn2 vulnerabilities (USN-4168-1)	Nessus	Ubuntu Local Security Checks	critical

Detections

Analytics

CVE-2019-18224

critical

Tenable Plugins

critical

critical

critical

critical

critical

critical

critical

critical

critical

critical

critical