Skip to content
Noroxi
CVE-2023-22809· NVD / CVE Program· CNA mitre

In Sudo before 1.9.12p2, the sudoedit (aka -e) feature mishandles extra arguments passed in the user-provided environment variables (SUDO_ED

Noroxi assessment

Priority: Plan (action score 48/100)

  • A ready-made attack module is public (Metasploit); exploiting it takes no special expertise.
  • Probability of exploitation in the next 30 days: 55.3% (FIRST EPSS); higher than 99% of all records.
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: sudo (AlmaLinux:8) 1.8.29-8.el8_7.1; sudo (AlmaLinux:9) 1.9.5p2-7.el9_1.1; sudo-python-plugin (AlmaLinux:9) 1.9.5p2-7.el9_1.1.

Add it to your regular patch cycle. Upgrade to sudo (AlmaLinux:8) 1.8.29-8.el8_7.1; sudo (AlmaLinux:9) 1.9.5p2-7.el9_1.1; sudo-python-plugin (AlmaLinux:9) 1.9.5p2-7.el9_1.1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In Sudo before 1.9.12p2, the sudoedit (aka -e) feature mishandles extra arguments passed in the user-provided environment variables (SUDO_EDITOR, VISUAL, and EDITOR), allowing a local attacker to append arbitrary entries to the list of files to process. This can lead to privilege escalation. Affected versions are 1.8.0 through 1.9.12.p1. The problem exists because a user-specified editor may contain a "--" argument that defeats a protection mechanism, e.g., an EDITOR='vim -- /path/to/extra/file' value.

HighCVSS 7.8 · v3.1—Weaponized Fix available
Published
Jan 18, 2023
Updated
Jun 17, 2026
EPSS
55.3% · 99th percentile

Report tools

JSON

Action score

48

Plan

Add it to your regular patch cycle.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
17 / 30 · 55.3%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • Weaponized exploit exists
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2023-22809

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
sudo projectsudo
debiandebian linux
fedoraprojectfedora
applemacos

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • apple macosbefore 13.4
  • debian debian linux10.0
  • debian debian linux11.0
  • fedoraproject fedora36
  • fedoraproject fedora37
  • sudo project sudo1.8.0 and later · before 1.9.12
  • sudo project sudo1.9.12

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:8sudobefore 1.8.29-8.el8_7.11.8.29-8.el8_7.1
AlmaLinux:9sudobefore 1.9.5p2-7.el9_1.11.9.5p2-7.el9_1.1
AlmaLinux:9sudo-python-pluginbefore 1.9.5p2-7.el9_1.11.9.5p2-7.el9_1.1
Alpine:v3.14sudofrom 1.8.0 · before 1.9.12_p2-r01.9.12_p2-r0
Debian:10sudobefore 1.8.27-1+deb10u51.8.27-1+deb10u5
Debian:11sudobefore 1.9.5p2-3+deb11u11.9.5p2-3+deb11u1
Debian:12sudobefore 1.9.12p2-11.9.12p2-1
openSUSE:Tumbleweedsudobefore 1.9.12p2-1.11.9.12p2-1.1
Red Hat:enterprise_linux:7::clientsudobefore 0:1.8.23-10.el7_9.30:1.8.23-10.el7_9.3
Red Hat:enterprise_linux:7::clientsudo-debuginfobefore 0:1.8.23-10.el7_9.30:1.8.23-10.el7_9.3
Red Hat:enterprise_linux:7::clientsudo-develbefore 0:1.8.23-10.el7_9.30:1.8.23-10.el7_9.3
Red Hat:enterprise_linux:8::baseossudobefore 0:1.8.29-8.el8_7.10:1.8.29-8.el8_7.1
Red Hat:enterprise_linux:8::baseossudo-debuginfobefore 0:1.8.29-8.el8_7.10:1.8.29-8.el8_7.1
Red Hat:enterprise_linux:8::baseossudo-debugsourcebefore 0:1.8.29-8.el8_7.10:1.8.29-8.el8_7.1
Red Hat:enterprise_linux:9::appstreamsudo-debuginfobefore 0:1.9.5p2-7.el9_1.10:1.9.5p2-7.el9_1.1
Red Hat:enterprise_linux:9::appstreamsudo-debugsourcebefore 0:1.9.5p2-7.el9_1.10:1.9.5p2-7.el9_1.1
Red Hat:enterprise_linux:9::appstreamsudo-python-pluginbefore 0:1.9.5p2-7.el9_1.10:1.9.5p2-7.el9_1.1
Red Hat:enterprise_linux:9::appstreamsudo-python-plugin-debuginfobefore 0:1.9.5p2-7.el9_1.10:1.9.5p2-7.el9_1.1
Red Hat:enterprise_linux:9::baseossudobefore 0:1.9.5p2-7.el9_1.10:1.9.5p2-7.el9_1.1
Red Hat:rhel_aus:7.4::serversudobefore 0:1.8.19p2-12.el7_4.30:1.8.19p2-12.el7_4.3
Red Hat:rhel_aus:7.4::serversudo-debuginfobefore 0:1.8.19p2-12.el7_4.30:1.8.19p2-12.el7_4.3
Red Hat:rhel_aus:7.4::serversudo-develbefore 0:1.8.19p2-12.el7_4.30:1.8.19p2-12.el7_4.3
Red Hat:rhel_aus:7.6::serversudobefore 0:1.8.23-3.el7_6.30:1.8.23-3.el7_6.3
Red Hat:rhel_aus:7.6::serversudo-debuginfobefore 0:1.8.23-3.el7_6.30:1.8.23-3.el7_6.3

+36

Other highest-scoring records for the same primary product.

  • CVE-2021-3156Sudo before 1.9.5p2 contains an off-by-one error that can result in a heap-based buffer overflow, which allows privilege escalation to root KEV
    91Now
  • CVE-2025-32463Sudo before 1.9.17p1 allows local users to obtain root access because /etc/nsswitch.conf from a user-controlled directory is used with the -KEV
    78This week
  • CVE-2019-14287In Sudo before 1.8.28, an attacker with access to a Runas ALL sudoer account can bypass certain policy blacklists and session PAM modules, a
    54Plan

Published before and after this one in the same product

  • ← EarlierCVE-2021-23240Jan 12, 2021 · selinux_edit_copy_tfiles in sudoedit in Sudo before 1.9.5 allows a local unprivileged user to gain file ownership and escalate privileges by
    31Monitor
  • ← EarlierCVE-2022-43995Nov 2, 2022 · Sudo 1.8.0 through 1.9.12, with the crypt() password backend, contains a plugins/sudoers/auth/passwd.c array-out-of-bounds error that can re
    28Monitor
  • Later →CVE-2023-27320Feb 28, 2023 · Sudo before 1.9.13p2 has a double free in the per-command chroot feature.
    28Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
almalinux:sudo1.9.5p2-7.el9_1.1 · AlmaLinux:9Package registry (OSV)
almalinux:sudo-python-plugin1.9.5p2-7.el9_1.1 · AlmaLinux:9Package registry (OSV)
alpine:sudo1.9.12_p2-r0 · Alpine:v3.14Package registry (OSV)
debian:sudo1.9.12p2-1 · Debian:12Package registry (OSV)
opensuse:sudo1.9.9-150400.4.12.1 · openSUSE:Leap Micro 5.3Package registry (OSV)
red hat:redhat-virtualization-host0:4.5.3-202302150956_8.6 · Red Hat:rhev_hypervisor:4.4::el8Package registry (OSV)
red hat:redhat-virtualization-host-image-update0:4.5.3-202302150956_8.6 · Red Hat:rhev_hypervisor:4.4::el8Package registry (OSV)
red hat:sudo0:1.8.25p1-8.el8_1.3 · Red Hat:rhel_e4s:8.1::baseosPackage registry (OSV)
red hat:sudo-debuginfo0:1.8.25p1-8.el8_1.3 · Red Hat:rhel_e4s:8.1::baseosPackage registry (OSV)
red hat:sudo-debugsource0:1.8.25p1-8.el8_1.3 · Red Hat:rhel_e4s:8.1::baseosPackage registry (OSV)
red hat:sudo-devel0:1.8.6p3-29.el6_10.7 · Red Hat:rhel_els:6Package registry (OSV)
red hat:sudo-python-plugin0:1.9.5p2-7.el9_0.2 · Red Hat:rhel_eus:9.0::appstreamPackage registry (OSV)
red hat:sudo-python-plugin-debuginfo0:1.9.5p2-7.el9_0.2 · Red Hat:rhel_eus:9.0::appstreamPackage registry (OSV)
rocky linux:sudo0:1.9.5p2-7.el9_1.1 · Rocky Linux:9Package registry (OSV)
suse:sudo1.8.10p3-10.44.1 · SUSE:Linux Enterprise Server 12 SP2-BCLPackage registry (OSV)
suse:sudo1.9.9-150400.4.12.1 · SUSE:Linux Enterprise Micro 5.3Package registry (OSV)

Exploit status

Weaponized

A ready exploit tool or active in-the-wild use is known for this vulnerability. This should be your top priority.

Evidence

  • Metasploit module ×1
  • Exploit-DB entry ×1
  • Proof-of-concept repository on GitHub ×12

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Exploit-DB entrylocal2023-04-03
Metasploit moduleexploit/linux/local/sudoedit_bypass_priv_escSudoedit Extra Arguments Priv Escexploit2023-01-18
Proof-of-concept repository on GitHubstars:1642023-01-21
Proof-of-concept repository on GitHubstars:62023-02-22
Proof-of-concept repository on GitHubstars:62023-04-06
Proof-of-concept repository on GitHubstars:02023-06-08
Proof-of-concept repository on GitHubstars:22023-06-20
Proof-of-concept repository on GitHubstars:02023-06-25
Proof-of-concept repository on GitHubstars:62023-07-10
Proof-of-concept repository on GitHubstars:22023-08-06
Proof-of-concept repository on GitHubstars:02024-08-26
Proof-of-concept repository on GitHubstars:22024-08-28

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. Metasploit-1 d
  2. Published
  3. First PoC+2 d
  4. TodayOct 18, 2026+1369 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Root cause

To simplify setup, a service account is granted broad, cluster-wide permissions. The principle of least privilege is skipped during installation.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

yaml
kind: ClusterRolerules:  - apiGroups: ["*"]    resources: ["*"]    verbs: ["*"]

Fixed

yaml
kind: Rolemetadata:  namespace: lodos-systemrules:  - apiGroups: ["apps"]    resources: ["deployments"]    verbs: ["get", "list", "update"]

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records