libcurl-using applications can ask for a specific client certificate to be used in a transfer. This is done with the `CURLOPT_SSLCERT` option (`--cert` with the command line tool).When libcurl is built to use the macOS native TLS library Secure Transport, an application can ask for the client certificate by name or with a file name - using the same option. If the name exists as a file, it will be used instead of by name.If the appliction runs with a current working directory that is writable by other users (like `/tmp`), a malicious user can create a file name with the same name as the app wants to use by name, and thereby trick the application to use the file based cert instead of the one referred to by name making libcurl send the wrong client certificate in the TLS connection handshake.
| Vulnerable Product | Search on Vulmon | Subscribe to Product |
|---|---|---|
haxx curl |
||
netapp snapcenter - |
||
netapp oncommand workflow automation - |
||
netapp oncommand insight - |
||
netapp clustered data ontap - |
||
netapp solidfire - |
||
netapp hci management node - |
||
netapp active iq unified manager - |
||
oracle peoplesoft enterprise peopletools 8.57 |
||
oracle peoplesoft enterprise peopletools 8.58 |
||
oracle peoplesoft enterprise peopletools 8.59 |
||
oracle mysql server |
||
siemens sinec infrastructure network services |
||
netapp h300s_firmware - |
||
netapp h300e_firmware - |
||
netapp h500e_firmware - |
||
netapp h500s_firmware - |
||
netapp h700s_firmware - |
||
netapp h700e_firmware - |
||
netapp h410s_firmware - |
||
splunk universal forwarder 9.1.0 |
||
splunk universal forwarder |
Vulmon