Virsec Security Platform (VSP) leverages the patented Trusted Execution™ technology to protect high-value enterprise applications deployed in data center or on public and hybrid clouds, from highly sophisticated attacks including memory corruption, code injection, credential theft, supply chain and other sophisticated attacks. VSP effectively creates and enforces guardrails around the application as it executes. These guardrails ensure that applications only perform as intended and restrain bad actors from corrupting memory as a precursor to hijacking control of the application and subsequent stealing or destroying high-value enterprise data.
DATE OF RELEASEDATE OF RELEASE
3/11/2022
FIXESFIXES
|
Defect ID |
Description |
|
V2-22143 |
HMM service is not coming up after "yum update && yum upgrade" due to a critical memory leak |
|
V2-22141 |
FSExclusionList is optimized to reduce the time taken for the scan |
|
V2-22140 |
Kafka and Zookeeper CMS services need JNDI mitigation for log4j |
Table – VSP 2.3.2 Fixes
KNOWN ISSUESKNOWN ISSUES
|
Category |
Description |
Known Issue/ Caveat |
|
Host Monitoring |
||
|
Windows library issue |
In Windows, VSP host monitoring does not suspend already running processes that have non-whitelisted libraries loaded into it |
Known Issue |
|
Linux HMM agent limitation |
In Linux, VSP host monitoring injects its own HMM agent into every running process. The HMM agent expects a specific version of glibc. If the application loads its own custom glibc version that is not compatible with the HMM agent, the HMM agent may not load correctly causing some application issues |
Limitation |
|
Windows application execution inconsistency |
In Windows, an application can be started with or without its .exe extension. Since VSP host monitoring analyzes the commandline as is, running python.exe vs python may result in different detections |
Limitation |
Table – Known Issues