Descriptioncurl before 7.53.0 has an incorrect TLS Certificate Status Request extension feature that asks for a fresh proof of the server's certificate's validity in the code that checks for a test success or failure. It ends up always thinking there's valid proof, even when there is none or if the server doesn't support the TLS extension in question. This could lead to users not detecting when a server's certificate goes invalid or otherwise be mislead that the server is in a better shape than it is in reality. This flaw also exists in the command line tool (--cert-status).
Overall state of this security issue: Does not affect SUSE products
This issue is currently rated as having moderate severity.
|National Vulnerability Database||SUSE|
|National Vulnerability Database|
List of released packages
|Product(s)||Fixed package version(s)||References|
|SUSE Linux Enterprise Module for Basesystem 15|| ||Patchnames:
SUSE Linux Enterprise Module for Basesystem 15 GA curl
|openSUSE Leap 15.0|| ||Patchnames:
openSUSE Leap 15.0 GA curl
Status of this issue by product and package
Please note that this evaluation state might be work in progress, incomplete or outdated. Also information for service packs in the LTSS phase is only included for issues meeting the LTSS criteria. If in doubt, feel free to contact us for clarification.
|SUSE Linux Enterprise Desktop 12 SP1||curl||Not affected|
|SUSE Linux Enterprise Desktop 12 SP2||curl||Not affected|
|SUSE Linux Enterprise SDK 11 SP4||curl||Not affected|
|SUSE Linux Enterprise SDK 12 SP1||curl||Not affected|
|SUSE Linux Enterprise SDK 12 SP2||curl||Not affected|
|SUSE Linux Enterprise Server 11 SP4||curl||Not affected|
|SUSE Linux Enterprise Server 12 SP1||curl||Not affected|
|SUSE Linux Enterprise Server 12 SP2||curl||Not affected|
|SUSE Studio Onsite 1.3||curl||Not affected|