Certain jar files are reported as Malformed Containers by Symantec Protection Engine for Cloud and NAS
Scan Engine log would contain events similar to the following:
A container violation has been found Event Severity Level : Warning File name : \\?\UNC\X.X.X.X\ONTAP_ADMIN$\vol\vol1\YYYYYYYYY-AAAAAA-BBB.jar File status : NOT REPAIRED
Component name : YYYYYYY~1.JAR Component disposition : NOT REPAIRED Container Violation : Malformed container (file not scanned)
This behaviour occurs when the jar file not entirely zip format compliant. When there is some deviation in the file from the standard the decomposer will return a malformed container verdict. Files may be checked by the provider against the relevant standard available:
Symantec are evaluating a means to relax the strict type checking the decomposer executes on thise files in order to reduce the frequency of these verdicts. This Technote will be updated when more information is available.
Subscribing will provide email updates when this Article is updated. Login is required.