dhcp: fix CVE-2022-38177, CVE-2022-38178, CVE-2022-2795 for bind

[elainezhao1]

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 (./SPECS/LICENSES-AND-NOTICES/data/licenses.json, ./SPECS/LICENSES-AND-NOTICES/LICENSES-MAP.md, ./SPECS/LICENSES-AND-NOTICES/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
• If you are adding/removing a .spec file that has multiple-versions supported, please add @microsoft/cbl-mariner-multi-package-reviewers team as reviewer (Eg. golang has 2 versions 1.18, 1.21+)
• [] Ready to merge

---

Summary

fix CVE-2023-50387, CVE-2022-38178, CVE-2022-2795 for bind in dhcp

Change Log

• add patches

Does this affect the toolchain?

NO

Associated issues

Links to CVEs

https://nvd.nist.gov/vuln/detail/CVE-2022-38177
https://nvd.nist.gov/vuln/detail/CVE-2022-38178
https://nvd.nist.gov/vuln/detail/CVE-2022-2795

Test Methodology

• Pipeline build id: https://dev.azure.com/mariner-org/mariner/_build/results?buildId=564241&view=results

[elainezhao1]

getting error in Verify all tests passed in pr check https://dev.azure.com/mariner-org/mariner/_build/results?buildId=564240&view=ms.vss-test-web.build-test-results-tab&runId=193405&resultId=100000&paneView=attachments , error: could not connect to libvirt (URI = qemu:///system): Failed to connect socket to '/var/run/libvirt/virtqemud-sock': No such file or directory [code=38 int1=2]"

[arc9693]

LGTM

[PawelWMS]

I was curious why you had to revert back to %setup and realized I've made a mistake in my initial suggestion by forgetting about the -N flag to disable auto patching. I've tested this to work locally:

Suggested change

	%setup -q -n dhcp-%{version}
	%autosetup -N

Sorry for the trouble.

[PawelWMS]

Documentation about %autosetup if you're curious: https://rpm-software-management.github.io/rpm/manual/autosetup.html.

[PawelWMS]

Looks good. One small request for %autosetup but not a blocker.

[CBL-Mariner-Bot]

Auto cherry-pick results:

• main ✅ -> [AUTO-CHERRYPICK] dhcp: fix CVE-2022-38177, CVE-2022-38178, CVE-2022-2795 for bind - branch main #9094

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