7.8 High
CVSS3
Attack Vector
LOCAL
Attack Complexity
LOW
Privileges Required
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality Impact
HIGH
Integrity Impact
HIGH
Availability Impact
HIGH
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
7.2 High
CVSS2
Access Vector
LOCAL
Access Complexity
LOW
Authentication
NONE
Confidentiality Impact
COMPLETE
Integrity Impact
COMPLETE
Availability Impact
COMPLETE
AV:L/AC:L/Au:N/C:C/I:C/A:C
0.971 High
EPSS
Percentile
99.7%
A heap-based overflow has been discovered in the set_cmd()
function in sudo, which may allow a local attacker to execute commands with elevated administrator privileges.
From the Sudo Main Page:
> Sudo (su “do”) allows a system administrator to delegate authority to give certain users (or groups of users) the ability to run some (or all) commands as root or another user while providing an audit trail of the commands and their arguments.
It is possible for a local Non-administrative user to exploit this vulnerability to elevate their privileges so that they can execute commands with administrator privileges. The team at Qualys assigned this vulnerability CVE-2021-3156 and found multiple *nix operating systems were vulnerable, including Fedora, Debian, and Ubuntu. A blog update from February 3, 2021, reports that macOS, AIX, and Solaris may be vulnerable, but Qualys had not yet confirmed this. There is additional reporting that other operating systems are affected, including Apple’s Big Sur.
If an attacker has local access to an affected machine then it is possible for them to execute commands with administrator privileges.
Apply an Update
Update sudo to the latest version to address this vulnerability when operationally feasible. This issue is resolved in sudo version 1.9.5p2. Please install this version, or a version from your distribution that has the fix applied to it
This vulnerability was researched and reported by the Qualys Research Team.
This document was written by Timur Snoke.
794544
Filter by status: All Affected Not Affected Unknown
Filter by content: __ Additional information available
__ Sort by: Status Alphabetical
Expand all
Notified: 2021-02-15 Updated: 2021-02-15
Statement Date: February 15, 2021
CVE-2021-3156 | Affected |
---|
Cisco is tracking this vulnerability via incident PSIRT-0750174077 .
Cisco has published a customer facing advisory here: https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-sudo-privesc-jan2021-qnYQfcM
it’s in interim status and gets update regularly as our investigation of the product base progresses.
Updated: 2021-02-04
Statement Date: January 26, 2021
CVE-2021-3156 | Affected |
---|
We have not received a statement from the vendor.
Notified: 2021-02-04 Updated: 2021-02-05
Statement Date: February 05, 2021
CVE-2021-3156 | Affected |
---|
F5 BIG-IP and BIG-IQ products are NOT VULNERABLE to CVE-2021-3156.
F5 Traffix SDC is vulnerable.
Please see K86488846: Sudo vulnerability CVE-2021-3156 for more information.
Updated: 2021-02-04
Statement Date: January 26, 2021
CVE-2021-3156 | Affected |
---|
We have not received a statement from the vendor.
Updated: 2021-02-04
Statement Date: January 26, 2021
CVE-2021-3156 | Affected |
---|
We have not received a statement from the vendor.
Notified: 2021-02-04 Updated: 2021-04-07
Statement Date: April 06, 2021
CVE-2021-3156 | Affected |
---|
We have not received a statement from the vendor.
Notified: 2021-02-04 Updated: 2021-02-05
Statement Date: February 04, 2021
CVE-2021-3156 | Affected |
---|
HardenedBSD’s sudo port has been updated and can be used to mitigate affected systems. Systems that have updated their sudo port/package are no longer vulnerable.
Notified: 2021-02-04 Updated: 2021-02-10
Statement Date: February 10, 2021
CVE-2021-3156 | Affected |
---|
SmartOS gets its sudo binary from pkgsrc(1). pkgsrc’s main feed has updated sudo binaries, and one merely need pkgin upgrade
in any affected SmartOS zone to get the fixed version.
Notified: 2021-02-04 Updated: 2021-03-04
Statement Date: March 04, 2021
CVE-2021-3156 | Affected |
---|
Juniper SIRT has confirmed that Sudo is not supplied with JUNOS/FreeBSD, hence these are not affected.
On Juniper platforms which are hosted on Wind River Linux (WRL) instances, the WRL instance contains the vulnerable version of Sudo, but only within the WRL OS. To exploit this vulnerability on Wind River Linux (WRL), authenticated users with Junos shell access, would first need to switch to a root account and then login to WRL OS. The vulnerability is contained within the WRL instance for which the Junos user would already have root privileges.
Security Incident Response Team Juniper Networks
Updated: 2021-02-04
Statement Date: February 03, 2021
CVE-2021-3156 | Affected |
---|
We have not received a statement from the vendor.
Updated: 2021-02-04
Statement Date: January 26, 2021
CVE-2021-3156 | Affected |
---|
We have not received a statement from the vendor.
Updated: 2021-02-04
Statement Date: January 27, 2021
CVE-2021-3156 | Affected |
---|
We have not received a statement from the vendor.
Updated: 2021-02-04
Statement Date: January 26, 2021
CVE-2021-3156 | Affected |
---|
We have not received a statement from the vendor.
Notified: 2021-02-04 Updated: 2021-02-05
Statement Date: February 05, 2021
CVE-2021-3156 | Affected |
---|
SUSE has already provided fixes for the affected supported products. Users should patch their systems. SUSE Linux Enterprise Server 12 and SUSE Linux Enterprise Server 15 products are affected. SUSE Linux Enterprise Server 11 products are not affected.
Notified: 2021-02-04 Updated: 2021-02-24
Statement Date: February 23, 2021
CVE-2021-3156 | Affected |
---|
We have not received a statement from the vendor.
Updated: 2021-02-04
Statement Date: January 26, 2021
CVE-2021-3156 | Affected |
---|
We have not received a statement from the vendor.
Notified: 2021-02-04 Updated: 2021-02-08
Statement Date: February 08, 2021
CVE-2021-3156 | Affected |
---|
“Heap-based buffer overflow in sudo” affects the Wind River Linux product.
Notified: 2021-02-04 Updated: 2021-02-08
Statement Date: February 05, 2021
CVE-2021-3156 | Not Affected |
---|
Android is not impacted as it does not have SUDO.
Notified: 2021-02-04 Updated: 2021-02-08
Statement Date: February 08, 2021
CVE-2021-3156 | Not Affected |
---|
While the base FreeBSD installation does not include sudo and is therefore not directly affected by this vulnerability, the FreeBSD Project recognises that sudo is a very popular package for users to install on FreeBSD.
Users can install sudo on FreeBSD using ports or binary packages. The sudo port was updated to 1.9.5p2 on 2021-01-26 at 20:15:31 (main) and on 2021-01-26 20:40:57 (2021Q1 quarterly). Binary packages are available for all tier-1 supported platforms (amd64, i386, aarch64) and several tier-2 supported platforms.
Notified: 2021-02-04 Updated: 2021-02-05
Statement Date: February 04, 2021
CVE-2021-3156 | Not Affected |
---|
We have not received a statement from the vendor.
Notified: 2021-02-04 Updated: 2021-02-10
Statement Date: February 10, 2021
CVE-2021-3156 | Not Affected |
---|
illumos itself does not have sudo in its source. Illumos distros, however, do.
A NOTE: base illumos has the RBAC/profile-based pfexec(1) family of commands that are an alternative for sudo.
SmartOS: Use pkgin upgrade
on any zones that have sudo installed.
OmniOSce and OpenIndiana (both use the IPS package system): Use pkg update
to obtain the latest sudo if it’s installed.
Dilos: Is fixed in update https://bitbucket.org/dilos/du2/commits/ca5129c54c84d7b2fd75d17e465e970435018f55 - a Debian-style update will install it.
Tribblix: If sudo is installed, zap refresh && zap update sudo
Notified: 2021-02-04 Updated: 2021-03-29
Statement Date: March 26, 2021
CVE-2021-3156 | Not Affected |
---|
We have not received a statement from the vendor.
Notified: 2021-02-04 Updated: 2021-02-15
Statement Date: February 12, 2021
CVE-2021-3156 | Not Affected |
---|
We have not received a statement from the vendor.
Notified: 2021-02-04 Updated: 2021-04-05
Statement Date: April 05, 2021
CVE-2021-3156 | Not Affected |
---|
We have not received a statement from the vendor.
Notified: 2021-02-04 Updated: 2021-04-26
Statement Date: April 25, 2021
CVE-2021-3156 | Not Affected |
---|
Not affected.
Notified: 2021-02-04 Updated: 2021-02-05
Statement Date: February 05, 2021
CVE-2021-3156 | Not Affected |
---|
The Zephyr project is an embedded RTOS, and as such, does not directly have the capability to run sudo. However, there are few instances of sudo in the project scripts and documentation.
Notified: 2021-02-04 Updated: 2021-02-05
Statement Date: February 05, 2021
CVE-2021-3156 | Not Affected |
---|
We have not received a statement from the vendor.
Notified: 2021-02-04 Updated: 2021-02-04 CVE-2021-3156 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2021-02-04 Updated: 2021-02-04 CVE-2021-3156 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2021-02-04 Updated: 2021-02-04 CVE-2021-3156 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2021-02-04 Updated: 2021-02-04 CVE-2021-3156 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2021-02-04 Updated: 2021-02-04 CVE-2021-3156 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2021-02-04 Updated: 2021-02-04 CVE-2021-3156 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2021-02-04 Updated: 2021-02-04 CVE-2021-3156 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2021-02-04 Updated: 2021-02-04 CVE-2021-3156 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2021-02-04 Updated: 2021-02-04 CVE-2021-3156 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2021-02-04 Updated: 2021-02-04 CVE-2021-3156 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2021-02-04 Updated: 2021-02-04 CVE-2021-3156 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2021-02-04 Updated: 2021-02-04 CVE-2021-3156 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2021-02-04 Updated: 2021-02-04 CVE-2021-3156 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2021-02-04 Updated: 2021-02-04 CVE-2021-3156 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2021-02-04 Updated: 2021-02-04 CVE-2021-3156 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2021-02-04 Updated: 2021-02-04 CVE-2021-3156 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2021-02-04 Updated: 2021-02-04 CVE-2021-3156 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2021-02-04 Updated: 2021-02-04 CVE-2021-3156 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2021-02-04 Updated: 2021-02-04 CVE-2021-3156 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2021-02-04 Updated: 2021-02-04 CVE-2021-3156 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2021-02-04 Updated: 2021-02-04 CVE-2021-3156 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2021-02-04 Updated: 2021-02-04 CVE-2021-3156 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2021-02-04 Updated: 2021-02-04 CVE-2021-3156 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2021-02-04 Updated: 2021-02-04 CVE-2021-3156 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2021-02-04 Updated: 2021-02-05
Statement Date: February 05, 2021
CVE-2021-3156 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2021-02-04 Updated: 2021-02-04 CVE-2021-3156 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2021-02-04 Updated: 2021-02-04 CVE-2021-3156 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2021-02-04 Updated: 2021-02-04 CVE-2021-3156 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2021-02-04 Updated: 2021-02-04 CVE-2021-3156 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2021-02-04 Updated: 2021-02-04 CVE-2021-3156 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2021-02-04 Updated: 2021-02-04 CVE-2021-3156 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2021-02-04 Updated: 2021-02-04 CVE-2021-3156 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2021-02-04 Updated: 2021-02-04 CVE-2021-3156 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2021-02-04 Updated: 2021-02-04 CVE-2021-3156 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2021-02-04 Updated: 2021-02-04 CVE-2021-3156 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2021-02-04 Updated: 2021-02-04 CVE-2021-3156 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2021-02-04 Updated: 2021-02-04 CVE-2021-3156 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2021-02-04 Updated: 2021-02-04 CVE-2021-3156 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2021-02-04 Updated: 2021-02-04 CVE-2021-3156 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2021-02-04 Updated: 2021-02-04 CVE-2021-3156 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2021-02-04 Updated: 2021-02-04 CVE-2021-3156 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2021-02-04 Updated: 2021-02-04 CVE-2021-3156 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2021-02-04 Updated: 2021-02-04 CVE-2021-3156 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2021-02-04 Updated: 2021-02-04 CVE-2021-3156 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2021-02-04 Updated: 2021-02-04 CVE-2021-3156 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2021-02-04 Updated: 2021-03-09
Statement Date: March 09, 2021
CVE-2021-3156 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2021-02-04 Updated: 2021-02-04 CVE-2021-3156 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2021-02-04 Updated: 2021-02-04 CVE-2021-3156 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2021-02-04 Updated: 2021-02-04 CVE-2021-3156 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2021-02-04 Updated: 2021-02-04 CVE-2021-3156 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2021-02-04 Updated: 2021-02-04 CVE-2021-3156 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2021-02-04 Updated: 2021-02-04 CVE-2021-3156 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2021-02-04 Updated: 2021-02-04 CVE-2021-3156 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2021-02-04 Updated: 2021-02-04 CVE-2021-3156 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2021-02-04 Updated: 2021-02-04 CVE-2021-3156 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2021-02-04 Updated: 2021-02-04 CVE-2021-3156 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2021-02-04 Updated: 2021-02-04 CVE-2021-3156 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2021-02-04 Updated: 2021-02-04 CVE-2021-3156 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2021-02-04 Updated: 2021-02-04 CVE-2021-3156 | Unknown |
---|
We have not received a statement from the vendor.
Notified: 2021-02-04 Updated: 2021-02-04 CVE-2021-3156 | Unknown |
---|
We have not received a statement from the vendor.
View all 87 vendors __View less vendors __
CVE IDs: | CVE-2021-3156 |
---|---|
Date Public: | 2021-01-26 Date First Published: |
7.8 High
CVSS3
Attack Vector
LOCAL
Attack Complexity
LOW
Privileges Required
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality Impact
HIGH
Integrity Impact
HIGH
Availability Impact
HIGH
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
7.2 High
CVSS2
Access Vector
LOCAL
Access Complexity
LOW
Authentication
NONE
Confidentiality Impact
COMPLETE
Integrity Impact
COMPLETE
Availability Impact
COMPLETE
AV:L/AC:L/Au:N/C:C/I:C/A:C
0.971 High
EPSS
Percentile
99.7%