Alerts This Week
Warning Icon 1 1,146
Alerts This Week
Warning Icon 1 1,146

Fedora: FEDORA-202405-07 Moderate Risk: libxyz Unauthorized Access

gentoo
Calendar Grey May 4, 2024
Dist Gentoo Esm H88
Several security flaws in mujs could result in unauthorized remote code execution. To reduce potential threats, please upgrade to version 1.3.2.
Multiple vulnerabilities have been discovered in mujs, the worst of which could lead to remote code execution.

Summary

Multiple vulnerabilities have been discovered in mujs. Please review the CVE identifiers referenced below for details.

Resolution

All mujs users should upgrade to the latest version:
# emerge --sync # emerge --ask --oneshot --verbose ">=dev-lang/mujs-1.3.2"

References

[ 1 ] CVE-2021-45005 https://nvd.nist.gov/vuln/detail/CVE-2021-45005 [ 2 ] CVE-2022-30974 https://nvd.nist.gov/vuln/detail/CVE-2022-30974 [ 3 ] CVE-2022-30975 https://nvd.nist.gov/vuln/detail/CVE-2022-30975 [ 4 ] CVE-2022-44789 https://nvd.nist.gov/vuln/detail/CVE-2022-44789

Availability

This GLSA and any updates to it are available for viewing at the Gentoo Security Website:
https://security.gentoo.org/glsa/202405-06
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: mujs: Multiple Vulnerabilities
Date: May 04, 2024
Bugs: #833453, #845399, #882775
ID: 202405-06

Synopsis

Multiple vulnerabilities have been discovered in mujs, the worst of which could lead to remote code execution.

Background

mujs is an embeddable Javascript interpreter in C.

Get the latest News and Insights

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

Affected Packages

Package Vulnerable Unaffected ------------- ------------ ------------ dev-lang/mujs < 1.3.2 >= 1.3.2

Impact

Please review the referenced CVE identifiers for details.

Workaround

There is no known workaround at this time.

Your message here