| Name | Modified | Size | Downloads / Week |
|---|---|---|---|
| Parent folder | |||
| libupnp-22.2.0.tar.bz2 | 2026-11-04 | 840.6 kB | |
| libupnp-22.2.0.tar.bz2.sha256 | 2026-11-04 | 89 Bytes | |
| README.md | 2026-11-04 | 1.1 kB | |
| release-22.2.0 source code.tar.gz | 2026-11-04 | 965.8 kB | |
| release-22.2.0 source code.zip | 2026-11-04 | 1.3 MB | |
| Totals: 5 Items | 3.1 MB | 1 | |
Security fixes
- GHSA-8rmx-x2cq-xh33: Authenticate the server of HTTPS connections. With
UPNP_ENABLE_OPEN_SSL, the client accepted any certificate and never checked the host name, so an on-path attacker or a malicious device could intercept an https:// connection (CWE-295, CWE-297). The client now usesSSL_VERIFY_PEERwith the system's default trust store and checks that the certificate matches the host of the URL. SOAP actions, GENA, NOTIFY,UpnpDownloadUrlItem()andUpnpDownloadXmlDoc()have no TLS and sent https:// requests in clear (CWE-319); they now returnUPNP_E_INVALID_URL. This changes the default behaviour: a server with an untrusted certificate is now rejected unless its certificate or CA is added to the context returned byUpnpGetSslCtx(). Only builds withUPNP_ENABLE_OPEN_SSLare affected.
What's Changed
- cast to unsigned char for ctype calls in the uri and http parsers by @Candybar99 in https://github.com/pupnp/pupnp/pull/666
Full Changelog: https://github.com/pupnp/pupnp/compare/release-22.1.10...release-22.2.0