#Windows users running stupid scanners now contact us for support regarding CVE-2023-46218 which the scanners say affects #curl 8.4.0 shipped by Microsoft.

It would, if their version was built to use #iibpsl, a prereq for this CVE, which #Microsoft does not.

Security scanners. A snake oil business.

curl.se/docs/CVE-2023-46218.ht…

This entry was edited (10 months ago)
in reply to daniel:// stenberg://

if scanners were trained to identify pictures of venomous snakes:

Rattlesnake: scanner says venomous snake, cvss9.8
Coral snake: scanner says venomous snake, cvss10.0
Milk snake: scanner says venomous snake, cvss10.0
Slow worm: scanner says venomous snake, cvss8.5
A coil of rope: scanner says venomous snake, cvss 9.0
A baby's rattle: scanner says venomous snake, cvss 9.8

in reply to daniel:// stenberg://

The problem is not the tools themselves (not entirely at least because they have many shortcomings, like not accounting for Debian/Ubuntu fixes backports) but how people (don't) analyze the results.
We do use vulnerability scanners (sending SBOMs to Dependency-Track) but this clearly requires work to analyze the results and determine if you're actually vulnerable (false positive, non-exploitable vuln, only if configured in some specific way, etc.)
Contacting project maintainers for assistance without even some prior analysis is just plain wrong I 💯 agree!