New vulnerability CVE-2022-32210 found on v18.x

[github-actions]

Failed run: https://github.com/nodejs/nodejs-dependency-vuln-assessments/actions/runs/2790721148
Vulnerability ID: CVE-2022-32210

Full output:

WARNING: New vulnerabilities found
- undici (version 5.8.0) :
	- CVE-2022-31151: https://nvd.nist.gov/vuln/detail/CVE-2022-31151
	- CVE-2022-31150: https://nvd.nist.gov/vuln/detail/CVE-2022-31150
	- CVE-2022-32210: https://nvd.nist.gov/vuln/detail/CVE-2022-32210

For each dependency and vulnerability, check the following:
- Check that the dependency's version printed by the script corresponds to the version present in the Node repo.
If not, update dependencies.py with the actual version number and run the script again.
- If the version is correct, check the vulnerability's description to see if it applies to the dependency as
used by Node. If not, the vulnerability ID (either a CVE or a GHSA) can be added to the ignore list in
dependencies.py. IMPORTANT: Only do this if certain that the vulnerability found is a false positive.
- Otherwise, the vulnerability found must be remediated by updating the dependency in the Node repo to a
non-affected version, followed by updating dependencies.py with the new version.

[mhdawson]

Check - #10 for confirmation that this does not affect Node.js

[mhdawson]

@facutuesca in respect to -#10 (comment) could you take another look to see if it still makes sense that its beeing reported as a vulnerability.

[facutuesca]

@mhdawson I found the issue: It is still being reported as a vulnerability even after the NVD updated the affected versions, due to the kind of query the script does to search for undici in the database.

I opened a small PR with the fix here: nodejs/node#44128

[mhdawson]

@facutuesca thanks, approved and requested fast track to see if we can get it landed soon.