p PatchFirst

PatchFirst · Aktuelle Sicherheitslücken

Sicherheitslücken in singularity

In den letzten 30 Tagen veröffentlichte Sicherheitslücken für singularity: 0. Davon im KEV-Katalog: 0.

Sicherheitslücken filtern
Filter zurücksetzen

Sicherheitslücken: 14

  1. CVE-2024-23653

    Kritisch · CVSS 9.8EPSS 4,13%Korrektur verfügbar

    BuildKit interactive containers API does not validate entitlements check

    BuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and repeatable manner. In addition to running containers as build steps, BuildKit also provides APIs for running interactive containers based on built images. It was possible to use these APIs to ask BuildKit to run a container with elevated privileges. Normally, running such containers is only allowed if special `security.insecure` entitlement is enabled both by buildkitd configuration and allowed by the user initializing the build request. The issue has been fixed in v0.12.5 . Avoid using BuildKit frontends from untrusted sources.

    • Auf 4.1.1-r0 aktualisieren
    Veröffentlicht Aktualisiert
  2. CVE-2024-23652

    Kritisch · CVSS 10EPSS 2,46%Korrektur verfügbar

    BuildKit possible host system access from mount stub cleaner

    BuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and repeatable manner. A malicious BuildKit frontend or Dockerfile using RUN --mount could trick the feature that removes empty files created for the mountpoints into removing a file outside the container, from the host system. The issue has been fixed in v0.12.5. Workarounds include avoiding using BuildKit frontends from an untrusted source or building an untrusted Dockerfile containing RUN --mount feature.

    • Auf 4.1.1-r0 aktualisieren
    Veröffentlicht Aktualisiert
  3. CVE-2024-23651

    Hoch · CVSS 8.7EPSS 0,91%Korrektur verfügbar

    BuildKit possible race condition with accessing subpaths from cache mounts

    BuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and repeatable manner. Two malicious build steps running in parallel sharing the same cache mounts with subpaths could cause a race condition that can lead to files from the host system being accessible to the build container. The issue has been fixed in v0.12.5. Workarounds include, avoiding using BuildKit frontend from an untrusted source or building an untrusted Dockerfile containing cache mounts with --mount=type=cache,source=... options.

    • Auf 4.1.1-r0 aktualisieren
    Veröffentlicht Aktualisiert
  4. CVE-2024-23650

    Mittel · CVSS 5.3EPSS 1,14%Korrektur verfügbar

    BuildKit possible panic when incorrect parameters sent from frontend

    BuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and repeatable manner. A malicious BuildKit client or frontend could craft a request that could lead to BuildKit daemon crashing with a panic. The issue has been fixed in v0.12.5. As a workaround, avoid using BuildKit frontends from untrusted sources.

    • Auf 4.1.1-r0 aktualisieren
    Veröffentlicht Aktualisiert
  5. CVE-2021-41190

    Niedrig · CVSS 3EPSS 2,22%Korrektur verfügbar

    Clarify Content-Type handling in OCI spec

    The OCI Distribution Spec project defines an API protocol to facilitate and standardize the distribution of content. In the OCI Distribution Specification version 1.0.0 and prior, the Content-Type header alone was used to determine the type of document during push and pull operations. Documents that contain both “manifests” and “layers” fields could be interpreted as either a manifest or an index in the absence of an accompanying Content-Type header. If a Content-Type header changed between two pulls of the same digest, a client may interpret the resulting content differently. The OCI Distribution Specification has been updated to require tha

    • Auf 3.8.5-r0 aktualisieren
    Veröffentlicht Aktualisiert
  6. CVE-2021-32635

    Mittel · CVSS 6.3EPSS 1,42%Korrektur verfügbar

    Action Commands (run/shell/exec) Against Library URIs Ignore Configured Remote Endpoint

    Singularity is an open source container platform. In verions 3.7.2 and 3.7.3, Dde to incorrect use of a default URL, `singularity` action commands (`run`/`shell`/`exec`) specifying a container using a `library://` URI will always attempt to retrieve the container from the default remote endpoint (`cloud.sylabs.io`) rather than the configured remote endpoint. An attacker may be able to push a malicious container to the default remote endpoint with a URI that is identical to the URI used by a victim with a non-default remote endpoint, thus executing the malicious container. Only action commands (`run`/`shell`/`exec`) against `library://` URIs a

    • Auf 3.7.4-r0 aktualisieren
    Veröffentlicht Aktualisiert
  7. CVE-2020-15229

    Hoch · CVSS 8.2EPSS 2,05%Korrektur verfügbar

    Path traversal and files overwrite with unsquashfs

    Singularity (an open source container platform) from version 3.1.1 through 3.6.3 has a vulnerability. Due to insecure handling of path traversal and the lack of path sanitization within `unsquashfs`, it is possible to overwrite/create any files on the host filesystem during the extraction with a crafted squashfs filesystem. The extraction occurs automatically for unprivileged (either installation or with `allow setuid = no`) run of Singularity when a user attempt to run an image which is a local SIF image or a single file containing a squashfs filesystem and is coming from remote sources `library://` or `shub://`. Image build is also impacted

    • Auf 3.6.4-r0 aktualisieren
    Veröffentlicht Aktualisiert
  8. CVE-2020-13845

    Hoch · CVSS 7.5EPSS 0,52%Korrektur verfügbar

    CVE-2020-13845

    Sylabs Singularity 3.0 through 3.5 has Improper Validation of an Integrity Check Value. Image integrity is not validated when an ECL policy is enforced. The fingerprint required by the ECL is compared against the signature object descriptor(s) in the SIF file, rather than to a cryptographically validated signature.

    • Auf 3.6.0-r0 aktualisieren
    Veröffentlicht Aktualisiert

Prüfen Sie Ihren Server

Gleichen Sie Ihren installierten Stack und seine Versionen mit den aktuellen Sicherheitsmeldungen ab.

Prüfen Sie Ihren Server →