Skip to content
Fencer Intel
medium 6.9

CVE-2010-0426 json

sudo 1.6.x before 1.6.9p21 and 1.7.x before 1.7.2p4, when a pseudo-command is enabled, permits a match between the name of the pseudo-comma…

published 16y ago modified 4mo ago also EUVD-2010-0457

cvss
6.9
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.1%
EPSS 1.1% chance of exploitation in 30 days, percentile 65%
public exploits
0
none known

Summary

sudo 1.6.x before 1.6.9p21 and 1.7.x before 1.7.2p4, when a pseudo-command is enabled, permits a match between the name of the pseudo-command and the name of an executable file in an arbitrary directory, which allows local users to gain privileges via a crafted executable file, as demonstrated by a file named sudoedit in a user's home directory.

Patch / fix

  • sudo Debian 14, Debian 13, Debian 12 1.7.2p1-1.2

debian advisories DEBIAN-CVE-2010-0426

  • sudo RHEL 5 1.6.9p17-6.el5_4

red hat advisories RHSA-2010:0122

Is CVE-2010-0426 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2010-0426 updated cvss 6.6

sudo: sudoedit option can possibly allow for arbitrary code execution

  • Red Hat Enterprise Linux (v. 5 server) sudo 1.6.9p17-6.el5_4 Red Hat Enterprise Linux Desktop (v. 5 client) sudo 1.6.9p17-6.el5_4
    fixed: vendor fix RHSA-2010:0122

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.08% chance of exploitation in the next 30 days, higher than 65% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 6.9 AV:L/AC:M/Au:N/C:C/I:C/A:C

Classification

Weakness
  • CWE-264 Permissions, Privileges, and Access Controls

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.