security - refactor azure test code to not use insecure tempfile methods.

[kennethkaane]

SonarQube scan reports five vulnerabilities with critical severity in the Cloud Custodian code. They arise from the use of the insecure 'tempfile.mktemp' function. Creating temporary files using insecure methods exposes the application to race conditions on filenames: a malicious user can try to create a file with a predictable name before the application does. A successful attack can result in other files being accessed, modified, corrupted, or deleted. This risk is even higher if the application runs with elevated permissions.

In the past, it has led to the following vulnerabilities:

• CVE-2014-1858
• CVE-2014-1932

The resolution is to use 'tempfile.TemporaryFile' function instead.

[linux-foundation-easycla]

• ✅ Kenneth Kaane (6261c1d)

• ❌ - kennethkaane-hopin The commit (e12579d ,0aee48a9a54419364d0d26ebbaf0f4c962758c27 ,766aaaa70ece74b61fdb46edf77eefafb3fbacae) is not authorized under a signed CLA. Please click here to be authorized. For further assistance with EasyCLA, please submit a support request ticket.

[kapilt]

most of this appears related to the azure provider test code, aka not an issue in practice, but scanners gonna scan.

ie zero of this is runtime operational.

that said, i agree these are poor uses of tempfile in this provider, and should be replaced

[kapilt]

@kennethkaane can you please go through the cncf contributor agreement process.

[update] direct link https://api.easycla.lfx.linuxfoundation.org/v2/repository-provider/github/sign/14202841/52837350/6985/#/?version=2

[kennethkaane]

the cncf contributor agreement process.

Hi @kapilt, I have completed the CNCF contributor agreement process.

[kapilt]

it looks like some of the earlier commits were done with a github user which the cla bot doesn't recognize, can you rebase those or amend those commits?