Alerts This Week
Warning Icon 1 714
Alerts This Week
Warning Icon 1 714

Gentoo: GLSA 202003-41 Normal: Heap Overflow Risk in GNU FriBidi

gentoo
Calendar Grey March 19, 2020
Dist Gentoo Esm H88
Investigate Gentoo's GLSA 202003-41 concerning a critical heap overflow vulnerability within GNU FriBidi, which poses a risk for potential remote code execution.
A heap-based buffer overflow in GNU FriBidi might allow remote attackers to execute arbitrary code.

Summary

A heap-based buffer overflow vulnerability was found in GNU FriBidi.

Resolution

All FriBidi users should upgrade to the latest version: # emerge --sync # emerge --ask --oneshot --verbose ">=dev-libs/fribidi-1.0.8"

References

[ 1 ] CVE-2019-18397 https://nvd.nist.gov/vuln/detail/CVE-2019-18397

Availability

This GLSA and any updates to it are available for viewing at the Gentoo Security Website: https://security.gentoo.org/glsa/202003-41
style>.gentoo_availability{display:block;}

Concerns

Security is a primary focus of Gentoo Linux and ensuring the confidentiality and security of our users' machines is of utmost importance to us. Any security concerns should be addressed to security@gentoo.org or alternatively, you may file a bug at https://bugs.gentoo.org.

Severity: Normal
Title: GNU FriBidi: Heap-based buffer overflow
Date: March 19, 2020
Bugs: #699338
ID: 202003-41

Synopsis

A heap-based buffer overflow in GNU FriBidi might allow remote attackers to execute arbitrary code.

Background

The Free Implementation of the Unicode Bidirectional Algorithm.

Get the latest News and Insights

Get the latest Linux and open source security news straight to your inbox.

Affected Packages

------------------------------------------------------------------- Package / Vulnerable / Unaffected ------------------------------------------------------------------- 1 dev-libs/fribidi < 1.0.8 >= 1.0.8

Impact

===== A remote attacker could possibly cause a memory corruption, execute arbitrary code with the privileges of the process or cause a Denial of Service condition.

Workaround

There is no known workaround at this time.

Your message here