CVE-2025-8792
📋 TL;DR
This vulnerability in LitmusChaos Litmus allows attackers to bypass server-side security controls through client-side manipulation. It affects LitmusChaos Litmus versions up to 3.19.0, enabling remote exploitation of security enforcement weaknesses.
💻 Affected Systems
- LitmusChaos Litmus
📦 What is this software?
Litmus by Litmuschaos
⚠️ Risk & Real-World Impact
Worst Case
Attackers could bypass critical security controls, potentially gaining unauthorized access to chaos engineering experiments or underlying infrastructure.
Likely Case
Limited security bypass allowing manipulation of chaos experiment parameters beyond intended scope.
If Mitigated
Minimal impact with proper network segmentation and access controls limiting exposure.
🎯 Exploit Status
Exploit details are publicly disclosed but require understanding of LitmusChaos architecture and access to the system.
🛠️ Fix & Mitigation
✅ Official Fix
Patch Version: Version 3.20.0 or later
Vendor Advisory: https://github.com/litmuschaos/litmus
Restart Required: Yes
Instructions:
1. Update LitmusChaos to version 3.20.0 or later. 2. Restart all LitmusChaos components. 3. Verify the update was successful.
🔧 Temporary Workarounds
Network Segmentation
allRestrict network access to LitmusChaos components to only trusted sources.
Access Control Enforcement
allImplement strict RBAC and ensure all security controls are enforced server-side.
🧯 If You Can't Patch
- Implement strict network segmentation and firewall rules to limit access to LitmusChaos.
- Enhance monitoring and alerting for unusual client-side manipulation attempts.
🔍 How to Verify
Check if Vulnerable:
Check LitmusChaos version using 'kubectl get pods -n litmus -o jsonpath="{.items[*].spec.containers[*].image}"' and look for versions <= 3.19.0.Check Version:
kubectl get pods -n litmus -o jsonpath="{.items[*].spec.containers[*].image}" | grep -o 'litmuschaos/litmus:[0-9.]*'Verify Fix Applied:
Verify version is 3.20.0 or later using the same command and ensure no components are running vulnerable versions.📡 Detection & Monitoring
Log Indicators:
- Unusual client-side requests bypassing expected security controls
- Authentication or authorization failures followed by successful operations
Network Indicators:
- Unexpected API calls to LitmusChaos endpoints from unauthorized sources
SIEM Query:
source="litmus*" AND (event="security_bypass" OR event="unauthorized_access")