Lucene search
K

libcurl keeps previously used connections in a connection pool for subsequenttransfers to reuse if one of them matches the setup.Due to errors in the logic the config matching function did not take 'issuercert' into account and it compared the involved paths *case insensitively*which could lead to libcurl reusing wrong connections.File paths are or can be case sensitive on many systems but not all and caneven vary depending on used file systems.The comparison also didn't include the 'issuer cert' which a transfer can setto qualify how to verify the server certificate.

🗓️ 17 Aug 2021 07:00:00Reported by MicrosoftType 
mscve
 mscve
🔗 msrc.microsoft.com👁 1 Views

Libcurl may reuse wrong connections from case-insensitive path checks and issuer omission.

Related
Detection

Data

Build on a solid foundation with Vulners data

We provide the essential building blocks for cybersecurity solutions with comprehensive, structured, and constantly updated vulnerability and exploits data

Api

Power your application with Vulners API

The Vulners REST API offers reliable, high-performance access to vulnerability intelligence, with 99.9% SLA uptime and CDN-backed data delivery for seamless global access

App

Assess and manage vulnerabilities with Vulners tools

Built on top of Vulners' database and SDK, end-user solutions give security professionals and developers lightweight and powerful tools for vulnerability remediation

16 Dec 2021 08:00Current
6.2Medium risk
Vulners AI Score6.2
CVSS 3.13.7
CVSS 24.3
EPSS0.0056
SSVC
1