<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://127.0.0.1:10001/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-21T06:25:51.681399+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://127.0.0.1:10001" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://127.0.0.1:10001/vuln/cve-2021-43784</id>
    <title>CVE-2021-43784 — Overflow in netlink bytemsg length field allows attacker to override netlink-based container configuration</title>
    <updated>2026-11-21T06:25:51.687015+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> opencontainers runc</p>
<p>runc is a CLI tool for spawning and running containers on Linux according to the OCI specification. In runc, netlink is used internally as a serialization system for specifying the relevant container configuration to the `C` portion of the code (responsible for the based namespace setup of containers). In all versions of runc prior to 1.0.3, the encoder did not handle the possibility of an integer overflow in the 16-bit length field for the byte array attribute type, meaning that a large enough malicious byte array attribute could result in the length overflowing and the attribute contents being parsed as netlink messages for container configuration. This vulnerability requires the attacker to have some control over the configuration of the container and would allow the attacker to bypass the namespace restrictions of the container by simply adding their own netlink payload which disables all namespaces. The main users impacted are those who allow untrusted images with untrusted configurations to run on their machines (such as with shared cloud infrastructure). runc version 1.0.3 contains a fix for this bug. As a workaround, one may try disallowing untrusted namespace paths from your container. It should be noted that untrusted namespace paths would allow the attacker to disable namespace protections entirely even in the absence of this bug.</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/cve-2021-43784"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/usn-6088-2</id>
    <title>USN-6088-2 — runc vulnerabilities</title>
    <updated>2026-11-21T06:25:51.687058+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:Pro:16.04:LTS: runc</p>
<p>USN-6088-1 fixed vulnerabilities in runC. This update provides
the corresponding updates for Ubuntu 16.04 LTS.</p>
<p>It was discovered that runC incorrectly performed access control when
mounting /proc to non-directories. An attacker could possibly use
this issue to escalate privileges.
(CVE-2019-19921)</p>
<p>Felix Wilhelm discovered that runC incorrecly handled netlink 
messages. An attacker could possibly use
this issue to escalate privileges. (CVE-2021-43784)</p>
<p>Andrew G. Morgan discovered that runC incorrectly set
inherited process capabilities inside the container.
An attacker could possibly use this issue to
escalate privileges. (CVE-2022-29162)</p>
<p>Original advisory details:</p>
<p>It was discovered that runC incorrectly made /sys/fs/cgroup
 writable when in rootless mode. An attacker could possibly
 use this issue to escalate privileges. (CVE-2023-25809)
 
 It was discovered that runC incorrectly performed access control when
 mounting /proc to non-directories. An attacker could possibly use
 this issue to escalate privileges. (CVE-2023-27561)
 
 It was discovered that runC incorrectly handled /proc and 
 /sys mounts inside a container. An attacker could possibly
 use this issue to bypass AppArmor, and potentially SELinux.
 (CVE-2023-28642)</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/usn-6088-2"/>
  </entry>
</feed>
