SSLContext.wrap_bio() missing validation of server_hostname parameter
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 3.10.22, 3.11.17, 3.12.15, 3.13.16, 3.14.8, and 1 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
ssl.SSLContext.wrap_bio() didn't require the server_hostname argument to not be None if ssl.SSLContext.check_hostname was set. Due to a missing parameter check in SSLObject, if the server_hostname argument isn't supplied then hostname verification would be silently skipped. This defect could lead to programs where certificate hostname verification appeared to be succeeding with SSLContext.check_hostname = True and no ValueError being raised due to misconfiguration. If the program passes a server_hostname value that isn't an empty string or None to any of these APIs then certificate hostname verification proceeds as expected and the program is not affected by this vulnerability. Mitigating this vulnerability doesn't require updating Python or applying the patch. To mitigate, pass a valid non-None and non-empty server_hostname value to SSLContext.wrap_bio(), asyncio.create_connection(), or asyncio.loop.start_tls() and certificate hostname verification will proceed as expected. Upgrading to the latest version of Python or applying the patch only changes the behavior from silently skipping hostname verification to raising a ValueError, similar to SSLContext.wrap_socket(), when server_hostname isn't supplied.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Python Software Foundation CPython
fixed in 3.10.22; From 3.11.0 · fixed in 3.11.17; From 3.12.0 · fixed in 3.12.15; From 3.13.0 · fixed in 3.13.16; From 3.14.0 · fixed in 3.14.8; From 3.15.0a1 · fixed in 3.15.0rc3
- libpythonBitnami
fixed in 3.10.22; From 3.11.0 · fixed in 3.11.17; From 3.12.0 · fixed in 3.12.15; From 3.13.0 · fixed in 3.13.16; From 3.14.0 · fixed in 3.14.8
- pythonBitnami
fixed in 3.10.22; From 3.11.0 · fixed in 3.11.17; From 3.12.0 · fixed in 3.12.15; From 3.13.0 · fixed in 3.13.16; From 3.14.0 · fixed in 3.14.8
- python-minBitnami
fixed in 3.10.22; From 3.11.0 · fixed in 3.11.17; From 3.12.0 · fixed in 3.12.15; From 3.13.0 · fixed in 3.13.16; From 3.14.0 · fixed in 3.14.8