This article includes a list the new features and bug fixes that are included in Lucent Sky AVM 4.2, as well as known issues of this release.
For more information about this release, visit the blog post Lucent Sky AVM 4.2 released.
Updates in Lucent Sky AVM 4.2
-
Second-generation source code analysis engine (first phase) - The second-generation source code analysis engine is an overhaul of the source code flow analysis engine and the contextual analysis engine. The entire upgrade is scheduled to be included in v4.2 and the two following releases. In the first phase, the primary focus is performance. Users should expect a 25% analysis performance improvement on most web and server applications, and a 45% boost on most mobile applications.
-
New encoding detection algorithm - Automatic encoding detection is a widely used feature among our East Asian users, which often have to handle source code with multiple encodings such as Big5, JIS, and multiple flavors of Unicode. The new encoding detection algorithm greatly improves the accuracy and performance of encoding detection, especially on complex applications using multiple encodings.
-
Regionally-customized identification rules - Over the past several months, we have received customer feedback about supporting security requirements and best-practices that are unique to each markets. Starting with Lucent Sky AVM 4.2, customers will have the option to have a second built-in rule package that is regionally-customized. To learn more about opt-in of the regionally-customized rule package, contact Lucent Sky support.
-
Bug fixes - Several bugs were fixed in this release, including a bug affecting source code and configuration analysis rules, and a bug causing low-confidence Instant Fixes not displayed correctly on the web UI.
List of fixes included in Lucent Sky AVM 4.2
Source code and configuration analysis rules in a custom rule package are ignored
If a custom rule package includes rules for source code and configuration analysis, these rules are ignored. Other rules, such as those for binary analysis and for mitigation are not affected.
This issue has been resolved in Lucent Sky AVM 4.2.
Known issues of Lucent Sky AVM 4.2
Scans of Android and iOS applications seem stuck at S-1 for an extended period of time
While most scans pass the S-1 stage in less than a minute, Android, and iOS applications seem to stuck at S-1 for an extended period of time. In the meantime, CLEAR Engine log files show that stage S-1 is already completed. This is due to a bug in the CLI and web UI, causing the incorrect scan progress to be retrieved. The impact of this issue is strictly cosmetic.
This issue has been resolved in Lucent Sky AVM 4.3.
Scan created using the CLI does not inherit project file from its application
When creating a scan using the CLI, the scan does not inherit project file set in its application. This is due to a bug in the CLI, and affects versions between 4.0 and 4.2.
This issue is expected to be resolved in Lucent Sky AVM 4.5.
Scan performance is worse than previous versions on systems with certain Intel processors
The scan performance is worse than previous versions on systems with certain Intel processors. The average scan time is about 30% longer compared to Lucent Sky AVM 4.1.1. This is due to a bug in the optimization process for Intel processors based on the Haswell and later microarchitectures.
This issue has been resolved in Lucent Sky AVM 4.3.