You won’t be able to inspect the file directly, unless you first extract it from the .jar archive. For that you’d need to run an Action.
This does seem similar to a use-case I’ve been refining in light of the Log4J, Spring Boot, and Grails vulnerabilities that have come up over the last few years.
I have a task at https://bigfix.me/fixlet/details/26943 that may be useful as an example of downloading the unzip exe utility and using it to extract files from a JAR archive. If your JAR is in a known path that’s a bit easier, this task was to scan all local drives to locate the jar archives.
Once you’ve extracted the properties file to a temp path, you could use a relevance substitution to read the version from the file, and apply it as a client setting, or have a separate analysis read the extracted properties file.
