T1021.005_vnc

T1021.005 VNC

Sub-technique of: T1021

High-Level Description

Adversaries may use Valid Accounts to remotely control machines using Virtual Network Computing (VNC). VNC is a platform-independent desktop sharing system that uses the RFB (“remote framebuffer”) protocol to enable users to remotely control another computer’s display by relaying the screen, mouse, and keyboard inputs over the network.

VNC differs from Remote Desktop Protocol as VNC is screen-sharing software rather than resource-sharing software. By default, VNC uses the system's authentication, but it can be configured to use credentials specific to VNC.

Adversaries may abuse VNC to perform malicious actions as the logged-on user such as opening documents, downloading files, and running arbitrary commands. An adversary could use VNC to remotely control and monitor a system to collect data and information to pivot to other systems within the network. Specific VNC libraries/implementations have also been susceptible to brute force attacks and memory usage exploitation.

Kill Chain Phase

• Lateral Movement (TA0008)

Platforms: Linux, Windows, macOS

What to Check

• Identify if VNC technique is applicable to target environment
• Check Linux systems for indicators of VNC
• Check Windows systems for indicators of VNC
• Check macOS systems for indicators of VNC
• Verify mitigations are bypassed or absent (4 known mitigations)
• Assess detection coverage (1 detection strategies)

How to Test

Atomic Red Team Tests

The following tests are from Atomic Red Team and provide actionable ways to test this technique:

Atomic Test 1: Enable Apple Remote Desktop Agent

ARD leverages a blend of protocols, including VNC to send the screen and control buffers and SSH for secure file transfer. Adversaries can abuse ARD to gain remote code execution and perform lateral movement.

References: https://www.mandiant.com/resources/blog/leveraging-apple-remote-desktop-for-good-and-evil

Supported Platforms: macos Elevation Required: Yes

sudo /System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Resources/kickstart -activate -configure -allowAccessFor -allUsers -privs -all -quiet

Manual Testing

If Atomic Red Team tests are not applicable, manually verify the technique by:

1. Identify Attack Surface: Determine if the target environment is susceptible to VNC by examining the target platforms (Linux, Windows, macOS).

2. Assess Existing Defenses: Review whether mitigations for T1021.005 are in place. If defenses are absent or misconfigured, this technique may be exploitable.

3. Execute Test: Use tools and methods described in the MITRE ATT&CK page and external references below.

Remediation Guide

M1042 Disable or Remove Feature or Program

Uninstall any VNC server software where not required.

M1037 Filter Network Traffic

VNC defaults to TCP ports 5900 for the server, 5800 for browser access, and 5500 for a viewer in listening mode. Filtering or blocking these ports will inhibit VNC traffic utilizing default ports.

M1047 Audit

Inventory workstations for unauthorized VNC server software.

M1033 Limit Software Installation

Restrict software installation to user groups that require it. A VNC server must be manually installed by the user or adversary.

Detection

Behavioral Detection of Unauthorized VNC Remote Control Sessions

Risk Assessment

CWE Categories

References

• Attacking VNC Servers PentestLab
• MacOS VNC software for Remote Desktop
• Havana authentication bug
• macOS root VNC login without authentication
• Offensive Security VNC Authentication Check
• Gnome Remote Desktop grd-settings
• Gnome Remote Desktop gschema
• Apple Unified Log Analysis Remote Login and Screen Sharing
• VNC Vulnerabilities
• The Remote Framebuffer Protocol
• VNC Authentication
• Hijacking VNC
• Atomic Red Team - T1021.005
• MITRE ATT&CK - T1021.005