CyberSecBulletin
CVE-2020-0796Exploited in the wildNVD status: Analyzed

Microsoft SMBv3 Remote Code Execution

CVE-2020-0796 is a critical-severity improper restriction of operations within the bounds of a memory buffer vulnerability in Windows 10 Version 1903 for 32-bit Systems from Microsoft, with a CVSS 3.1 base score of 10.0 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. CISA added it to the Known Exploited Vulnerabilities catalogue on February 10, 2022, which means attacks have been observed in the wild, including in ransomware campaigns.

Patch now

Attackers are already exploiting this vulnerability, according to CISA.

What to do

  1. Check which version of Windows 10 Version 1903 for 32-bit Systems you run against the affected versions below, and install the vendor's latest release.
  2. CISA's required action: Apply updates per vendor instructions.
  3. Read the advisory on portal.msrc.microsoft.com for workarounds and exact fixed builds.
  4. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.

Affected products and versions

VendorProductAffected versionsFixed in
MicrosoftWindows 10 Version 1903 for 32-bit SystemsNot specified in the recordNot stated
MicrosoftWindows 10 Version 1903 for x64-based SystemsNot specified in the recordNot stated
MicrosoftWindows 10 Version 1903 for ARM64-based SystemsNot specified in the recordNot stated
MicrosoftWindows Server, version 1903 (Server Core installation)Not specified in the recordNot stated
MicrosoftWindows 10 Version 1909 for 32-bit SystemsNot specified in the recordNot stated
MicrosoftWindows 10 Version 1909 for x64-based SystemsNot specified in the recordNot stated
MicrosoftWindows 10 Version 1909 for ARM64-based SystemsNot specified in the recordNot stated
MicrosoftWindows Server, version 1909 (Server Core installation)Not specified in the recordNot stated
MicrosoftWindows 10 1903Not specified in the recordNot stated
MicrosoftWindows 10 1909Not specified in the recordNot stated
MicrosoftWindows Server 1903Not specified in the recordNot stated
MicrosoftWindows Server 1909Not specified in the recordNot stated

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
NoneNo account or login is needed.
User interaction
NoneNo action by a victim is required.
Scope
ChangedThe attack can reach beyond the vulnerable component into other systems.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H. Scored by NVD.

Scoring systemScoreSeverityScored by
CVSS 3.110.0CriticalNVD
CVSS 3.110.0CriticalCISA (ADP)
CVSS 2.07.5HighNVD

Official description

A remote code execution vulnerability exists in the way that the Microsoft Server Message Block 3.1.1 (SMBv3) protocol handles certain requests, aka 'Windows SMBv3 Client/Server Remote Code Execution Vulnerability'.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Improper Restriction of Operations within the Bounds of a Memory Buffer

The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary.

How developers prevent this class of flaw

  • Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, many languages that perform their own memory management, such as Java and Perl, are not subject to buffer overflows. Other languages, such as Ada and C#, typically provide overflow protection, but the protection can be disabled by the programmer. Be wary that a language's interface to native code may still be subject to overflows, even if the language itself is theoretically safe.
  • Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. Examples include the Safe C String Library (SafeStr) by Messier and Viega, and the Strsafe.h library from Microsoft. These libraries provide safer versions of overflow-prone string-handling functions.
  • Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking. D3-SFCV (Stack Frame Canary Validation) from D3FEND discusses canary-based detection in detail.

More Improper Restriction of Operations within the Bounds of a Memory Buffer vulnerabilities (CWE-119)

Timeline

  1. CVE record published.
  2. Added to CISA's Known Exploited Vulnerabilities catalogue.
  3. Deadline for US federal agencies to remediate, set by CISA.
  4. CISA published its SSVC assessment (exploitation: active, automatable: yes, technical impact: total).
  5. Record last changed materially (score, affected products, status or references).

References

Technical write-ups (may include proof of concept)

Other vulnerabilities in Windows 10 Version 1903 for 32-bit Systems

All Windows 10 Version 1903 for 32-bit Systems vulnerabilities

Recent Improper Restriction of Operations within the Bounds of a Memory Buffer vulnerabilities

Spotted an error? Tell us.