whatsapp-mcp Unauthenticated API Allows Message Sending and Arbitrary File Read (CVE-2024-48555)

Vulnerability Overview Vulnerability Name: Unauthenticated bridge API allows message sending and arbitrary file exfiltration Vulnerability ID: GHSA-7j9-4qqq-4xc4 Publication Date: May 17 Severity: High (7.7 / 10) Impact Scope Affected Versions: <= 0.2.0 Fixed Version: 0.2.1 Impact Description: - Local processes can send WhatsApp messages as the bridged user. - The same caller can read any user-readable file (e.g., SSH private keys, browser session data, source code, attachments, etc.) and exfiltrate it. - Remote attackers can trigger the same actions via DNS rebinding, bypassing Host header validation. Remediation Fixed Version: Upgrade to and the corresponding Docker image/release artifacts. Fix Details: - Introduced Bearer token authentication. - Added Host header whitelist validation to prevent DNS rebinding. - Restricted to the configured directory, rejecting absolute paths and path traversal sequences. Additional Information CWEs: - CWE-306: Missing Authentication for Critical Function - CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') - CWE-346: The software does not properly verify that the source of data or communication is valid CVSS v3 Base Metrics: - Attack vector: Local - Attack complexity: Low - Privileges required: None - User interaction: None - Scope: Unchanged - Confidentiality: High - Integrity: High - Availability: None CVE ID: CVE-2024-48555 Credits: Poker71 References Reporter: Paul van der Klooster (@Poker71) Fix Release: https://github.com/verygoodplugins/whatsapp-mcp/releases/tag/v0.2.1 Security Policy: https://github.com/verygoodplugins/whatsapp-mcp/blob/main/SECURITY.md

Goal Reached Thanks to every supporter — we hit 100%!

whatsapp-mcp Unauthenticated API Allows Message Sending and Arbitrary File Read (CVE-2024-48555)

More from this source