Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1393431 - (CVE-2016-9243) CVE-2016-9243 python-cryptography: HKDF might return an empty byte-string
CVE-2016-9243 python-cryptography: HKDF might return an empty byte-string
Status: NEW
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
low Severity low
: ---
: ---
Assigned To: Red Hat Product Security
impact=low,public=20161105,reported=2...
: Security
Depends On: 1393432
Blocks: 1393433
  Show dependency treegraph
 
Reported: 2016-11-09 09:36 EST by Andrej Nemec
Modified: 2018-04-30 18:15 EDT (History)
18 users (show)

See Also:
Fixed In Version: python-cryptography 1.5.3
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Andrej Nemec 2016-11-09 09:36:53 EST
Cryptography 1.5.3 release fixed one security issue.

HKDF would return an empty byte-string if used with a length less than algorithm.digest_size.

References:

https://cryptography.io/en/latest/changelog/#id1

Upstream bug:

https://github.com/pyca/cryptography/issues/3211

Upstream patch:

https://github.com/pyca/cryptography/commit/b924696b2e8731f39696584d12cceeb3aeb2d874
Comment 1 Andrej Nemec 2016-11-09 09:37:29 EST
Created python-cryptography tracking bugs for this issue:

Affects: fedora-all [bug 1393432]
Comment 2 Huzaifa S. Sidhpurwala 2016-11-10 02:57:20 EST
Data returned by the HKDF() are deemed to be cryptographically strong keys, which can be used by other cryptrographical primitives like ciphers to encrypt secret data. When HKDF() returns empty strings, then depending on the primitive used, it could mean weak encryption or perhaps no encryption at all.

Note You need to log in before you can comment on or make changes to this bug.