Homepage

Cleartext Transmission of Sensitive Information The advisory has been revoked - it doesn't affect any version of package jbcs-http24-curl  (opens in a new tab)

Threat Intelligence

EPSS
16.6% (97th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-RHEL7-JBCSHTTP24CURL-3594386
  • published21 Dec 2022
  • disclosed21 Dec 2022
Report a new vulnerability Found a mistake?

Introduced: 21 Dec 2022

CVE-2022-43551  (opens in a new tab)
CWE-319  (opens in a new tab)

Amendment

The Red Hat security team deemed this advisory irrelevant for RHEL:7.

NVD Description

Note: Versions mentioned in the description apply only to the upstream jbcs-http24-curl package and not the jbcs-http24-curl package as distributed by RHEL.

A vulnerability exists in curl <7.87.0 HSTS check that could be bypassed to trick it to keep using HTTP. Using its HSTS support, curl can be instructed to use HTTPS instead of using an insecure clear-text HTTP step even when HTTP is provided in the URL. However, the HSTS mechanism could be bypassed if the host name in the given URL first uses IDN characters that get replaced to ASCII counterparts as part of the IDN conversion. Like using the character UTF-8 U+3002 (IDEOGRAPHIC FULL STOP) instead of the common ASCII full stop (U+002E) .. Then in a subsequent request, it does not detect the HSTS state and makes a clear text transfer. Because it would store the info IDN encoded but look for it IDN decoded.