cve.bz

CVE-2023-27320 Double Free

7.2 highExploit referenceEPSS 1.7%

High (7.2). EPSS 1.7% estimated probability of exploitation activity in the next 30 days.

On this page
Sudo before 1.9.13p2 has a double free in the per-command chroot feature.

Severity

CVSS 3.1

7.2 high
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
EPSS
1.7% (unchanged from 1.7% a week ago; 1.7% 30 days ago) estimated probability of exploitation activity in the next 30 days; 77th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2025-03-21. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-415 Double Free
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2023-27320 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2023-27320?via=ask-ai-copy and https://cve.bz/cve/CVE-2023-27320?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2023-27320 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
sudo_project:sudofrom 1.9.8 before 1.9.13
sudo_project:sudo1.9.13
sudo_project:sudo1.9.13:p1
fedoraproject:fedora36
fedoraproject:fedora37
fedoraproject:fedora38

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13, 14sudo1.9.13p3-1DEBIAN-CVE-2023-27320
Ubuntu22.04:LTSsudo1.9.9-1ubuntu2.3UBUNTU-CVE-2023-27320 USN-5908-1
SUSELinux Enterprise Micro 5.3, Linux Enterprise Micro 5.4, Linux Enterprise Module for Basesystem 15 SP4sudo1.9.9-150400.4.26.1SUSE-SU-2023:1665-1
openSUSELeap 15.4, Leap Micro 5.3sudo1.9.9-150400.4.26.1SUSE-SU-2023:1665-1
openSUSETumbleweedsudo1.9.13p3-2.1openSUSE-SU-2024:12795-1
Alpinev3.17sudo1.9.12_p2-r1ALPINE-CVE-2023-27320
Azure Linux2sudo1.9.13p3-1AZL-13784

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; the Alpine secdb, CC BY-SA 4.0; Microsoft's Azure Linux vulnerability data, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · SUSE · openSUSE · Alpine.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

The CHROOT support was only added in Sudo v1.9.3 and Sudo v1.9.8 included a fix for a memory leak in the set_cmnd_path() function, which can result in the "user_cmnd" variable being freed twice, but only when processing a sudoers rule that contains a "CHROOT" setting. This does not affect the "chroot" Defaults setting. Only a per-rule "CHROOT" setting will trigger the bug.

Hence, it only affects Sudo v1.9.8 through to 1.9.13p1.

Red Hat Enterprise Linux - 6, 7, 8, 9 are shipped with lower versions of Sudo that doesn't contains the vulnerable code. Thus, they are not affected.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 6sudoNot affected
Red Hat Enterprise Linux 7sudoNot affected
Red Hat Enterprise Linux 8sudoNot affected
Red Hat Enterprise Linux 9sudoNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2023-27320.

References

Check your stackJSON