sylabs/singularity: Singularity 3.5.2 Release
Notice bibliographique
Résumé
Security Release The 3.5.2 release of Singularity contains fixes for a security issue related to incorrect file permissions (CVE-2019-19724) on user configuration and cache directories. In Singularity >=3.3.0 (on all OS/kernels) the $HOME/.singularity directory holding user configuration and caches is incorrectly created with 777 permissions. If the $HOME directory of a user has group/any x permission set, then a malicious user with login access to the host system may traverse into $HOME/.singularity and: Inject a remote.yaml configuration file that can direct interactions with Sylabs cloud services / Singularity Enterprise to a malicious server. This may result in the execution of malicious container images. Read the content of a user's cached containers, which may include sensitive private data. In Singularity >=2.4.0 (on all OS/kernels) the $HOME/.singularity directory and any explicit SINGULARITY_CACHEDIR directory are created with 755, or umask dependent permissions. If a user's $HOME directory, or the directory containing an explicitly set SINGULARITY_CACHEDIR, have group/any x permission set, then a malicious user with login access to the host system may: Read the content of a user's cached containers, which may include sensitive private data. Singularity 3.5.2 should be installed immediately, and all previous versions of Singularity should be removed. Additionally, we recommend running chmod 700 against the .singularity directory within all user $HOME directories, especially if $HOME directories may have group/any x bits set on your system. Mitigations / Notes If no user $HOME directories have group/any x bits set, and SINGULARITY_CACHEDIR has never been set to a location open to shared access, the exploits listed above are not possible. If Singularity is configured to only run containers signed with keys specified in an execution control list, and these keys are not compromised, arbitrary malicious containers cannot be run with a remote.yaml exploit. Singularity 3.5.2 ensures 700 permissions are set on $HOME/.singularity when the singularity command is run by a user, and that 700 permissions are set for any existing or new explicit cache directory configured using the SINGULARITY_CACHEDIR environment variable. This release makes additional permission changes to further harden plugin operations against weak directory permissions / sudo secure umask settings, that should not occur without explicit administrator action. Singularity Desktop for Mac Previous alpha and beta versions of Singularity Desktop for Mac are affected by this issue. A new beta release, beta-v0.2, is being prepared, and will be available shortly. Patches against prior versions In keeping with our commitment to the open source community to release security patches incorporated into Singularity PRO, Sylabs is also releasing patches that can be applied to the 3.1, 2.6, 2.5, and 2.4 series. Even though 3.5.2 technically deprecates all previous open-source versions of Singularity, interested parties can find the patches to fix this specific issue at the following links: 3.1: https://repo.sylabs.io/security/2019/CVE-2019-19724-31.diff 2.6 / 2.5 / 2.4: https://repo.sylabs.io/security/2019/CVE-2019-19724-2x.diff Note - these prior versions of Singularity may be subject to additional security issues, addressed by further patches released previously. Please review the release history carefully before using a deprecated version of Singularity. Release Notes Security related fix 700 permissions are enforced on $HOME/.singularity and SINGULARITY_CACHEDIR directories (CVE-2019-19724). Many thanks to Stuart Barkley for reporting this issue. Bug Fixes Fixes an issue preventing use of .docker/config for docker registry authentication. Fixes the run-help command in the unprivileged workflow. Fixes a regression in the inspect command to support older image formats. Adds a workaround for an EL6 kernel bug regarding shared bind mounts. Fixes caching of http(s) sources with conflicting filenames. Fixes a fakeroot sandbox build error on certain filesystems, e.g. lustre, GPFS. Fixes a fakeroot build failure to a sandbox in $HOME. Fixes a fakeroot build failure from a bad def file section script location. Fixes container execution errors when CWD is a symlink. Provides a useful warning r.e. possible fakeroot build issues when seccomp support is not available. Fixes an issue where the --disable-cache option was not being honored.
Récupéré en direct depuis OpenAlex et désinversé. Les résumés ne sont pas conservés dans cette base de données : les index inversés représentent 8,6 Go des 9,3 Go de texte de la base, et le serveur dispose de 13 Go libres.
Comment cette classification a été obtenuedéplier
Prédiction machine sur la base complète
Imitation des enseignantsNi prévalence calibrée, ni vérité terrain. Validation humaine à venir. Le volet Gemma est une étiquette directe du modèle pour chaque travail de la base, lue sur la notice réduite au titre. Le volet Codex est un classifieur appris des 10 348 étiquettes directes de Codex et calibré sur les taux pondérés de l'échantillon; les champs sans appui suffisant ne portent aucun appel Codex. Le mode candidate est l'union des deux volets; le consensus est leur intersection. Ces sorties portent le statut machine_predicted_unvalidated et ne sont pas des étiquettes humaines.
Scores du classifieur distillé par catégorie (deux têtes)
| Catégorie | Codex | Gemma |
|---|---|---|
| Métarecherche | 0,005 | 0,038 |
| Méta-épidémiologie (sens strict) | 0,002 | 0,002 |
| Méta-épidémiologie (sens large) | 0,001 | 0,001 |
| Bibliométrie | 0,002 | 0,001 |
| Études des sciences et des technologies | 0,001 | 0,002 |
| Communication savante | 0,007 | 0,009 |
| Science ouverte | 0,005 | 0,006 |
| Intégrité de la recherche | 0,003 | 0,005 |
| Charge utile insuffisante (le modèle a refusé de juger) | 0,263 | 0,316 |
Scores machine (provisoires)
Les deux têtes enseignantes du modèle étudiant, lues sur ce travail. Un score ordonne la base pour la relecture; il n'affirme jamais une catégorie, et le statut de validation accompagne chaque rangée tel quel.
Scores de référence d'un modèle non mature (critères de maturité non atteints, 7 itérations). Un score ordonne; il n'affirme jamais une catégorie.
score_only:v0-immature-baseline · tel quel depuis la passe de notation : score_only signifie que le nombre peut ordonner les travaux, et qu'aucune étiquette de catégorie n'en découleClassification
machine, non validéePrédiction automatique; un appel candidat d’une seule source (Gemma direct ou Codex distillé), pas un consensus.
Le détail, modèle par modèle et score par score, se trouve en fin de page sous « Comment cette classification a été obtenue ».