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
11/11/2022
FIXESFIXES
|
Defect ID |
Description |
|
SUPP-275 |
Cannot delete OR disable Scheduled Report item that has generated report entries |
|
SUPP-391 |
False Positive incidents are reported to CMS due to delay in registering for RL check |
|
SUPP-411 |
RL re-validation did not remove a malicious file from whitelist that was auto-allowlisted initially (zero day) |
|
SUPP-465 |
The field "Updated By" for all system alerts related to Maintenance mode displays the value "SYSTEM" |
|
SUPP-479 |
The Application Landing page displays error |
|
SUPP-502 |
Errors encountered while viewing AE Stats using VSP-CLI |
|
SUPP-508 |
DotNet Application does not move to normal state |
|
SUPP-516 |
Stored XSS attacks for legitimate payload is blocking application |
|
SUPP-520 |
Tomcat Application crashed due to insufficient memory for the JRE |
|
SUPP-526 |
High resource usage is observed after enabling Detect mode on a host |
|
SUPP-546 |
Server Connectivity Issues encountered after VSP Probe Upgrade |
|
SUPP-555 |
Password-protected probe installation becomes non-responsive indefinitely |
Table – VSP 2.4.7 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