Benoitc hackney
Custom cacerts or cacertfile do not restrict trust to the pinned CA in hackney
Improper Certificate Validation vulnerability in hackney_ssl in benoitc hackney allows an on-path attacker to impersonate a server pinned to a private certificate authority via a certificate chain that ends in a publicly trusted root. hackney adds {partial_chain, fun hackney_ssl:partial_chain/1} to every verify_peer configuration. The callback returns any certificate in the peer chain whose public key matches a root in the bundled certifi store as the trust anchor, and OTP honours that callback over the configured cacerts. hackney_ssl:merge_ssl_opts/3 kept the callback when the caller replaced the trust store with cacerts or cacertfile in ssl_options, so a connection pinned to a private CA still accepted any chain that carried a publicly trusted root. The hostname check still applies, so the attacker needs a publicly trusted certificate for the pinned hostname. This issue affects hackney: from 1.24.0 before 4.9.0.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 1.24.0, < 4.9.0
Fixed in 4.9.0
- >= d8a9afcf5c3849904274e2eba1df56c63d1a1a0c, < 915eb5737e9c489d8fc22eec8cdae30e9b027be4
Fixed in 915eb5737e9c489d8fc22eec8cdae30e9b027be4
Mitigation
Upgrade hackney to 4.9.0 or later.
Upgrade hackney to 915eb5737e9c489d8fc22eec8cdae30e9b027be4 or later.
Workaround
Pass your own {partial_chain, Fun} in ssl_options alongside cacerts or cacertfile. A caller-supplied partial_chain replaces hackney's in the merge, and a callback that returns unknown_ca makes OTP validate against the configured cacerts only.
References
- Vendor advisory github.com/benoitc/hackney/releases/tag/4.9.0
- Patch github.com/benoitc/hackney/pull/978
- Patch github.com/benoitc/hackney/commit/d8a9afcf5c38…
1 more
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.