It was discovered that Sudo incorrectly handled the per-command chroot feature. In certain environments where Sudo is configured with a rule that contains a CHROOT setting, a local attacker could use this issue to cause Sudo to crash, resulting in a denial of service, or possibly escalate privileges.
{
"availability": "No subscription required",
"binaries": [
{
"binary_name": "sudo",
"binary_version": "1.9.9-1ubuntu2.3"
},
{
"binary_name": "sudo-ldap",
"binary_version": "1.9.9-1ubuntu2.3"
}
]
}
{
"ecosystem": "Ubuntu:22.04:LTS",
"cves": [
{
"severity": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H"
},
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H"
},
{
"type": "Ubuntu",
"score": "medium"
}
],
"id": "CVE-2023-27320"
}
]
}