- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Gentoo Linux Security Advisory                           GLSA 202107-50
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                                           https://security.gentoo.org/
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

 Severity: High
    Title: Singularity: Remote code execution
     Date: July 22, 2021
     Bugs: #792465
       ID: 202107-50

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Synopsis
=======
A vulnerability in Singularity could result in remote code execution.

Background
=========
Singularity is the container platform for performance sensitive
workloads.

Affected packages
================
    -------------------------------------------------------------------
     Package              /     Vulnerable     /            Unaffected
    -------------------------------------------------------------------
  1  sys-cluster/singularity      < 3.7.4                    >= 3.7.4 

Description
==========
Singularity always uses the default remote endpoint,
'cloud.syslabs.io', for action commands using the 'library://' URI
rather than the configured remote endpoint.

Impact
=====
An attacker that that can push a malicious container to the default
remote endpoint could execute code on hosts that fetch the container.

Workaround
=========
There is no known workaround at this time.

Resolution
=========
All Singularity users should upgrade to the latest version:

  # emerge --sync
  # emerge --ask --oneshot --verbose ">=sys-cluster/singularity-3.7.4"

References
=========
[ 1 ] CVE-2021-32635
      https://nvd.nist.gov/vuln/detail/CVE-2021-32635

Availability
===========
This GLSA and any updates to it are available for viewing at
the Gentoo Security Website:

 https://security.gentoo.org/glsa/202107-50

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 2021 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-202107-50: Singularity: Remote code execution

A vulnerability in Singularity could result in remote code execution.

Summary

Singularity always uses the default remote endpoint, 'cloud.syslabs.io', for action commands using the 'library://' URI rather than the configured remote endpoint.

Resolution

All Singularity users should upgrade to the latest version: # emerge --sync # emerge --ask --oneshot --verbose ">=sys-cluster/singularity-3.7.4"

References

[ 1 ] CVE-2021-32635 https://nvd.nist.gov/vuln/detail/CVE-2021-32635

Availability

This GLSA and any updates to it are available for viewing at the Gentoo Security Website: https://security.gentoo.org/glsa/202107-50

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: High
Title: Singularity: Remote code execution
Date: July 22, 2021
Bugs: #792465
ID: 202107-50

Synopsis

A vulnerability in Singularity could result in remote code execution.

Background

Singularity is the container platform for performance sensitive workloads.

Affected Packages

------------------------------------------------------------------- Package / Vulnerable / Unaffected ------------------------------------------------------------------- 1 sys-cluster/singularity < 3.7.4 >= 3.7.4

Impact

===== An attacker that that can push a malicious container to the default remote endpoint could execute code on hosts that fetch the container.

Workaround

There is no known workaround at this time.

Related News