CVE-2025-8797

6.3 MEDIUM

📋 TL;DR

A critical permission vulnerability in LitmusChaos Litmus up to version 3.19.0 allows remote attackers to exploit the LocalStorage Handler component. This could lead to unauthorized access or privilege escalation in LitmusChaos deployments. Organizations using LitmusChaos for chaos engineering are affected.

💻 Affected Systems

Products:
  • LitmusChaos Litmus
Versions: up to 3.19.0
Operating Systems: All platforms running LitmusChaos
Default Config Vulnerable: ⚠️ Yes
Notes: All deployments using the vulnerable LocalStorage Handler component are affected regardless of configuration.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Remote attackers could gain administrative control over the LitmusChaos platform, potentially compromising the entire chaos engineering infrastructure and adjacent systems.

🟠

Likely Case

Attackers could manipulate chaos experiments, disrupt testing environments, or gain unauthorized access to sensitive chaos engineering data.

🟢

If Mitigated

With proper network segmentation and access controls, impact would be limited to the LitmusChaos environment only.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

Public PoC: ⚠️ Yes
Weaponized: UNKNOWN
Unauthenticated Exploit: ✅ No
Complexity: MEDIUM

Exploit details have been publicly disclosed but require some knowledge of LitmusChaos architecture.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 3.20.0 or later

Vendor Advisory: https://github.com/litmuschaos/litmus/releases

Restart Required: Yes

Instructions:

1. Check current LitmusChaos version. 2. Upgrade to version 3.20.0 or later. 3. Restart LitmusChaos components. 4. Verify the upgrade was successful.

🔧 Temporary Workarounds

Network Isolation

all

Restrict network access to LitmusChaos deployment to trusted IPs only

Use network policies or firewall rules to limit access to LitmusChaos services

Disable LocalStorage Handler

all

If not required, disable the vulnerable LocalStorage Handler component

Modify LitmusChaos configuration to disable LocalStorage Handler functionality

🧯 If You Can't Patch

  • Implement strict network segmentation to isolate LitmusChaos from critical systems
  • Enable detailed audit logging and monitor for suspicious LocalStorage Handler activity

🔍 How to Verify

Check if Vulnerable:

Check LitmusChaos version: kubectl get pods -n litmus -o jsonpath='{.items[*].spec.containers[*].image}' | grep -o 'litmuschaos/litmus:[0-9.]*'

Check Version:

kubectl get pods -n litmus -o jsonpath='{.items[*].spec.containers[*].image}'

Verify Fix Applied:

Confirm version is 3.20.0 or later and test LocalStorage Handler functionality

📡 Detection & Monitoring

Log Indicators:

  • Unauthorized access attempts to LocalStorage Handler
  • Unusual permission changes in LitmusChaos logs

Network Indicators:

  • Unexpected remote connections to LitmusChaos LocalStorage endpoints

SIEM Query:

source="litmus-chaos" AND (event="permission_violation" OR event="unauthorized_access")

🔗 References

📤 Share & Export