https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 12:55:29 +0000 https://cve.radiocsirt.org/vuln/bdu:2023-03675 bdu:2023-03675 https://cve.radiocsirt.org/vuln/bdu:2023-03675 https://cve.radiocsirt.org/vuln/bell-cve-2021-41190 <p><strong>Withdrawn by the publisher.</strong></p> <p><strong>Withdrawn by the publisher.</strong></p> https://cve.radiocsirt.org/vuln/bell-cve-2021-41190 https://cve.radiocsirt.org/vuln/certfr-2022-avi-591 certfr-2022-avi-591 https://cve.radiocsirt.org/vuln/certfr-2022-avi-591 https://cve.radiocsirt.org/vuln/cleanstart-2025-hq55158 <p><strong>Affected:</strong> CleanStart: containerd</p> <p>Security vulnerability affects the containerd package. The OCI Distribution Spec project defines an API protocol to facilitate and standardize the distribution of content.</p> <p><strong>Affected:</strong> CleanStart: containerd</p> <p>Security vulnerability affects the containerd package. The OCI Distribution Spec project defines an API protocol to facilitate and standardize the distribution of content.</p> https://cve.radiocsirt.org/vuln/cleanstart-2025-hq55158 https://cve.radiocsirt.org/vuln/euvd-2026-31565 EUVD-2026-31565 https://cve.radiocsirt.org/vuln/euvd-2026-31565 https://cve.radiocsirt.org/vuln/fkie_cve-2021-41190 <p>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 that a mediaType value present in a manifest or index match the Content-Type header used during the push and pull operations. Clients pulling from a registry may distrust the Content-Type header and reject an ambiguous document that contains both “manifests” and “layers” fields or “manifests” and “config” fields if they are unable to update to version 1.0.1 of the spec.</p> <p>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 that a mediaType value present in a manifest or index match the Content-Type header used during the push and pull operations. Clients pulling from a registry may distrust the Content-Type header and reject an ambiguous document that contains both “manifests” and “layers” fields or “manifests” and “config” fields if they are unable to update to version 1.0.1 of the spec.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2021-41190 https://cve.radiocsirt.org/vuln/ghsa-mc8v-mgrf-8f4m <p><strong>Affected:</strong> Go: github.com/opencontainers/distribution-spec</p> <p>### Impact 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.</p> <p>### Patches The OCI Distribution Specification will be updated to require that a `mediaType` value present in a manifest or index match the Content-Type header used during the push and pull operations.</p> <p>### Workarounds Clients pulling from a registry may distrust the Content-Type header and reject an ambiguous document that contains both “manifests” and “layers” fields or “manifests” and “config” fields.</p> <p>### References https://github.com/opencontainers/image-spec/security/advisories/GHSA-77vh-xpmg-72qh</p> <p>### For more information If you have any questions or comments about this advisory: * Open an issue in https://github.com/opencontainers/distribution-spec/ * Email us at security@opencontainers.org</p> <p><strong>Affected:</strong> Go: github.com/opencontainers/distribution-spec</p> <p>### Impact 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.</p> <p>### Patches The OCI Distribution Specification will be updated to require that a `mediaType` value present in a manifest or index match the Content-Type header used during the push and pull operations.</p> <p>### Workarounds Clients pulling from a registry may distrust the Content-Type header and reject an ambiguous document that contains both “manifests” and “layers” fields or “manifests” and “config” fields.</p> <p>### References https://github.com/opencontainers/image-spec/security/advisories/GHSA-77vh-xpmg-72qh</p> <p>### For more information If you have any questions or comments about this advisory: * Open an issue in https://github.com/opencontainers/distribution-spec/ * Email us at security@opencontainers.org</p> https://cve.radiocsirt.org/vuln/ghsa-mc8v-mgrf-8f4m https://cve.radiocsirt.org/vuln/gsd-2021-41190 gsd-2021-41190 https://cve.radiocsirt.org/vuln/gsd-2021-41190 https://cve.radiocsirt.org/vuln/opensuse-su-2021:1525-1 <p>Security update for singularity</p> <p>Security update for singularity</p> https://cve.radiocsirt.org/vuln/opensuse-su-2021:1525-1 https://cve.radiocsirt.org/vuln/rhsa-2022:0055 <p>CXF: SSL hostname verification bypass, incomplete CVE-2012-6153 fix coreos-installer: incorrect signature verification on gzip-compressed install images jenkins-2-plugins/git: stored XSS vulnerability jenkins: FilePath#mkdirs does not check permission to create parent directories jenkins: File path filters do not canonicalize paths, allowing operations to follow symbolic links to outside allowed directories jenkins: FilePath#untar does not check permission to create symbolic links when unarchiving a symbolic link jenkins: FilePath#reading(FileVisitor) does not reject any operations allowing users to have unrestricted read access jenkins: FilePath#unzip and FilePath#untar were not subject to any access control jenkins: Agent processes are able to completely bypass file path filtering by wrapping the file operation in an agent file path jenkins: Creating symbolic links is possible without the symlink permission jenkins: The operations FilePath#renameTo and FilePath#moveAllChildrenTo only check read permission on the source path jenkins: When creating temporary files, permission to create files is only checked after they’ve been created. jenkins: FilePath#toURI, FilePath#hasSymlink, FilePath#absolutize, FilePath#isDescendant, and FilePath#get*DiskSpace do not check any permissions jenkins: FilePath#listFiles lists files outside directories with agent read access when following symbolic links. jenkins: Agent-to-controller access control allowed writing to sensitive directory use…</p> <p>CXF: SSL hostname verification bypass, incomplete CVE-2012-6153 fix coreos-installer: incorrect signature verification on gzip-compressed install images jenkins-2-plugins/git: stored XSS vulnerability jenkins: FilePath#mkdirs does not check permission to create parent directories jenkins: File path filters do not canonicalize paths, allowing operations to follow symbolic links to outside allowed directories jenkins: FilePath#untar does not check permission to create symbolic links when unarchiving a symbolic link jenkins: FilePath#reading(FileVisitor) does not reject any operations allowing users to have unrestricted read access jenkins: FilePath#unzip and FilePath#untar were not subject to any access control jenkins: Agent processes are able to completely bypass file path filtering by wrapping the file operation in an agent file path jenkins: Creating symbolic links is possible without the symlink permission jenkins: The operations FilePath#renameTo and FilePath#moveAllChildrenTo only check read permission on the source path jenkins: When creating temporary files, permission to create files is only checked after they’ve been created. jenkins: FilePath#toURI, FilePath#hasSymlink, FilePath#absolutize, FilePath#isDescendant, and FilePath#get*DiskSpace do not check any permissions jenkins: FilePath#listFiles lists files outside directories with agent read access when following symbolic links. jenkins: Agent-to-controller access control allowed writing to sensitive directory use…</p> https://cve.radiocsirt.org/vuln/rhsa-2022:0055 https://cve.radiocsirt.org/vuln/suse-su-2022:0213-1 <p>Security update for containerd, docker</p> <p>Security update for containerd, docker</p> https://cve.radiocsirt.org/vuln/suse-su-2022:0213-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-41190 <p><strong>Affected:</strong> Ubuntu:Pro:16.04:LTS: docker.io, Ubuntu:Pro:16.04:LTS: containerd, Ubuntu:18.04:LTS: containerd, Ubuntu:Pro:18.04:LTS: docker.io, Ubuntu:20.04:LTS: containerd, Ubuntu:22.04:LTS: containerd</p> <p>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 that a mediaType value present in a manifest or index match the Content-Type header used during the push and pull operations. Clients pulling from a registry may distrust the Content-Type header and reject an ambiguous document that contains both “manifests” and “layers” fields or “manifests” and “config” fields if they are unable to update to version 1.0.1 of the spec.</p> <p><strong>Affected:</strong> Ubuntu:Pro:16.04:LTS: docker.io, Ubuntu:Pro:16.04:LTS: containerd, Ubuntu:18.04:LTS: containerd, Ubuntu:Pro:18.04:LTS: docker.io, Ubuntu:20.04:LTS: containerd, Ubuntu:22.04:LTS: containerd</p> <p>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 that a mediaType value present in a manifest or index match the Content-Type header used during the push and pull operations. Clients pulling from a registry may distrust the Content-Type header and reject an ambiguous document that contains both “manifests” and “layers” fields or “manifests” and “config” fields if they are unable to update to version 1.0.1 of the spec.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-41190 https://cve.radiocsirt.org/vuln/wid-sec-w-2022-0510 <p>Ein entfernter, anonymer, authentisierter oder lokaler Angreifer kann mehrere Schwachstellen in IBM DB2 ausnutzen, um Dateien zu manipulieren, Sicherheitsmaßnahmen zu umgehen, vertrauliche Informationen offenzulegen, einen Denial-of-Service-Zustand auszulösen, willkürlichen Code mit erhöhten Rechten auszuführen, Informationen falsch darzustellen und beliebigen Code auszuführen.</p> <p>Ein entfernter, anonymer, authentisierter oder lokaler Angreifer kann mehrere Schwachstellen in IBM DB2 ausnutzen, um Dateien zu manipulieren, Sicherheitsmaßnahmen zu umgehen, vertrauliche Informationen offenzulegen, einen Denial-of-Service-Zustand auszulösen, willkürlichen Code mit erhöhten Rechten auszuführen, Informationen falsch darzustellen und beliebigen Code auszuführen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2022-0510