- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Gentoo Linux Security Advisory                           GLSA 202405-06
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                                           https://security.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.

Affected packages
=================

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

Description
===========

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

Impact
======

Please review the referenced CVE identifiers for details.

Workaround
==========

There is no known workaround at this time.

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

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.

License
=======

Copyright 2024 Gentoo Foundation, Inc; referenced text
belongs to its owner(s).

The contents of this document are licensed under the
Creative Commons - Attribution / Share Alike license.

https://creativecommons.org/licenses/by-sa/2.5

Gentoo: GLSA-202405-06: mujs: Security Advisory Updates

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

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
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.

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.

Related News