grails-databinding detection scan (Linux)
| 0 Votes |
Description
This is Community Content. When you use these solutions, it is incumbent on your organization to test any solutions provided across the broadest available system base including various OS, storage solutions, and application inventory.
Please see the Community Solution Testing Statement
This Task performs a filesystem scan on Windows systems to attempt detecting Spring Framework versions that may be vulnerable to the following vulnerabilties reported in July 2022:
https://nvd.nist.gov/vuln/detail/CVE-2022-35912
https://github.com/grails/grails-core/security/advisories/GHSA-6rh6-x8ww-9h97
This Task performs a filesystem search across all fixed disks on Windows platforms, to locate Grails databinding JAR files, either directly on the filesystem or embedded in a .WAR or .EAR archive file. In the case any .WAR / .EAR file is found on the system, the 'unzip.exe' utility is used to perform a listing of files inside the archive to locate Spring-related .JAR files. Specifically, this Task searches for any versions of grails-databinding-*.jar. Information on the Grails vulnerability is still evolving and the list of vulnerable versions is still subject to change.
Scan results are stored in a "Scans" subdirectory beneath the "BES Client" folder. 'grails-databinding-scan-output.txt' contains the full script output for potential debugging or diagnosis, and "grails-databinding-scan.txt' contains a listing of detected files in one of the forms
/opt/grails/libs/grails-databinding-5.1.9.jar/opt/grails/grails-dist.war::grails.RELEASE/libs/grails-databinding-5.1.9.RELEASE.jar
The first sample entry indicates a detected grails-databinding.jar file directly in the filesystem, while the second entry indicates a Grails .jar file embedded within a .WAR archive.
This Task has several known limitations:
- Archives are not extracted recursively - only .JAR files contained directly within a .WAR archive are found; archives embedded within multiple layers of .WAR archives are not detected.
- There is no option to throttle the scan in terms of processor or disk i/o usage. Scans should be executed during non-critical hours, and staggered over time especially where multiple systems share a storage resource, such as a SAN or virtual machine storage pool.
This detection method uses Linux Bash script with external dependencies on 'df', 'find', 'sed', and 'unzip'. Results of the scan may be retrieved using the related Analysis.
Property Details
| 26942 | |
| Alpha - Code that was just developed | |
| grails-databinding detection scan (Linux) | |
| BESC | |
| Vulnerability Scan | |
| HCL BigFix Services | |
| 7/18/2022 12:00:00 AM | |
| grails, grails-databinding, jar, scan, file search, CVE-2022-35912 | |
| True | |
| JasonWalker on 7/20/2022 9:12:54 AM | |
| JasonWalker on 7/20/2022 9:12:54 AM | |
| 160 Views / 1 Download | |
* Average over 0 ratings.
** Log In or Register to add your rating.
|
Relevance
Actions
Action 1 (default)
parameter "ScansFolder" = "{(if (version of client >= "9" as version) then (pathname of parent folder of data folder of client) else (pathname of parent folder of parent folder of client folder of site "actionsite"))}/Scans"
folder create "{parameter "ScansFolder"}"
parameter "output"="{pathname of folder (parameter "ScansFolder")}/grails-databinding-scan.txt"
parameter "exec_output"="{pathname of folder (parameter "ScansFolder")}/grails-databinding-scan-output.txt"
delete "{parameter "output"}"
delete "{parameter "exec_output"}"
delete __createfile
createfile until EOF_EOF_EOF_EOF
#!/bin/sh
OUTPUT_FILE={parameter "output"}
function handle_file() {{
echo Handling $1
if [[ $1 == *\.war || $1 == *\.WAR || $1 == *\.zip || $1 == *\.ZIP || $1 == *\.ear || $1 == *\.EAR ]]
then
echo "${{1} is an archive, searing content via unzip";
for embeddedfile in `unzip -Z -1 "$1" *grails-databinding-*.jar -x *-sources.jar *-javadoc.jar`
do
echo ${{1}::${{embeddedfile}>>${{OUTPUT_FILE}
done
else
echo ${{1}>>${{OUTPUT_FILE}
fi
}
for j in `df -l --output=target -x tmpfs -x devtmpfs | sed 1d`
do echo "searching $j"
for targetfile in `find $j -xdev \( -name "*grails-databinding*.jar" -o -name "*.war" -o -name "*.ear" \) -a ! \( -name "*-sources.jar" -o -name "*-javadoc.jar" \)`
do handle_file "$targetfile"
done
done
EOF_EOF_EOF_EOF
delete run_scan.sh
copy __createfile run_scan.sh
wait chmod +x run_scan.sh
wait /bin/sh -c "./run_scan.sh > '{parameter "exec_output"}' 2>&1"
This action will be considered successful when the applicability relevance evaluates to false.
Sharing
| Social Media: |
