Added mao's scanning actions from FINOS security scanning

[linux-foundation-easycla[bot]]

The committers listed above are authorized under a signed CLA.

• :white_check_mark: login: robmoffat / name: Rob Moffat (4bb4bd85e3910c2f044e37ca9ad37f3dcd81b37a, 4339b8df6d80af9985eca783191e7105d30afb19, 5e894741f95bf504e4a65d3ed70bedd31c874aa7, 69f77169889fa8958768a6cba7b8d33ab34556dd, 5c12d5c829b8266f027d4214e9ee8512f27679c4, 695441c324af52b78400709d79725da9f290e4f2, 85d112dd65948902dbcb2c44910bcc25a8a9f9c2, 1da9430893393f4412140c80053792ffada6ab4e, 8c0b44fcd83145a5e2e70c644e31883446ebe281, ea4c06d0c8acad674319318f8e54873f7ac862e8, a25fe8196a7a906c6abbcff8a24e6e0be529cc92, cc1e01cf849cd25fcf9ac34ff5d262171954e60b, 3808ffe33dcd1edf67c5bf9ad1028e822cc604e4, a02555d3b5ff820169949a12307fe7ec1c9bad7f, be7da57efe48923238d12bd87bc8118535c00084, 75d3fce6d12a7d61f2357b7602bf9ec06cf35301, f0267375caf061f5a151cde99ec0cd65a2754ad2, d6de9c9645405417aa1b4e32c4705cfecf8f1093)
• :white_check_mark: login: web-flow / name: GitHub Web Flow (cc1e01cf849cd25fcf9ac34ff5d262171954e60b, f0267375caf061f5a151cde99ec0cd65a2754ad2, d6de9c9645405417aa1b4e32c4705cfecf8f1093)
• :white_check_mark: login: maoo / name: Maurizio Pillitu (d3a7ebbc1eead50e7d7cf77f63015c6c5ab185d2, a22c5173b67b959d471a9caaf00c19931f1b641a)

[TheJuanAndOnly99]

/easycla

[jarias-lfx]

/easycla

[robmoffat]

@maoo @vaibhav-db

this basically works now, except that there is a new critical CVE for Spring Boot and so our white source / Dependency Checks are failing.

Once a new version gets published we can release. Please review + approve.

[maoo]

@robmoffat - apparently spring-web-5.3.26.jar is affected by CVE-2016-1000027 , which states:

Pivotal Spring Framework through 5.3.16 suffers from a potential remote code execution (RCE) issue if used for Java deserialization of untrusted data. Depending on how the library is implemented within a product, this issue may or not occur, and authentication may be required. NOTE: the vendor's position is that untrusted data is not an intended use case. The product's behavior will not be changed because some users rely on deserialization of trusted data.

If you don't use spring-web for deserialization of untrusted data (that is, data that is manually entered), I'd suggest to add this to allow-list.xml with a note that explains why the CVE can be safely ignored; see https://nvd.nist.gov/vuln/detail/cve-2016-1000027

[robmoffat]

@vaibhav-db let's review. Also took out white source for future PRs