opensuse-su-2019:2288-1
Vulnerability from csaf_opensuse
Published
2019-10-07 15:31
Modified
2019-10-07 15:31
Summary
Security update for singularity
Notes
Title of the patch
Security update for singularity
Description of the patch
This update for singularity fixes the following issues:
singularity was updated to version 3.4.1:
This point release addresses the following issues:
- Fixes an issue where a PID namespace was always being used
- Fixes compilation on non 64-bit architectures
- Allows fakeroot builds for zypper, pacstrap, and debootstrap
- Correctly detects seccomp on OpenSUSE
- Honors GO_MODFLAGS properly in the mconfig generated makefile
- Passes the Mac hostname to the VM in MacOS Singularity builds
- Handles temporary EAGAIN failures when setting up loop devices on
recent kernels.
New version 3.4.0. Many changes since 3.2.1, for the full changelog
please read CHANGELOG.md
Update to version 3.2.1:
This point release fixes the following bugs:
- Allows users to join instances with non-suid workflow
- Removes false warning when seccomp is disabled on the host
- Fixes an issue in the terminal when piping output to commands
- Binds NVIDIA persistenced socket when `--nv` is invoked
Improve integration with SUSE Products: add support to create Singularity
images with SLE.
* Newer SUSE versions use a different path for the RPM database.
* When the installation succeeds by an installation scriptlet fails
zypper returns error code 107. Don't treat this as an error.
* In order to specify a repository GPG key, add support for
multi line variables.
* In order to specify a list of additional repos, add support
to 'indexed' variables.
* Improve handling of SUSE repositires:
- For SLE, use SUSEConnect to get all product repos.
- Allow to specify a repository GPG key.
- Allow to specify additional installation repositories.
- Add group 'singularity', fix ownerships.
Updated to singularity v3.2.0
* CVE-2019-11328: Instance files are now stored in user's home directory for privacy and
many checks have been added to ensure that a user can't manipulate files
to change `starter-suid` behavior when instances are joined (many thanks
to Matthias Gerstner from the SUSE security team for finding and securely
reporting this vulnerability) (boo#1128598)
* New features / functionalities
- Introduced a new basic framework for creating and managing plugins
- Added the ability to create containers through multi-stage builds
- Created the concept of a Sylabs Cloud 'remote' endpoint and added the
ability for users and admins to set them through CLI and conf files
- Added caching for images from Singularity Hub
- Made it possible to compile Singularity outside of `$GOPATH`
- Added a json partition to SIF files for OCI configuration when building
from an OCI source
- Full integration with Singularity desktop for MacOS code base
* New Commands
- Introduced the `plugin` command group for creating and managing plugins.
* Introduced the `remote` command group to support management of Singularity
endpoints.
* Added to the `key` command group to improve PGP key management.
* Added the `Stage: <name>` keyword to the definition file header and the
`from <stage name>` option/argument pair to the `%files` section to
support multistage builds
* Deprecated / removed commands
- The `--token/-t` option has been deprecated in favor of the `singularity
remote` command group
* Changed defaults / behaviors
- Ask to confirm password on a newly generated PGP key
- Prompt to push a key to the KeyStore when generated
- Refuse to push an unsigned container unless overridden with
`--allow-unauthenticated/-U` option
- Warn and prompt when pulling an unsigned container without the
`--allow-unauthenticated/-U` option
For more information check:
https://github.com/sylabs/singularity/blob/release-3.2/CHANGELOG.md
Updated to singularity v3.1.1:
* New Commands
- New hidden `buildcfg` command to display compile-time parameters
- Added support for `LDFLAGS`, `CFLAGS`, `CGO_` variables in build system
- Added `--nocolor` flag to Singularity client to disable color in logging
* Removed Commands
- `singularity capability <add/drop> --desc` has been removed
- `singularity capability list <--all/--group/--user>` flags have all
been removed
* New features / functionalities
- The `--builder` flag to the `build` command implicitly sets `--remote`
- Repeated binds no longer cause Singularity to exit and fail, just warn
instead
- Corrected typos and improved docstrings throughout
- Removed warning when CWD does not exist on the host system
- Added support to spec file for RPM building on SLES 11
Update to singularity 3.1.0 what is reimplementaion in go
so this is a complete new build and just reusing the changelog
entries, following build differences were made to the upstream
spec file
* build position independent executable
* build stripped executable
- Change from /var/singularity to /var/lib/singularity
- Fix warning on bash-completion file about non-executible script.
- Add bash completions directory to file list for suse_version < 1500
to keep the build checker happy.
Patchnames
openSUSE-2019-2288
Terms of use
CSAF 2.0 data is provided by SUSE under the Creative Commons License 4.0 with Attribution (CC-BY-4.0).
{ "document": { "aggregate_severity": { "namespace": "https://www.suse.com/support/security/rating/", "text": "moderate" }, "category": "csaf_security_advisory", "csaf_version": "2.0", "distribution": { "text": "Copyright 2024 SUSE LLC. All rights reserved.", "tlp": { "label": "WHITE", "url": "https://www.first.org/tlp/" } }, "lang": "en", "notes": [ { "category": "summary", "text": "Security update for singularity", "title": "Title of the patch" }, { "category": "description", "text": "This update for singularity fixes the following issues:\n\nsingularity was updated to version 3.4.1:\n\nThis point release addresses the following issues:\n\n- Fixes an issue where a PID namespace was always being used\n- Fixes compilation on non 64-bit architectures\n- Allows fakeroot builds for zypper, pacstrap, and debootstrap\n- Correctly detects seccomp on OpenSUSE\n- Honors GO_MODFLAGS properly in the mconfig generated makefile\n- Passes the Mac hostname to the VM in MacOS Singularity builds\n- Handles temporary EAGAIN failures when setting up loop devices on\nrecent kernels.\n\nNew version 3.4.0. Many changes since 3.2.1, for the full changelog \n please read CHANGELOG.md\n\nUpdate to version 3.2.1:\n\nThis point release fixes the following bugs:\n\n- Allows users to join instances with non-suid workflow\n- Removes false warning when seccomp is disabled on the host\n- Fixes an issue in the terminal when piping output to commands\n- Binds NVIDIA persistenced socket when `--nv` is invoked\n\nImprove integration with SUSE Products: add support to create Singularity\nimages with SLE.\n\n* Newer SUSE versions use a different path for the RPM database.\n* When the installation succeeds by an installation scriptlet fails\n zypper returns error code 107. Don\u0027t treat this as an error.\n* In order to specify a repository GPG key, add support for\n multi line variables.\n* In order to specify a list of additional repos, add support\n to \u0027indexed\u0027 variables.\n* Improve handling of SUSE repositires:\n\n - For SLE, use SUSEConnect to get all product repos.\n - Allow to specify a repository GPG key.\n - Allow to specify additional installation repositories.\n\n- Add group \u0027singularity\u0027, fix ownerships.\n\nUpdated to singularity v3.2.0\n\n* CVE-2019-11328: Instance files are now stored in user\u0027s home directory for privacy and\n many checks have been added to ensure that a user can\u0027t manipulate files\n to change `starter-suid` behavior when instances are joined (many thanks\n to Matthias Gerstner from the SUSE security team for finding and securely\n reporting this vulnerability) (boo#1128598)\n\n* New features / functionalities\n\n - Introduced a new basic framework for creating and managing plugins\n - Added the ability to create containers through multi-stage builds\n - Created the concept of a Sylabs Cloud \u0027remote\u0027 endpoint and added the\n ability for users and admins to set them through CLI and conf files \n - Added caching for images from Singularity Hub\n - Made it possible to compile Singularity outside of `$GOPATH`\n - Added a json partition to SIF files for OCI configuration when building\n from an OCI source\n - Full integration with Singularity desktop for MacOS code base\n\n* New Commands\n\n - Introduced the `plugin` command group for creating and managing plugins.\n\n* Introduced the `remote` command group to support management of Singularity\n endpoints.\n* Added to the `key` command group to improve PGP key management.\n* Added the `Stage: \u003cname\u003e` keyword to the definition file header and the\n `from \u003cstage name\u003e` option/argument pair to the `%files` section to\n support multistage builds\n* Deprecated / removed commands\n\n - The `--token/-t` option has been deprecated in favor of the `singularity\n remote` command group\n\n* Changed defaults / behaviors\n\n - Ask to confirm password on a newly generated PGP key\n - Prompt to push a key to the KeyStore when generated\n - Refuse to push an unsigned container unless overridden with\n `--allow-unauthenticated/-U` option\n - Warn and prompt when pulling an unsigned container without the\n `--allow-unauthenticated/-U` option\nFor more information check:\n https://github.com/sylabs/singularity/blob/release-3.2/CHANGELOG.md\n\nUpdated to singularity v3.1.1:\n\n* New Commands\n\n - New hidden `buildcfg` command to display compile-time parameters \n - Added support for `LDFLAGS`, `CFLAGS`, `CGO_` variables in build system\n - Added `--nocolor` flag to Singularity client to disable color in logging\n\n* Removed Commands\n\n - `singularity capability \u003cadd/drop\u003e --desc` has been removed\n - `singularity capability list \u003c--all/--group/--user\u003e` flags have all\n been removed \n\n* New features / functionalities\n - The `--builder` flag to the `build` command implicitly sets `--remote`\n - Repeated binds no longer cause Singularity to exit and fail, just warn\n instead\n - Corrected typos and improved docstrings throughout\n - Removed warning when CWD does not exist on the host system\n - Added support to spec file for RPM building on SLES 11\n\nUpdate to singularity 3.1.0 what is reimplementaion in go\nso this is a complete new build and just reusing the changelog\nentries, following build differences were made to the upstream\nspec file\n\n* build position independent executable\n* build stripped executable\n\n- Change from /var/singularity to /var/lib/singularity\n- Fix warning on bash-completion file about non-executible script.\n\n- Add bash completions directory to file list for suse_version \u003c 1500\n to keep the build checker happy.\n", "title": "Description of the patch" }, { "category": "details", "text": "openSUSE-2019-2288", "title": "Patchnames" }, { "category": "legal_disclaimer", "text": "CSAF 2.0 data is provided by SUSE under the Creative Commons License 4.0 with Attribution (CC-BY-4.0).", "title": "Terms of use" } ], "publisher": { "category": "vendor", "contact_details": "https://www.suse.com/support/security/contact/", "name": "SUSE Product Security Team", "namespace": "https://www.suse.com/" }, "references": [ { "category": "external", "summary": "SUSE ratings", "url": "https://www.suse.com/support/security/rating/" }, { "category": "self", "summary": "URL of this CSAF notice", "url": "https://ftp.suse.com/pub/projects/security/csaf/opensuse-su-2019_2288-1.json" }, { "category": "self", "summary": "URL for openSUSE-SU-2019:2288-1", "url": "https://lists.opensuse.org/archives/list/security-announce@lists.opensuse.org/thread/IKW24LOLINECHPX4KVSOFZEYFTA7RDEL/#IKW24LOLINECHPX4KVSOFZEYFTA7RDEL" }, { "category": "self", "summary": "E-Mail link for openSUSE-SU-2019:2288-1", "url": "https://lists.opensuse.org/archives/list/security-announce@lists.opensuse.org/thread/IKW24LOLINECHPX4KVSOFZEYFTA7RDEL/#IKW24LOLINECHPX4KVSOFZEYFTA7RDEL" }, { "category": "self", "summary": "SUSE Bug 1125369", "url": "https://bugzilla.suse.com/1125369" }, { "category": "self", "summary": "SUSE Bug 1128598", "url": "https://bugzilla.suse.com/1128598" }, { "category": "self", "summary": "SUSE CVE CVE-2019-11328 page", "url": "https://www.suse.com/security/cve/CVE-2019-11328/" } ], "title": "Security update for singularity", "tracking": { "current_release_date": "2019-10-07T15:31:24Z", "generator": { "date": "2019-10-07T15:31:24Z", "engine": { "name": "cve-database.git:bin/generate-csaf.pl", "version": "1" } }, "id": "openSUSE-SU-2019:2288-1", "initial_release_date": "2019-10-07T15:31:24Z", "revision_history": [ { "date": "2019-10-07T15:31:24Z", "number": "1", "summary": "Current version" } ], "status": "final", "version": "1" } }, "product_tree": { "branches": [ { "branches": [ { "branches": [ { "category": "product_version", "name": "singularity-3.4.1-bp151.3.3.1.aarch64", "product": { "name": "singularity-3.4.1-bp151.3.3.1.aarch64", "product_id": "singularity-3.4.1-bp151.3.3.1.aarch64" } } ], "category": "architecture", "name": "aarch64" }, { "branches": [ { "category": "product_version", "name": "singularity-3.4.1-bp151.3.3.1.ppc64le", "product": { "name": "singularity-3.4.1-bp151.3.3.1.ppc64le", "product_id": "singularity-3.4.1-bp151.3.3.1.ppc64le" } } ], "category": "architecture", "name": "ppc64le" }, { "branches": [ { "category": "product_version", "name": "singularity-3.4.1-bp151.3.3.1.s390x", "product": { "name": "singularity-3.4.1-bp151.3.3.1.s390x", "product_id": "singularity-3.4.1-bp151.3.3.1.s390x" } } ], "category": "architecture", "name": "s390x" }, { "branches": [ { "category": "product_version", "name": "singularity-3.4.1-bp151.3.3.1.x86_64", "product": { "name": "singularity-3.4.1-bp151.3.3.1.x86_64", "product_id": "singularity-3.4.1-bp151.3.3.1.x86_64" } } ], "category": "architecture", "name": "x86_64" }, { "branches": [ { "category": "product_name", "name": "SUSE Package Hub 15", "product": { "name": "SUSE Package Hub 15", "product_id": "SUSE Package Hub 15" } }, { "category": "product_name", "name": "SUSE Package Hub 15 SP1", "product": { "name": "SUSE Package Hub 15 SP1", "product_id": "SUSE Package Hub 15 SP1" } } ], "category": "product_family", "name": "SUSE Linux Enterprise" } ], "category": "vendor", "name": "SUSE" } ], "relationships": [ { "category": "default_component_of", "full_product_name": { "name": "singularity-3.4.1-bp151.3.3.1.aarch64 as component of SUSE Package Hub 15", "product_id": "SUSE Package Hub 15:singularity-3.4.1-bp151.3.3.1.aarch64" }, "product_reference": "singularity-3.4.1-bp151.3.3.1.aarch64", "relates_to_product_reference": "SUSE Package Hub 15" }, { "category": "default_component_of", "full_product_name": { "name": "singularity-3.4.1-bp151.3.3.1.ppc64le as component of SUSE Package Hub 15", "product_id": "SUSE Package Hub 15:singularity-3.4.1-bp151.3.3.1.ppc64le" }, "product_reference": "singularity-3.4.1-bp151.3.3.1.ppc64le", "relates_to_product_reference": "SUSE Package Hub 15" }, { "category": "default_component_of", "full_product_name": { "name": "singularity-3.4.1-bp151.3.3.1.s390x as component of SUSE Package Hub 15", "product_id": "SUSE Package Hub 15:singularity-3.4.1-bp151.3.3.1.s390x" }, "product_reference": "singularity-3.4.1-bp151.3.3.1.s390x", "relates_to_product_reference": "SUSE Package Hub 15" }, { "category": "default_component_of", "full_product_name": { "name": "singularity-3.4.1-bp151.3.3.1.x86_64 as component of SUSE Package Hub 15", "product_id": "SUSE Package Hub 15:singularity-3.4.1-bp151.3.3.1.x86_64" }, "product_reference": "singularity-3.4.1-bp151.3.3.1.x86_64", "relates_to_product_reference": "SUSE Package Hub 15" }, { "category": "default_component_of", "full_product_name": { "name": "singularity-3.4.1-bp151.3.3.1.aarch64 as component of SUSE Package Hub 15 SP1", "product_id": "SUSE Package Hub 15 SP1:singularity-3.4.1-bp151.3.3.1.aarch64" }, "product_reference": "singularity-3.4.1-bp151.3.3.1.aarch64", "relates_to_product_reference": "SUSE Package Hub 15 SP1" }, { "category": "default_component_of", "full_product_name": { "name": "singularity-3.4.1-bp151.3.3.1.ppc64le as component of SUSE Package Hub 15 SP1", "product_id": "SUSE Package Hub 15 SP1:singularity-3.4.1-bp151.3.3.1.ppc64le" }, "product_reference": "singularity-3.4.1-bp151.3.3.1.ppc64le", "relates_to_product_reference": "SUSE Package Hub 15 SP1" }, { "category": "default_component_of", "full_product_name": { "name": "singularity-3.4.1-bp151.3.3.1.s390x as component of SUSE Package Hub 15 SP1", "product_id": "SUSE Package Hub 15 SP1:singularity-3.4.1-bp151.3.3.1.s390x" }, "product_reference": "singularity-3.4.1-bp151.3.3.1.s390x", "relates_to_product_reference": "SUSE Package Hub 15 SP1" }, { "category": "default_component_of", "full_product_name": { "name": "singularity-3.4.1-bp151.3.3.1.x86_64 as component of SUSE Package Hub 15 SP1", "product_id": "SUSE Package Hub 15 SP1:singularity-3.4.1-bp151.3.3.1.x86_64" }, "product_reference": "singularity-3.4.1-bp151.3.3.1.x86_64", "relates_to_product_reference": "SUSE Package Hub 15 SP1" } ] }, "vulnerabilities": [ { "cve": "CVE-2019-11328", "ids": [ { "system_name": "SUSE CVE Page", "text": "https://www.suse.com/security/cve/CVE-2019-11328" } ], "notes": [ { "category": "general", "text": "An issue was discovered in Singularity 3.1.0 to 3.2.0-rc2, a malicious user with local/network access to the host system (e.g. ssh) could exploit this vulnerability due to insecure permissions allowing a user to edit files within `/run/singularity/instances/sing/\u003cuser\u003e/\u003cinstance\u003e`. The manipulation of those files can change the behavior of the starter-suid program when instances are joined resulting in potential privilege escalation on the host.", "title": "CVE description" } ], "product_status": { "recommended": [ "SUSE Package Hub 15 SP1:singularity-3.4.1-bp151.3.3.1.aarch64", "SUSE Package Hub 15 SP1:singularity-3.4.1-bp151.3.3.1.ppc64le", "SUSE Package Hub 15 SP1:singularity-3.4.1-bp151.3.3.1.s390x", "SUSE Package Hub 15 SP1:singularity-3.4.1-bp151.3.3.1.x86_64", "SUSE Package Hub 15:singularity-3.4.1-bp151.3.3.1.aarch64", "SUSE Package Hub 15:singularity-3.4.1-bp151.3.3.1.ppc64le", "SUSE Package Hub 15:singularity-3.4.1-bp151.3.3.1.s390x", "SUSE Package Hub 15:singularity-3.4.1-bp151.3.3.1.x86_64" ] }, "references": [ { "category": "external", "summary": "CVE-2019-11328", "url": "https://www.suse.com/security/cve/CVE-2019-11328" }, { "category": "external", "summary": "SUSE Bug 1128598 for CVE-2019-11328", "url": "https://bugzilla.suse.com/1128598" } ], "remediations": [ { "category": "vendor_fix", "details": "To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or \"zypper patch\".\n", "product_ids": [ "SUSE Package Hub 15 SP1:singularity-3.4.1-bp151.3.3.1.aarch64", "SUSE Package Hub 15 SP1:singularity-3.4.1-bp151.3.3.1.ppc64le", "SUSE Package Hub 15 SP1:singularity-3.4.1-bp151.3.3.1.s390x", "SUSE Package Hub 15 SP1:singularity-3.4.1-bp151.3.3.1.x86_64", "SUSE Package Hub 15:singularity-3.4.1-bp151.3.3.1.aarch64", "SUSE Package Hub 15:singularity-3.4.1-bp151.3.3.1.ppc64le", "SUSE Package Hub 15:singularity-3.4.1-bp151.3.3.1.s390x", "SUSE Package Hub 15:singularity-3.4.1-bp151.3.3.1.x86_64" ] } ], "scores": [ { "cvss_v3": { "baseScore": 8.8, "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H", "version": "3.1" }, "products": [ "SUSE Package Hub 15 SP1:singularity-3.4.1-bp151.3.3.1.aarch64", "SUSE Package Hub 15 SP1:singularity-3.4.1-bp151.3.3.1.ppc64le", "SUSE Package Hub 15 SP1:singularity-3.4.1-bp151.3.3.1.s390x", "SUSE Package Hub 15 SP1:singularity-3.4.1-bp151.3.3.1.x86_64", "SUSE Package Hub 15:singularity-3.4.1-bp151.3.3.1.aarch64", "SUSE Package Hub 15:singularity-3.4.1-bp151.3.3.1.ppc64le", "SUSE Package Hub 15:singularity-3.4.1-bp151.3.3.1.s390x", "SUSE Package Hub 15:singularity-3.4.1-bp151.3.3.1.x86_64" ] } ], "threats": [ { "category": "impact", "date": "2019-10-07T15:31:24Z", "details": "important" } ], "title": "CVE-2019-11328" } ] }
Loading…
Loading…
Sightings
Author | Source | Type | Date |
---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.
Loading…
Loading…