Upgrade openssl to 3.3.7

[jykanase]

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

• The toolchain has been rebuilt successfully (or no changes were made to it)
• The toolchain/worker package manifests are up-to-date
• Any updated packages successfully build (or no packages were changed)
• Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
• Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
• All package sources are available
• cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
• LICENSE-MAP files are up-to-date (./LICENSES-AND-NOTICES/SPECS/data/licenses.json, ./LICENSES-AND-NOTICES/SPECS/LICENSES-MAP.md, ./LICENSES-AND-NOTICES/SPECS/LICENSE-EXCEPTIONS.PHOTON)
• All source files have up-to-date hashes in the *.signatures.json files
• sudo make go-tidy-all and sudo make go-test-coverage pass
• Documentation has been updated to match any changes to the build system
• Ready to merge

---

Summary

Upgrade openssl to 3.3.7

Change Log

Does this affect the toolchain?

YES/NO

Associated issues

• #xxxx

Links to CVEs

• https://nvd.nist.gov/vuln/detail/CVE-YYYY-XXXX

Test Methodology

• Pipeline build id: xxxx

[Kanishk-Bansal]

Buddy Build

[jykanase]

1. Installed openssl-3.3.7 when SymCrypt-OpenSSL is installed by default. Tried the following command, it loaded SymCrypt providers: openssl list -digest-algorithms

2. Removed SymCrypt-OpenSSL package and tried if openssl works:

3. When SymCrypt-OpenSSL is not installed, it did not load the providers:

[jykanase]

Buddy Build has passed.
Full Build has passed.

[kgodara912]

Minor version bump to openssl. They both are from the same stable release chain and will be used as drop-in replacement. There was previously an upgrade attempted as PR-16518 but some tests were failed by that upgrade. Though we don't have that list of test cases, but author says that they are fixed. As both full build and buddy build are successful, hence re-attempting the merge. If tests fail for other packages, we will properly debug and fix. LGTM.