Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

podman · Vulnerability

CVSS 3.1 5.9 MEDIUMEUVD CVSS 3.1 5.9 CVSS 3.1 · [email protected] · Secondary 5.9 MEDIUMCVSS 3.1 · [email protected] · Primary 5.9 MEDIUMCVSS 2.0 · [email protected] · Primary 5.8 MEDIUMCVSS_V3 Publisher rating MODERATEFixed by github.com/containers/podman 2.0.6Fixed by github.com/containers/podman/v2 2.0.6osv · severity unknownFixed by github.com/containers/libpod/v2 2.0.6KEV status unknown

cve-program · CVE-2020-1726

Published

A flaw was discovered in Podman where it incorrectly allows containers when created to overwrite existing files in volumes, even if they are mounted as read-only. When a user runs a malicious container or a container based on a malicious image with an attached volume that is used for the first time, it is possible to trigger the flaw and overwrite files in the volume.This issue was introduced in version 1.6.0.

Read the publisher's advisory

euvd · EUVD-2022-5384

Published

A flaw was discovered in Podman where it incorrectly allows containers when created to overwrite existing files in volumes, even if they are mounted as read-only. When a user runs a malicious container or a container based on a malicious image with an attached volume that is used for the first time, it is possible to trigger the flaw and overwrite files in the volume.This issue was introduced in version 1.6.0.

Read the publisher's advisory

nvd · CVE-2020-1726

Published

A flaw was discovered in Podman where it incorrectly allows containers when created to overwrite existing files in volumes, even if they are mounted as read-only. When a user runs a malicious container or a container based on a malicious image with an attached volume that is used for the first time, it is possible to trigger the flaw and overwrite files in the volume.This issue was introduced in version 1.6.0.

Read the publisher's advisory

osv · GHSA-vmhj-p9hw-vgrf

Published

A flaw was discovered in Podman where it incorrectly allows containers when created to overwrite existing files in volumes, even if they are mounted as read-only. When a user runs a malicious container or a container based on a malicious image with an attached volume that is used for the first time, it is possible to trigger the flaw and overwrite files in the volume. This issue was introduced in version 1.6.0.

Read the publisher's advisory

osv · GO-2023-1544

Published

Podman has Files or Directories Accessible to External Parties in github.com/containers/libpod

Read the publisher's advisory

Affected versions, risk and source history

Related advisories and sources

Publishers link these advisories through the identifiers shown below. A shared identifier or date alone does not tell you whether your software is affected or whether the advisories describe the same cause.

CVE-2020-1726 · CVE overview and exploitation status

EUVD-2022-5384

GHSA-vmhj-p9hw-vgrf

GO-2023-1544

cve-program · CVE-2020-1726

euvd · EUVD-2022-5384

nvd · CVE-2020-1726

osv · GHSA-vmhj-p9hw-vgrf

osv · GO-2023-1544

Related changes

Linked by CVE identifier
ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 15 Nov 23:13 UTC · 274 of 275 readable · 250 fully read · 18 waiting for GitHub's hourly limit · documentation 461/469 current