suse-su-2020:3378-1
Vulnerability from csaf_suse
Published
2020-11-19 08:30
Modified
2020-11-19 08:30
Summary
Security update for podman

Notes

Title of the patch
Security update for podman
Description of the patch
This update for podman fixes the following issues: Security issue fixed: - This release resolves CVE-2020-14370, in which environment variables could be leaked between containers created using the Varlink API (bsc#1176804). Non-security issues fixed: - add dependency to timezone package or podman fails to build a container (bsc#1178122) - Install new auto-update system units - Update to v2.1.1 (bsc#1178392): * Changes - The `podman info` command now includes the cgroup manager Podman is using. * API - The REST API now includes a Server header in all responses. - Fixed a bug where the Libpod and Compat Attach endpoints could terminate early, before sending all output from the container. - Fixed a bug where the Compat Create endpoint for containers did not properly handle the Interactive parameter. - Fixed a bug where the Compat Kill endpoint for containers could continue to run after a fatal error. - Fixed a bug where the Limit parameter of the Compat List endpoint for Containers did not properly handle a limit of 0 (returning nothing, instead of all containers) [#7722]. - The Libpod Stats endpoint for containers is being deprecated and will be replaced by a similar endpoint with additional features in a future release. - Changes in v2.1.0 * Features - A new command, `podman image mount`, has been added. This allows for an image to be mounted, read-only, to inspect its contents without creating a container from it [#1433]. - The `podman save` and `podman load` commands can now create and load archives containing multiple images [#2669]. - Rootless Podman now supports all `podman network` commands, and rootless containers can now be joined to networks. - The performance of `podman build` on `ADD` and `COPY` instructions has been greatly improved, especially when a `.dockerignore` is present. - The `podman run` and `podman create` commands now support a new mode for the `--cgroups` option, `--cgroups=split`. Podman will create two cgroups under the cgroup it was launched in, one for the container and one for Conmon. This mode is useful for running Podman in a systemd unit, as it ensures that all processes are retained in systemd's cgroup hierarchy [#6400]. - The `podman run` and `podman create` commands can now specify options to slirp4netns by using the `--network` option as follows: `--net slirp4netns:opt1,opt2`. This allows for, among other things, switching the port forwarder used by slirp4netns away from rootlessport. - The `podman ps` command now features a new option, `--storage`, to show containers from Buildah, CRI-O and other applications. - The `podman run` and `podman create` commands now feature a `--sdnotify` option to control the behavior of systemd's sdnotify with containers, enabling improved support for Podman in `Type=notify` units. - The `podman run` command now features a `--preserve-fds` opton to pass file descriptors from the host into the container [#6458]. - The `podman run` and `podman create` commands can now create overlay volume mounts, by adding the `:O` option to a bind mount (e.g. `-v /test:/test:O`). Overlay volume mounts will mount a directory into a container from the host and allow changes to it, but not write those changes back to the directory on the host. - The `podman play kube` command now supports the Socket HostPath type [#7112]. - The `podman play kube` command now supports read-only mounts. - The `podman play kube` command now supports setting labels on pods from Kubernetes metadata labels. - The `podman play kube` command now supports setting container restart policy [#7656]. - The `podman play kube` command now properly handles `HostAlias` entries. - The `podman generate kube` command now adds entries to `/etc/hosts` from `--host-add` generated YAML as `HostAlias` entries. - The `podman play kube` and `podman generate kube` commands now properly support `shareProcessNamespace` to share the PID namespace in pods. - The `podman volume ls` command now supports the `dangling` filter to identify volumes that are dangling (not attached to any container). - The `podman run` and `podman create` commands now feature a `--umask` option to set the umask of the created container. - The `podman create` and `podman run` commands now feature a `--tz` option to set the timezone within the container [#5128]. - Environment variables for Podman can now be added in the `containers.conf` configuration file. - The `--mount` option of `podman run` and `podman create` now supports a new mount type, `type=devpts`, to add a `devpts` mount to the container. This is useful for containers that want to mount `/dev/` from the host into the container, but still create a terminal. - The `--security-opt` flag to `podman run` and `podman create` now supports a new option, `proc-opts`, to specify options for the container's `/proc` filesystem. - Podman with the `crun` OCI runtime now supports a new option to `podman run` and `podman create`, `--cgroup-conf`, which allows for advanced configuration of cgroups on cgroups v2 systems. - The `podman create` and `podman run` commands now support a `--override-variant` option, to override the architecture variant of the image that will be pulled and ran. - A new global option has been added to Podman, `--runtime-flags`, which allows for setting flags to use when the OCI runtime is called. - The `podman manifest add` command now supports the `--cert-dir`, `--auth-file`, `--creds`, and `--tls-verify` options. * Security - This release resolves CVE-2020-14370, in which environment variables could be leaked between containers created using the Varlink API. * Changes - Podman will now retry pulling an image 3 times if a pull fails due to network errors. - The `podman exec` command would previously print error messages (e.g. `exec session exited with non-zero exit code -1`) when the command run exited with a non-0 exit code. It no longer does this. The `podman exec` command will still exit with the same exit code as the command run in the container did. - Error messages when creating a container or pod with a name that is already in use have been improved. - For read-only containers running systemd init, Podman creates a tmpfs filesystem at `/run`. This was previously limited to 65k in size and mounted `noexec`, but is now unlimited size and mounted `exec`. - The `podman system reset` command no longer removes configuration files for rootless Podman. * API - The Libpod API version has been bumped to v2.0.0 due to a breaking change in the Image List API. - Docker-compatible Volume Endpoints (Create, Inspect, List, Remove, Prune) are now available! - Added an endpoint for generating systemd unit files for containers. - The `last` parameter to the Libpod container list endpoint now has an alias, `limit` [#6413]. - The Libpod image list API new returns timestamps in Unix format, as integer, as opposed to as strings - The Compat Inspect endpoint for containers now includes port information in NetworkSettings. - The Compat List endpoint for images now features limited support for the (deprecated) `filter` query parameter [#6797]. - Fixed a bug where the Compat Create endpoint for containers was not correctly handling bind mounts. - Fixed a bug where the Compat Create endpoint for containers would not return a 404 when the requested image was not present. - Fixed a bug where the Compat Create endpoint for containers did not properly handle Entrypoint and Command from images. - Fixed a bug where name history information was not properly added in the Libpod Image List endpoint. - Fixed a bug where the Libpod image search endpoint improperly populated the Description field of responses. - Added a `noTrunc` option to the Libpod image search endpoint. - Fixed a bug where the Pod List API would return null, instead of an empty array, when no pods were present [#7392]. - Fixed a bug where endpoints that hijacked would do perform the hijack too early, before being ready to send and receive data [#7195]. - Fixed a bug where Pod endpoints that can operate on multiple containers at once (e.g. Kill, Pause, Unpause, Stop) would not forward errors from individual containers that failed. - The Compat List endpoint for networks now supports filtering results [#7462]. - Fixed a bug where the Top endpoint for pods would return both a 500 and 404 when run on a non-existent pod. - Fixed a bug where Pull endpoints did not stream progress back to the client. - The Version endpoints (Libpod and Compat) now provide version in a format compatible with Docker. - All non-hijacking responses to API requests should not include headers with the version of the server. - Fixed a bug where Libpod and Compat Events endpoints did not send response headers until the first event occurred [#7263]. - Fixed a bug where the Build endpoints (Compat and Libpod) did not stream progress to the client. - Fixed a bug where the Stats endpoints (Compat and Libpod) did not properly handle clients disconnecting. - Fixed a bug where the Ignore parameter to the Libpod Stop endpoint was not performing properly. - Fixed a bug where the Compat Logs endpoint for containers did not stream its output in the correct format [#7196].
Patchnames
SUSE-2020-3378,SUSE-SLE-Module-Containers-15-SP1-2020-3378,SUSE-SLE-Module-Containers-15-SP2-2020-3378,SUSE-Storage-7-2020-3378
Terms of use
CSAF 2.0 data is provided by SUSE under the Creative Commons License 4.0 with Attribution (CC-BY-4.0).


To clipboard 

{
  "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 podman",
        "title": "Title of the patch"
      },
      {
        "category": "description",
        "text": "This update for podman fixes the following issues:\n\nSecurity issue fixed:\n\n- This release resolves CVE-2020-14370, in which environment variables could be leaked between containers created using the Varlink API (bsc#1176804).\n\nNon-security issues fixed:\n\n- add dependency to timezone package or podman fails to build a \n  container (bsc#1178122)\n\n- Install new auto-update system units\n- Update to v2.1.1 (bsc#1178392):\n  * Changes\n    - The `podman info` command now includes the cgroup manager\n      Podman is using.\n  * API\n    - The REST API now includes a Server header in all responses.\n    - Fixed a bug where the Libpod and Compat Attach endpoints\n      could terminate early, before sending all output from the\n      container.\n    - Fixed a bug where the Compat Create endpoint for containers\n      did not properly handle the Interactive parameter.\n    - Fixed a bug where the Compat Kill endpoint for containers\n      could continue to run after a fatal error.\n    - Fixed a bug where the Limit parameter of the Compat List\n      endpoint for Containers did not properly handle a limit of 0\n      (returning nothing, instead of all containers) [#7722].\n    - The Libpod Stats endpoint for containers is being deprecated\n      and will be replaced by a similar endpoint with additional\n      features in a future release.\n- Changes in v2.1.0\n  * Features\n    - A new command, `podman image mount`, has been added. This\n      allows for an image to be mounted, read-only, to inspect its\n      contents without creating a container from it [#1433].\n    - The `podman save` and `podman load` commands can now create\n      and load archives containing multiple images [#2669].\n    - Rootless Podman now supports all `podman network` commands,\n      and rootless containers can now be joined to networks.\n    - The performance of `podman build` on `ADD` and `COPY`\n      instructions has been greatly improved, especially when a\n      `.dockerignore` is present.\n    - The `podman run` and `podman create` commands now support a\n      new mode for the `--cgroups` option, `--cgroups=split`.\n      Podman will create two cgroups under the cgroup it was\n      launched in, one for the container and one for Conmon. This\n      mode is useful for running Podman in a systemd unit, as it\n      ensures that all processes are retained in systemd\u0027s cgroup\n      hierarchy [#6400].\n    - The `podman run` and `podman create` commands can now specify\n      options to slirp4netns by using the `--network` option as\n      follows:  `--net slirp4netns:opt1,opt2`. This allows for,\n      among other things, switching the port forwarder used by\n      slirp4netns away from rootlessport.\n    - The `podman ps` command now features a new option,\n      `--storage`, to show containers from Buildah, CRI-O and other\n      applications.\n    - The `podman run` and `podman create` commands now feature a\n      `--sdnotify` option to control the behavior of systemd\u0027s\n      sdnotify with containers, enabling improved support for\n      Podman in `Type=notify` units.\n    - The `podman run` command now features a `--preserve-fds`\n      opton to pass file descriptors from the host into the\n      container [#6458].\n    - The `podman run` and `podman create` commands can now create\n      overlay volume mounts, by adding the `:O` option to a bind\n      mount (e.g. `-v /test:/test:O`). Overlay volume mounts will\n      mount a directory into a container from the host and allow\n      changes to it, but not write those changes back to the\n      directory on the host.\n    - The `podman play kube` command now supports the Socket\n      HostPath type [#7112].\n    - The `podman play kube` command now supports read-only mounts.\n    - The `podman play kube` command now supports setting labels on\n      pods from Kubernetes metadata labels.\n    - The `podman play kube` command now supports setting container\n      restart policy [#7656].\n    - The `podman play kube` command now properly handles\n      `HostAlias` entries.\n    - The `podman generate kube` command now adds entries to\n      `/etc/hosts` from `--host-add` generated YAML as `HostAlias`\n      entries.\n    - The `podman play kube` and `podman generate kube` commands\n      now properly support `shareProcessNamespace` to share the PID\n      namespace in pods.\n    - The `podman volume ls` command now supports the `dangling`\n      filter to identify volumes that are dangling (not attached to\n      any container).\n    - The `podman run` and `podman create` commands now feature a\n      `--umask` option to set the umask of the created container.\n    - The `podman create` and `podman run` commands now feature a\n      `--tz` option to set the timezone within the container [#5128].\n    - Environment variables for Podman can now be added in the\n      `containers.conf` configuration file.\n    - The `--mount` option of `podman run` and `podman create` now\n      supports a new mount type, `type=devpts`, to add a `devpts`\n      mount to the container. This is useful for containers that\n      want to mount `/dev/` from the host into the container, but\n      still create a terminal.\n    - The `--security-opt` flag to `podman run` and `podman create`\n      now supports a new option, `proc-opts`, to specify options\n      for the container\u0027s `/proc` filesystem.\n    - Podman with the `crun` OCI runtime now supports a new option\n      to `podman run` and `podman create`, `--cgroup-conf`, which\n      allows for advanced configuration of cgroups on cgroups v2\n      systems.\n    - The `podman create` and `podman run` commands now support a\n      `--override-variant` option, to override the architecture\n      variant of the image that will be pulled and ran.\n    - A new global option has been added to Podman,\n      `--runtime-flags`, which allows for setting flags to use when\n      the OCI runtime is called.\n    - The `podman manifest add` command now supports the\n      `--cert-dir`, `--auth-file`, `--creds`, and `--tls-verify`\n      options.\n  * Security\n    - This release resolves CVE-2020-14370, in which environment\n      variables could be leaked between containers created using\n      the Varlink API.\n  * Changes\n    - Podman will now retry pulling an image 3 times if a pull\n      fails due to network errors.\n    - The `podman exec` command would previously print error\n      messages (e.g. `exec session exited with non-zero exit code\n      -1`) when the command run exited with a non-0 exit code. It\n      no longer does this. The `podman exec` command will still\n      exit with the same exit code as the command run in the\n      container did.\n    - Error messages when creating a container or pod with a name\n      that is already in use have been improved.\n    - For read-only containers running systemd init, Podman creates\n      a tmpfs filesystem at `/run`. This was previously limited to\n      65k in size and mounted `noexec`, but is now unlimited size\n      and mounted `exec`.\n    - The `podman system reset` command no longer removes\n      configuration files for rootless Podman.\n  * API\n    - The Libpod API version has been bumped to v2.0.0 due to a\n      breaking change in the Image List API.\n    - Docker-compatible Volume Endpoints (Create, Inspect, List,\n      Remove, Prune) are now available!\n    - Added an endpoint for generating systemd unit files for\n      containers.\n    - The `last` parameter to the Libpod container list endpoint\n      now has an alias, `limit` [#6413].\n    - The Libpod image list API new returns timestamps in Unix\n      format, as integer, as opposed to as strings\n    - The Compat Inspect endpoint for containers now includes port\n      information in NetworkSettings.\n    - The Compat List endpoint for images now features limited\n      support for the (deprecated) `filter` query parameter [#6797].\n    - Fixed a bug where the Compat Create endpoint for containers\n      was not correctly handling bind mounts.\n    - Fixed a bug where the Compat Create endpoint for containers\n      would not return a 404 when the requested image was not\n      present.\n    - Fixed a bug where the Compat Create endpoint for containers\n      did not properly handle Entrypoint and Command from images.\n    - Fixed a bug where name history information was not properly\n      added in the Libpod Image List endpoint.\n    - Fixed a bug where the Libpod image search endpoint improperly\n      populated the Description field of responses.\n    - Added a `noTrunc` option to the Libpod image search endpoint.\n    - Fixed a bug where the Pod List API would return null, instead\n      of an empty array, when no pods were present [#7392].\n    - Fixed a bug where endpoints that hijacked would do perform\n      the hijack too early, before being ready to send and receive\n      data [#7195].\n    - Fixed a bug where Pod endpoints that can operate on multiple\n      containers at once (e.g. Kill, Pause, Unpause, Stop) would\n      not forward errors from individual containers that failed.\n    - The Compat List endpoint for networks now supports filtering\n      results [#7462].\n    - Fixed a bug where the Top endpoint for pods would return both\n      a 500 and 404 when run on a non-existent pod.\n    - Fixed a bug where Pull endpoints did not stream progress back\n      to the client.\n    - The Version endpoints (Libpod and Compat) now provide version\n      in a format compatible with Docker.\n    - All non-hijacking responses to API requests should not\n      include headers with the version of the server.\n    - Fixed a bug where Libpod and Compat Events endpoints did not\n      send response headers until the first event occurred [#7263].\n    - Fixed a bug where the Build endpoints (Compat and Libpod) did\n      not stream progress to the client.\n    - Fixed a bug where the Stats endpoints (Compat and Libpod) did\n      not properly handle clients disconnecting.\n    - Fixed a bug where the Ignore parameter to the Libpod Stop\n      endpoint was not performing properly.\n    - Fixed a bug where the Compat Logs endpoint for containers did\n      not stream its output in the correct format [#7196].\n",
        "title": "Description of the patch"
      },
      {
        "category": "details",
        "text": "SUSE-2020-3378,SUSE-SLE-Module-Containers-15-SP1-2020-3378,SUSE-SLE-Module-Containers-15-SP2-2020-3378,SUSE-Storage-7-2020-3378",
        "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/suse-su-2020_3378-1.json"
      },
      {
        "category": "self",
        "summary": "URL for SUSE-SU-2020:3378-1",
        "url": "https://www.suse.com/support/update/announcement/2020/suse-su-20203378-1/"
      },
      {
        "category": "self",
        "summary": "E-Mail link for SUSE-SU-2020:3378-1",
        "url": "https://lists.suse.com/pipermail/sle-security-updates/2020-November/007809.html"
      },
      {
        "category": "self",
        "summary": "SUSE Bug 1176804",
        "url": "https://bugzilla.suse.com/1176804"
      },
      {
        "category": "self",
        "summary": "SUSE Bug 1178122",
        "url": "https://bugzilla.suse.com/1178122"
      },
      {
        "category": "self",
        "summary": "SUSE Bug 1178392",
        "url": "https://bugzilla.suse.com/1178392"
      },
      {
        "category": "self",
        "summary": "SUSE CVE CVE-2020-14370 page",
        "url": "https://www.suse.com/security/cve/CVE-2020-14370/"
      }
    ],
    "title": "Security update for podman",
    "tracking": {
      "current_release_date": "2020-11-19T08:30:15Z",
      "generator": {
        "date": "2020-11-19T08:30:15Z",
        "engine": {
          "name": "cve-database.git:bin/generate-csaf.pl",
          "version": "1"
        }
      },
      "id": "SUSE-SU-2020:3378-1",
      "initial_release_date": "2020-11-19T08:30:15Z",
      "revision_history": [
        {
          "date": "2020-11-19T08:30:15Z",
          "number": "1",
          "summary": "Current version"
        }
      ],
      "status": "final",
      "version": "1"
    }
  },
  "product_tree": {
    "branches": [
      {
        "branches": [
          {
            "branches": [
              {
                "category": "product_version",
                "name": "podman-2.1.1-4.28.1.aarch64",
                "product": {
                  "name": "podman-2.1.1-4.28.1.aarch64",
                  "product_id": "podman-2.1.1-4.28.1.aarch64"
                }
              }
            ],
            "category": "architecture",
            "name": "aarch64"
          },
          {
            "branches": [
              {
                "category": "product_version",
                "name": "podman-2.1.1-4.28.1.i586",
                "product": {
                  "name": "podman-2.1.1-4.28.1.i586",
                  "product_id": "podman-2.1.1-4.28.1.i586"
                }
              }
            ],
            "category": "architecture",
            "name": "i586"
          },
          {
            "branches": [
              {
                "category": "product_version",
                "name": "podman-cni-config-2.1.1-4.28.1.noarch",
                "product": {
                  "name": "podman-cni-config-2.1.1-4.28.1.noarch",
                  "product_id": "podman-cni-config-2.1.1-4.28.1.noarch"
                }
              }
            ],
            "category": "architecture",
            "name": "noarch"
          },
          {
            "branches": [
              {
                "category": "product_version",
                "name": "podman-2.1.1-4.28.1.ppc64le",
                "product": {
                  "name": "podman-2.1.1-4.28.1.ppc64le",
                  "product_id": "podman-2.1.1-4.28.1.ppc64le"
                }
              }
            ],
            "category": "architecture",
            "name": "ppc64le"
          },
          {
            "branches": [
              {
                "category": "product_version",
                "name": "podman-2.1.1-4.28.1.s390x",
                "product": {
                  "name": "podman-2.1.1-4.28.1.s390x",
                  "product_id": "podman-2.1.1-4.28.1.s390x"
                }
              }
            ],
            "category": "architecture",
            "name": "s390x"
          },
          {
            "branches": [
              {
                "category": "product_version",
                "name": "podman-2.1.1-4.28.1.x86_64",
                "product": {
                  "name": "podman-2.1.1-4.28.1.x86_64",
                  "product_id": "podman-2.1.1-4.28.1.x86_64"
                }
              }
            ],
            "category": "architecture",
            "name": "x86_64"
          },
          {
            "branches": [
              {
                "category": "product_name",
                "name": "SUSE Linux Enterprise Module for Containers 15 SP1",
                "product": {
                  "name": "SUSE Linux Enterprise Module for Containers 15 SP1",
                  "product_id": "SUSE Linux Enterprise Module for Containers 15 SP1",
                  "product_identification_helper": {
                    "cpe": "cpe:/o:suse:sle-module-containers:15:sp1"
                  }
                }
              },
              {
                "category": "product_name",
                "name": "SUSE Linux Enterprise Module for Containers 15 SP2",
                "product": {
                  "name": "SUSE Linux Enterprise Module for Containers 15 SP2",
                  "product_id": "SUSE Linux Enterprise Module for Containers 15 SP2",
                  "product_identification_helper": {
                    "cpe": "cpe:/o:suse:sle-module-containers:15:sp2"
                  }
                }
              },
              {
                "category": "product_name",
                "name": "SUSE Enterprise Storage 7",
                "product": {
                  "name": "SUSE Enterprise Storage 7",
                  "product_id": "SUSE Enterprise Storage 7",
                  "product_identification_helper": {
                    "cpe": "cpe:/o:suse:ses:7"
                  }
                }
              }
            ],
            "category": "product_family",
            "name": "SUSE Linux Enterprise"
          }
        ],
        "category": "vendor",
        "name": "SUSE"
      }
    ],
    "relationships": [
      {
        "category": "default_component_of",
        "full_product_name": {
          "name": "podman-2.1.1-4.28.1.aarch64 as component of SUSE Linux Enterprise Module for Containers 15 SP1",
          "product_id": "SUSE Linux Enterprise Module for Containers 15 SP1:podman-2.1.1-4.28.1.aarch64"
        },
        "product_reference": "podman-2.1.1-4.28.1.aarch64",
        "relates_to_product_reference": "SUSE Linux Enterprise Module for Containers 15 SP1"
      },
      {
        "category": "default_component_of",
        "full_product_name": {
          "name": "podman-2.1.1-4.28.1.ppc64le as component of SUSE Linux Enterprise Module for Containers 15 SP1",
          "product_id": "SUSE Linux Enterprise Module for Containers 15 SP1:podman-2.1.1-4.28.1.ppc64le"
        },
        "product_reference": "podman-2.1.1-4.28.1.ppc64le",
        "relates_to_product_reference": "SUSE Linux Enterprise Module for Containers 15 SP1"
      },
      {
        "category": "default_component_of",
        "full_product_name": {
          "name": "podman-2.1.1-4.28.1.s390x as component of SUSE Linux Enterprise Module for Containers 15 SP1",
          "product_id": "SUSE Linux Enterprise Module for Containers 15 SP1:podman-2.1.1-4.28.1.s390x"
        },
        "product_reference": "podman-2.1.1-4.28.1.s390x",
        "relates_to_product_reference": "SUSE Linux Enterprise Module for Containers 15 SP1"
      },
      {
        "category": "default_component_of",
        "full_product_name": {
          "name": "podman-2.1.1-4.28.1.x86_64 as component of SUSE Linux Enterprise Module for Containers 15 SP1",
          "product_id": "SUSE Linux Enterprise Module for Containers 15 SP1:podman-2.1.1-4.28.1.x86_64"
        },
        "product_reference": "podman-2.1.1-4.28.1.x86_64",
        "relates_to_product_reference": "SUSE Linux Enterprise Module for Containers 15 SP1"
      },
      {
        "category": "default_component_of",
        "full_product_name": {
          "name": "podman-cni-config-2.1.1-4.28.1.noarch as component of SUSE Linux Enterprise Module for Containers 15 SP1",
          "product_id": "SUSE Linux Enterprise Module for Containers 15 SP1:podman-cni-config-2.1.1-4.28.1.noarch"
        },
        "product_reference": "podman-cni-config-2.1.1-4.28.1.noarch",
        "relates_to_product_reference": "SUSE Linux Enterprise Module for Containers 15 SP1"
      },
      {
        "category": "default_component_of",
        "full_product_name": {
          "name": "podman-2.1.1-4.28.1.aarch64 as component of SUSE Linux Enterprise Module for Containers 15 SP2",
          "product_id": "SUSE Linux Enterprise Module for Containers 15 SP2:podman-2.1.1-4.28.1.aarch64"
        },
        "product_reference": "podman-2.1.1-4.28.1.aarch64",
        "relates_to_product_reference": "SUSE Linux Enterprise Module for Containers 15 SP2"
      },
      {
        "category": "default_component_of",
        "full_product_name": {
          "name": "podman-2.1.1-4.28.1.ppc64le as component of SUSE Linux Enterprise Module for Containers 15 SP2",
          "product_id": "SUSE Linux Enterprise Module for Containers 15 SP2:podman-2.1.1-4.28.1.ppc64le"
        },
        "product_reference": "podman-2.1.1-4.28.1.ppc64le",
        "relates_to_product_reference": "SUSE Linux Enterprise Module for Containers 15 SP2"
      },
      {
        "category": "default_component_of",
        "full_product_name": {
          "name": "podman-2.1.1-4.28.1.s390x as component of SUSE Linux Enterprise Module for Containers 15 SP2",
          "product_id": "SUSE Linux Enterprise Module for Containers 15 SP2:podman-2.1.1-4.28.1.s390x"
        },
        "product_reference": "podman-2.1.1-4.28.1.s390x",
        "relates_to_product_reference": "SUSE Linux Enterprise Module for Containers 15 SP2"
      },
      {
        "category": "default_component_of",
        "full_product_name": {
          "name": "podman-2.1.1-4.28.1.x86_64 as component of SUSE Linux Enterprise Module for Containers 15 SP2",
          "product_id": "SUSE Linux Enterprise Module for Containers 15 SP2:podman-2.1.1-4.28.1.x86_64"
        },
        "product_reference": "podman-2.1.1-4.28.1.x86_64",
        "relates_to_product_reference": "SUSE Linux Enterprise Module for Containers 15 SP2"
      },
      {
        "category": "default_component_of",
        "full_product_name": {
          "name": "podman-cni-config-2.1.1-4.28.1.noarch as component of SUSE Linux Enterprise Module for Containers 15 SP2",
          "product_id": "SUSE Linux Enterprise Module for Containers 15 SP2:podman-cni-config-2.1.1-4.28.1.noarch"
        },
        "product_reference": "podman-cni-config-2.1.1-4.28.1.noarch",
        "relates_to_product_reference": "SUSE Linux Enterprise Module for Containers 15 SP2"
      },
      {
        "category": "default_component_of",
        "full_product_name": {
          "name": "podman-2.1.1-4.28.1.aarch64 as component of SUSE Enterprise Storage 7",
          "product_id": "SUSE Enterprise Storage 7:podman-2.1.1-4.28.1.aarch64"
        },
        "product_reference": "podman-2.1.1-4.28.1.aarch64",
        "relates_to_product_reference": "SUSE Enterprise Storage 7"
      },
      {
        "category": "default_component_of",
        "full_product_name": {
          "name": "podman-2.1.1-4.28.1.x86_64 as component of SUSE Enterprise Storage 7",
          "product_id": "SUSE Enterprise Storage 7:podman-2.1.1-4.28.1.x86_64"
        },
        "product_reference": "podman-2.1.1-4.28.1.x86_64",
        "relates_to_product_reference": "SUSE Enterprise Storage 7"
      }
    ]
  },
  "vulnerabilities": [
    {
      "cve": "CVE-2020-14370",
      "ids": [
        {
          "system_name": "SUSE CVE Page",
          "text": "https://www.suse.com/security/cve/CVE-2020-14370"
        }
      ],
      "notes": [
        {
          "category": "general",
          "text": "An information disclosure vulnerability was found in containers/podman in versions before 2.0.5. When using the deprecated Varlink API or the Docker-compatible REST API, if multiple containers are created in a short duration, the environment variables from the first container will get leaked into subsequent containers. An attacker who has control over the subsequent containers could use this flaw to gain access to sensitive information stored in such variables.",
          "title": "CVE description"
        }
      ],
      "product_status": {
        "recommended": [
          "SUSE Enterprise Storage 7:podman-2.1.1-4.28.1.aarch64",
          "SUSE Enterprise Storage 7:podman-2.1.1-4.28.1.x86_64",
          "SUSE Linux Enterprise Module for Containers 15 SP1:podman-2.1.1-4.28.1.aarch64",
          "SUSE Linux Enterprise Module for Containers 15 SP1:podman-2.1.1-4.28.1.ppc64le",
          "SUSE Linux Enterprise Module for Containers 15 SP1:podman-2.1.1-4.28.1.s390x",
          "SUSE Linux Enterprise Module for Containers 15 SP1:podman-2.1.1-4.28.1.x86_64",
          "SUSE Linux Enterprise Module for Containers 15 SP1:podman-cni-config-2.1.1-4.28.1.noarch",
          "SUSE Linux Enterprise Module for Containers 15 SP2:podman-2.1.1-4.28.1.aarch64",
          "SUSE Linux Enterprise Module for Containers 15 SP2:podman-2.1.1-4.28.1.ppc64le",
          "SUSE Linux Enterprise Module for Containers 15 SP2:podman-2.1.1-4.28.1.s390x",
          "SUSE Linux Enterprise Module for Containers 15 SP2:podman-2.1.1-4.28.1.x86_64",
          "SUSE Linux Enterprise Module for Containers 15 SP2:podman-cni-config-2.1.1-4.28.1.noarch"
        ]
      },
      "references": [
        {
          "category": "external",
          "summary": "CVE-2020-14370",
          "url": "https://www.suse.com/security/cve/CVE-2020-14370"
        },
        {
          "category": "external",
          "summary": "SUSE Bug 1176804 for CVE-2020-14370",
          "url": "https://bugzilla.suse.com/1176804"
        }
      ],
      "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 Enterprise Storage 7:podman-2.1.1-4.28.1.aarch64",
            "SUSE Enterprise Storage 7:podman-2.1.1-4.28.1.x86_64",
            "SUSE Linux Enterprise Module for Containers 15 SP1:podman-2.1.1-4.28.1.aarch64",
            "SUSE Linux Enterprise Module for Containers 15 SP1:podman-2.1.1-4.28.1.ppc64le",
            "SUSE Linux Enterprise Module for Containers 15 SP1:podman-2.1.1-4.28.1.s390x",
            "SUSE Linux Enterprise Module for Containers 15 SP1:podman-2.1.1-4.28.1.x86_64",
            "SUSE Linux Enterprise Module for Containers 15 SP1:podman-cni-config-2.1.1-4.28.1.noarch",
            "SUSE Linux Enterprise Module for Containers 15 SP2:podman-2.1.1-4.28.1.aarch64",
            "SUSE Linux Enterprise Module for Containers 15 SP2:podman-2.1.1-4.28.1.ppc64le",
            "SUSE Linux Enterprise Module for Containers 15 SP2:podman-2.1.1-4.28.1.s390x",
            "SUSE Linux Enterprise Module for Containers 15 SP2:podman-2.1.1-4.28.1.x86_64",
            "SUSE Linux Enterprise Module for Containers 15 SP2:podman-cni-config-2.1.1-4.28.1.noarch"
          ]
        }
      ],
      "scores": [
        {
          "cvss_v3": {
            "baseScore": 6.5,
            "baseSeverity": "MEDIUM",
            "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N",
            "version": "3.1"
          },
          "products": [
            "SUSE Enterprise Storage 7:podman-2.1.1-4.28.1.aarch64",
            "SUSE Enterprise Storage 7:podman-2.1.1-4.28.1.x86_64",
            "SUSE Linux Enterprise Module for Containers 15 SP1:podman-2.1.1-4.28.1.aarch64",
            "SUSE Linux Enterprise Module for Containers 15 SP1:podman-2.1.1-4.28.1.ppc64le",
            "SUSE Linux Enterprise Module for Containers 15 SP1:podman-2.1.1-4.28.1.s390x",
            "SUSE Linux Enterprise Module for Containers 15 SP1:podman-2.1.1-4.28.1.x86_64",
            "SUSE Linux Enterprise Module for Containers 15 SP1:podman-cni-config-2.1.1-4.28.1.noarch",
            "SUSE Linux Enterprise Module for Containers 15 SP2:podman-2.1.1-4.28.1.aarch64",
            "SUSE Linux Enterprise Module for Containers 15 SP2:podman-2.1.1-4.28.1.ppc64le",
            "SUSE Linux Enterprise Module for Containers 15 SP2:podman-2.1.1-4.28.1.s390x",
            "SUSE Linux Enterprise Module for Containers 15 SP2:podman-2.1.1-4.28.1.x86_64",
            "SUSE Linux Enterprise Module for Containers 15 SP2:podman-cni-config-2.1.1-4.28.1.noarch"
          ]
        }
      ],
      "threats": [
        {
          "category": "impact",
          "date": "2020-11-19T08:30:15Z",
          "details": "moderate"
        }
      ],
      "title": "CVE-2020-14370"
    }
  ]
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




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.