Litmus: Incorrect Privilege Assignment
CVE-2025-8797 is a high-severity incorrect privilege assignment vulnerability in Litmus from LitmusChaos, with a CVSS 3.1 base score of 8.8 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. Affected Litmus versions: 3.0; 3.1; 3.2, and others listed below. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.63% chance of exploitation within 30 days, higher than 51% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Check which version of Litmus you run against the affected versions below, and install the vendor's latest release.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| LitmusChaos | Litmus | 3.0; 3.1; 3.2; 3.3; 3.4; 3.5; 3.6; 3.7; and 12 more ranges | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 4.0 | 2.1 | Low | CNA (vuldb.com) |
| CVSS 3.1 | 6.3 | Medium | CNA (vuldb.com) |
| CVSS 3.1 | 8.8 | High | NVD |
| CVSS 2.0 | 6.5 | Medium | CNA (vuldb.com) |
Official description
A vulnerability was found in LitmusChaos Litmus up to 3.19.0 and classified as critical. This issue affects some unknown processing of the component LocalStorage Handler. The manipulation leads to permission issues. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Incorrect Privilege Assignment
A product incorrectly assigns a privilege to a particular actor, creating an unintended sphere of control for that actor.
How developers prevent this class of flaw
- Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
- Run your code using the lowest privileges that are required to accomplish the necessary tasks. If possible, create isolated accounts with limited privileges that are only used for a single task. That way, a successful attack will not immediately give the attacker access to the rest of the software or its environment. For example, database applications rarely need to run as the database administrator, especially in day-to-day operations.
More Incorrect Privilege Assignment vulnerabilities (CWE-266)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: poc, automatable: no, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Third-party and government advisories
- vuldb.com/?id.319325Third Party Advisory, VDB Entry
- vuldb.com/?submit.625991Third Party Advisory, VDB Entry
Technical write-ups (may include proof of concept)
- github.com/MaiqueSilva/VulnDB/blob/main/readme07.mdExploit, Third Party Advisory
Other references
- vuldb.com/?ctiid.319325Permissions Required, VDB Entry
Other vulnerabilities in Litmus
- 7.1 High severity
- 9.9 Critical severity
- 7.8 High severity
Recent Incorrect Privilege Assignment vulnerabilities
- 7.0 High severity
- 7.0 High severity
- 8.8 High severity
- 7.2 High severity
- 9.8 Critical severity
- 7.2 High severity
Spotted an error? Tell us.