BullWall Server Intrusion Protection (SIP) services are initialized after login services during system startup. A local, authenticated attacker can log in after boot and before SIP MFA is running. The SIP services do not retroactively enforce MFA or disconnect sessions that were not subject to SIP MFA. Versions 4.6.0.0, 4.6.0.6, 4.6.0.7, and 4.6.1.4 are affected. Other versions mayy also be affected. BullWall plans to improve detection method documentation.
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XBullwall Server Intrusion Protection
APPBullwall4.6.0.04.6.0.64.6.0.74.6.1.4
Related vulnerabilities
BullWall Server Intrusion Protection has a noticeable configuration-dependent delay before the MFA check for R...
BullWall Ransomware Containment supports configurable file and directory exclusions such as '$RECYCLE.BIN' to ...
BullWall Ransomware Containment may not always detect an encrypted file. This issue affects a specific file in...
BullWall Ransomware Containment considers the number of files modified to trigger detection. An authenticated ...