There is an ASM signature for this - 200104796 - that signature is not specific to CVE-2022-35912 but rather is a generic mitigation for that class of attack, and existed prior to the disclosure of CVE-2022-35912.
As long as you have signatures newer than 2022/04/10 then you'll already have the latest version of that signature, and just need to ensure it is enabled in your policies.
