CVE-2025-12381
BaseFortify
Publication date: 2025-12-09
Last updated on: 2025-12-17
Assigner: AlgoSec
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| algosec | firewall_analyzer | a33.10 |
| algosec | firewall_analyzer | 4.0 |
| algosec | firewall_analyzer | a33.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-269 | The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is an Improper Privilege Management issue in AlgoSec Firewall Analyzer on Linux (64 bit). It allows a local user who has command line access to escalate their privileges by exploiting parameters of a command that is approved in the sudoers file. Essentially, the user can gain higher privileges than intended by abusing how command parameters are handled.
How can this vulnerability impact me? :
This vulnerability can allow a local user to escalate their privileges on the affected system, potentially gaining unauthorized access to sensitive functions or data. This could lead to unauthorized changes, data exposure, or further compromise of the system's security.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
You can detect this vulnerability by checking the sudoers file for misconfigured entries related to AlgoSec Firewall Analyzer commands that allow parameter injection. Specifically, look for sudoers entries permitting commands without proper parameter restrictions. For example, you can run: sudo -l -U <username> to list allowed sudo commands for a user and inspect if any commands are vulnerable. Additionally, verify the installed version of AlgoSec Firewall Analyzer to see if it is A33.0 (build below 330) or A33.10 (build below 230), which are affected versions. [1]
What immediate steps should I take to mitigate this vulnerability?
The immediate mitigation step is to upgrade AlgoSec Firewall Analyzer to the fixed versions: A33.0 build 330 or above, or A33.10 build 230 or above, where the sudoers misconfigurations have been corrected. Until the upgrade is applied, restrict local user access to the command line and review sudoers entries to remove or limit commands that allow parameter injection. [1]