Patch luajit for CVE-2024-25177[HIGH]

[kgodara912]

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

Added patch for CVE-2024-25177

Change Log

• Added patch for CVE-2024-25177
• Modified luajit.spec

Does this affect the toolchain?

NO

Associated issues

• #xxxx

Links to CVEs

• https://nvd.nist.gov/vuln/detail/CVE-2024-25177

Test Methodology

• Pipeline build id: Buddy Build

[realsdx]

this link https://luajit.org/download/LuaJIT-2.1.0-beta3.tar.gz is dead, maybe we can use the github one?

[Sumynwa]

this link https://luajit.org/download/LuaJIT-2.1.0-beta3.tar.gz is dead, maybe we can use the github one?

Yes, please use the github link.

[Kanishk-Bansal]

We can use https://github.com/LuaJIT/LuaJIT/archive/refs/tags/v2.1.0-beta3.tar.gz

[kgodara912]

The above has different signature compared to what we have already due to .gitignore in source tree, except that everything else is same. I will rename existing source tree and will update signature for the file.

[kgodara912]

Updated buddy build

[Kanishk-Bansal]

Patch Analysis (the patch applies cleanly wrt t upstream)

there was a check failing due to which we updated the signature and cgmanifest as the older link was giving a 404 error

• Buddy Build 
• patch applied during the build (check rpm.log)
• patch include an upstream reference
• PR has security tag

[CBL-Mariner-Bot]

Auto cherry-pick results:

• main ✅ -> [AUTO-CHERRYPICK] Patch luajit for CVE-2024-25177[HIGH] - branch main #14524

Auto cherry-pick pipeline run -> https://dev.azure.com/mariner-org/mariner/_build/results?buildId=900928&view=results