Bug 1900705 (CVE-2020-28924) - CVE-2020-28924 rclone: Insecure passwords generated by rclone config (security hardening)
Summary: CVE-2020-28924 rclone: Insecure passwords generated by rclone config (securit...
Keywords:
Status: CLOSED UPSTREAM
Alias: CVE-2020-28924
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1900718 1900719
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-11-23 15:02 UTC by Marian Rehak
Modified: 2020-11-23 17:34 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-11-23 17:34:14 UTC


Attachments (Terms of Use)

Description Marian Rehak 2020-11-23 15:02:45 UTC
An issue was discovered in Rclone before 1.53.3. Due to the use of a weak random number generator, the password generator has been producing weak passwords with much less entropy than advertised. The suggested passwords depend deterministically on the time the second rclone was started. This limits the entropy of the passwords enormously. These passwords are often used in the crypt backend for encryption of data. It would be possible to make a dictionary of all possible passwords with about 38 million entries per password length. This would make decryption of secret material possible with a plausible amount of effort. NOTE: all passwords generated by affected versions should be changed.

https://github.com/rclone/rclone/issues/4783
https://rclone.org/downloads/

Comment 1 Marian Rehak 2020-11-23 15:19:58 UTC
Created rclone tracking bugs for this issue:

Affects: epel-all [bug 1900719]
Affects: fedora-all [bug 1900718]

Comment 2 Product Security DevOps Team 2020-11-23 17:34:14 UTC
This CVE Bugzilla entry is for community support informational purposes only as it does not affect a package in a commercially supported Red Hat product. Refer to the dependent bugs for status of those individual community products.


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