It was discovered that a systemd service that uses DynamicUser property can create a SUID/SGID binary that would be allowed to run as the transient service UID/GID even after the service is terminated. A local attacker may use this flaw to access resources that will be owned by a potentially different service in the future, when the UID/GID will be recycled.
{
"availability": "No subscription required",
"binaries": [
{
"binary_name": "libnss-myhostname",
"binary_version": "237-3ubuntu10.38"
},
{
"binary_name": "libnss-mymachines",
"binary_version": "237-3ubuntu10.38"
},
{
"binary_name": "libnss-resolve",
"binary_version": "237-3ubuntu10.38"
},
{
"binary_name": "libnss-systemd",
"binary_version": "237-3ubuntu10.38"
},
{
"binary_name": "libpam-systemd",
"binary_version": "237-3ubuntu10.38"
},
{
"binary_name": "libsystemd-dev",
"binary_version": "237-3ubuntu10.38"
},
{
"binary_name": "libsystemd0",
"binary_version": "237-3ubuntu10.38"
},
{
"binary_name": "libudev-dev",
"binary_version": "237-3ubuntu10.38"
},
{
"binary_name": "libudev1",
"binary_version": "237-3ubuntu10.38"
},
{
"binary_name": "systemd",
"binary_version": "237-3ubuntu10.38"
},
{
"binary_name": "systemd-container",
"binary_version": "237-3ubuntu10.38"
},
{
"binary_name": "systemd-coredump",
"binary_version": "237-3ubuntu10.38"
},
{
"binary_name": "systemd-journal-remote",
"binary_version": "237-3ubuntu10.38"
},
{
"binary_name": "systemd-sysv",
"binary_version": "237-3ubuntu10.38"
},
{
"binary_name": "systemd-tests",
"binary_version": "237-3ubuntu10.38"
},
{
"binary_name": "udev",
"binary_version": "237-3ubuntu10.38"
}
]
}