Sudo: memory corruption flaw under attack

What is affected

Sudo is mostly run by companies, schools and public bodies, not on home computers. You are unlikely to have it yourself, but organisations that hold your data may. Breaches that start with flaws like this one are how personal data ends up leaked.

Sudo contains an off-by-one error that can result in a heap-based buffer overflow, which allows for privilege escalation.

What an attacker can do

This is a memory corruption flaw. It lets an attacker corrupt the program's memory by feeding it specially crafted content: a web page, a file or a network message. The result ranges from a crash to the attacker running their own code.

How it is reached

Needs access to the device or a file opened on it

Access the attacker needs

A basic user account

Does the victim have to do something?

No, works without the victim doing anything

What to do

1. At home: nothing to install. Keep your own devices updated and use a different password for every service, so that a breach at one organisation does not open your other accounts.
2. If you administer Sudo at work: apply the vendor's fix or mitigation now and review logs for signs of compromise, because the flaw was being exploited before it was listed.
3. If the product is past its support date and no fix exists, take it off the internet or retire it.

Apply updates per vendor instructions.

How urgent is it

CISA added this vulnerability to its Known Exploited Vulnerabilities catalogue on April 6, 2022, which means there is reliable evidence of attacks in the wild. US federal agencies must fix it by April 27, 2022, a deadline that has already passed. That deadline does not bind anyone else, but it shows how seriously the agency rates it.

The EPSS model estimates a 100% probability that this flaw will be exploited somewhere in the next 30 days. That is higher than 100.0% of all scored vulnerabilities.

Its CVSS severity score is 7.8 out of 10 (high), as recorded in the US National Vulnerability Database.

Technical description

Sudo 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 via "sudoedit -s" and a command-line argument that ends with a single backslash character.