6 ms·
Probably that is because these three cURL issues are quite convoluted for an attacker to exploit, and so the issue has seen less urgency at Microsoft: - https:
by mschuster91 3y ago
Probably that is because these three cURL issues are quite convoluted for an attacker to exploit, and so the issue has seen less urgency at Microsoft:
- https://curl.se/docs/CVE-2023-38039.html https://curl.se/docs/CVE-2023-38039.html => that one is a resource exhaustion that needs the victim to connect to a malicious server intentionally
- https://curl.se/docs/CVE-2023-38545.html https://curl.se/docs/CVE-2023-38545.html => that one needs a way for the attacker to control the target hostname and the victim needs to use SOCKS5, which in itself is incredibly rare. Never seen it either in BigCo or government environments, I only remember that from a decade ago when dabbling in warez.
- https://curl.se/docs/CVE-2023-38546.html https://curl.se/docs/CVE-2023-38546.html => that one only affects people using libcurl or its bindings directly, and use the `duphandle` function, which is why it's ranked "Low" in severity.
- dspillett 3y ago> needs to use SOCKS5, which in itself is incredibly rare. Never seen it either in BigCo Anecdata: We use a SOCKS5 proxy for some internal plumbing, though not in a context where curl/libcurl are at all relevant. I've seen reference to it elsewhere in recent times, so “incredibly rare” might be somewhat an overstatement. But I agree with your assessment that these issues do not seem to be high priority. Also two of them are down as affecting v8.3 so were only addressed in an upstream release one week ago.