CVE-2024-6107

9.6 CRITICAL

📋 TL;DR

This authentication bypass vulnerability in MAAS allows attackers to execute unauthorized RPC commands without proper credentials. Systems running vulnerable versions of MAAS are affected, potentially enabling complete system compromise. The vulnerability stems from insufficient verification of client authentication.

💻 Affected Systems

Products:
  • MAAS (Metal as a Service)
Versions: Versions prior to the fix in MAAS snap updates
Operating Systems: Ubuntu (primary), Linux distributions running MAAS
Default Config Vulnerable: ⚠️ Yes
Notes: All MAAS deployments using vulnerable versions are affected regardless of configuration.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete compromise of MAAS-managed infrastructure, allowing attacker to provision/control servers, access sensitive data, and pivot to other systems.

🟠

Likely Case

Unauthorized access to MAAS functionality, enabling attacker to deploy malicious systems, modify configurations, or exfiltrate sensitive infrastructure data.

🟢

If Mitigated

Limited impact if network segmentation restricts MAAS access and strong authentication controls are in place.

🌐 Internet-Facing: HIGH - MAAS instances exposed to internet are extremely vulnerable to exploitation.
🏢 Internal Only: HIGH - Even internally, this authentication bypass allows lateral movement and privilege escalation.

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: LIKELY
Unauthenticated Exploit: ⚠️ Yes
Complexity: LOW

Authentication bypass vulnerabilities are frequently weaponized due to their simplicity and high impact.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Latest MAAS snap updates addressing the vulnerability

Vendor Advisory: https://bugs.launchpad.net/maas/+bug/2069094

Restart Required: Yes

Instructions:

1. Update MAAS snap: 'sudo snap refresh maas' 2. Restart MAAS services: 'sudo systemctl restart snap.maas.*' 3. Verify update with 'snap info maas'

🔧 Temporary Workarounds

Network Isolation

linux

Restrict network access to MAAS API endpoints

sudo ufw deny from any to <maas-ip> port 5240
sudo iptables -A INPUT -p tcp --dport 5240 -j DROP

API Access Restriction

linux

Limit MAAS API access to trusted IPs only

Edit MAAS configuration to restrict API endpoints to internal network

🧯 If You Can't Patch

  • Implement strict network segmentation to isolate MAAS from untrusted networks
  • Deploy additional authentication layer (reverse proxy with auth) in front of MAAS API

🔍 How to Verify

Check if Vulnerable:

Check MAAS version: 'snap info maas | grep installed' and compare with patched versions in advisory

Check Version:

snap info maas | grep installed

Verify Fix Applied:

Verify updated version and test authentication requirements for RPC commands

📡 Detection & Monitoring

Log Indicators:

  • Unauthorized RPC command attempts
  • Authentication failures followed by successful RPC commands
  • Unusual API access patterns

Network Indicators:

  • RPC traffic from unauthorized sources
  • Unusual volume of API requests to MAAS endpoints

SIEM Query:

source="maas.log" AND ("authentication failure" OR "unauthorized access") AND "RPC command"

🔗 References

📤 Share & Export