CVE-2022-42916: High severity Apple macOS Monterey vulnerability

Published Oct 17, 2022
·
Updated

A vulnerability was found in curl. The issue occurs because curl's HSTS check can be bypassed to trick it to keep using HTTP. Using its HSTS support, it can instruct curl to use HTTPS directly instead of using an insecure clear-text HTTP step even when HTTP is provided in the URL. This mechanism can be bypassed if the hostname in the given URL uses IDN characters that get replaced with 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) ..

Other sources

curl. Multiple issues were addressed by updating to curl version 7.86.0.

Apple

curl's HSTS check could be bypassed to trick it to keep using HTTP. Using its HSTS support, curl can be instructed to use HTTPS directly instead of using an insecure clear-text HTTP step even when HTTP is provided in the URL. This mechanism could be bypassed if the host name in the given URL 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) ..

Reference:

https://curl.se/docs/CVE-2022-42916.html

Red Hat

In curl before 7.86.0 the HSTS check could be bypassed to trick it into staying with HTTP. Using its HSTS support curl can be instructed to use HTTPS directly (instead of using an insecure cleartext HTTP step) even when HTTP is provided in the URL. This mechanism could be bypassed if the host name in the given URL uses IDN characters that get replaced with ASCII counterparts as part of the IDN conversion e.g. using the character UTF-8 U+3002 (IDEOGRAPHIC FULL STOP) instead of the common ASCII full stop of U+002E (.). The earliest affected version is 7.77.0 2021-05-26.

Microsoft

In curl before 7.86.0, the HSTS check could be bypassed to trick it into staying with HTTP. Using its HSTS support, curl can be instructed to use HTTPS directly (instead of using an insecure cleartext HTTP step) even when HTTP is provided in the URL. This mechanism could be bypassed if the host name in the given URL uses IDN characters that get replaced with ASCII counterparts as part of the IDN conversion, e.g., using the character UTF-8 U+3002 (IDEOGRAPHIC FULL STOP) instead of the common ASCII full stop of U+002E (.). The earliest affected version is 7.77.0 2021-05-26.

Credit

CVE-2022-42915, CVE-2022-42916, CVE-2022-32221, CVE-2022-35260

Affected Software

18 affected componentsFixes available
redhat/jbcs-httpd24-curl<0:7.86.0-2.el8
0:7.86.0-2.el8
redhat/jbcs-httpd24-curl<0:7.86.0-2.el7
0:7.86.0-2.el7
redhat/curl<7.86.0
7.86.0
Apple macOS Monterey<12.6.3
12.6.3
Apple macOS Ventura<13.2
13.2
haxx curl>=7.77.0<7.86.0
Fedoraproject Fedora=35
Fedoraproject Fedora=36
Fedoraproject Fedora=37
Apple macOS<12.6.3
Apple macOS>=13.0<13.2
Splunk Universal Forwarder>=8.2.0<8.2.12
Splunk Universal Forwarder>=9.0.0<9.0.6
Splunk Universal Forwarder=9.1.0
Microsoft azl3 tensorflow 2.16.1-1
Microsoft cbl2 curl 7.86.0-1
Microsoft azl3 tensorflow 2.11.1-1
Microsoft cm1 curl 7.86.0-1

Event History

Oct 26, 2022
CVE Published
12:00 AM
Oct 29, 2022
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
Description
Data Sourced
via NVD·02:15 AM
DescriptionSeverityWeaknessAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the vulnerability ID for this issue?

The vulnerability ID for this issue is CVE-2022-42916.

2

What is the severity of CVE-2022-42916?

The severity of CVE-2022-42916 is high.

3

How can this vulnerability be exploited?

This vulnerability can be exploited by bypassing the HSTS check in curl before version 7.86.0, allowing an attacker to trick it into staying with HTTP.

4

Which software versions are affected by CVE-2022-42916?

macOS Monterey version 12.6.3, curl version up to 7.86.0, jbcs-httpd24-curl version up to 0:7.86.0-2.el8, jbcs-httpd24-curl version up to 0:7.86.0-2.el7, and macOS Ventura version up to 13.2.

5

How do I fix CVE-2022-42916?

To fix CVE-2022-42916, update to curl version 7.86.0 or newer.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203