LlamaFarm Insecure Default Configuration and Unauthenticated API Access

LlamaFarm versions through 0.0.34 suffer from an insecure default configuration that exposes the internal FastAPI management server to all network interfaces by binding it to 0.0.0.0 on port 14345. Additionally, the lf command-line interface fails to honor host overrides, preventing administrators from restricting access to the local loopback interface. This vulnerability allows network-adjacent attackers to interact directly with the project and dataset management API without any form of authentication. By sending crafted HTTP requests, an attacker can exfiltrate sensitive provider API keys stored within the application, modify existing projects, trigger unauthorized data ingestion processes, or perform destructive actions such as the irreversible deletion of projects. This exposure creates significant risk for organizations using LlamaFarm in environments accessible from broader network segments.

Impact

Successful exploitation allows unauthorized third parties to gain full control over the LlamaFarm application. The impact includes the exfiltration of sensitive third-party API credentials, the potential poisoning or unauthorized modification of datasets, and data loss due to the ability to delete projects. Given the nature of project management APIs, this could result in significant operational disruption and compromise of upstream services authenticated by the exfiltrated keys.

Recommendation

• Upgrade LlamaFarm to the latest version immediately to remediate the default binding configuration.
• Implement network segmentation to ensure port 14345 is not reachable from untrusted network segments.
• Apply host-based firewall rules to explicitly restrict access to port 14345 to known authorized management IP addresses.
• Audit logs for the LlamaFarm API endpoint for any unauthorized POST, PUT, or DELETE requests from unexpected source IP addresses.