Use of insecure crypto for storing passwords
Bug #1158373 reported by
Marc Deslauriers
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
remote-login-service (Ubuntu) |
Confirmed
|
Undecided
|
David Barth |
Bug Description
remote-
The crypto used for the file is totally wrong and insecure. It is trivial to perform an attack on this file and recover the contents and the user password.
In crypt.c:
- A password should not be used as an AES encryption key. The user password, along with a salt, should be put through a key-derivation function such as PBKDF2 before being used as the AES key.
- The key should not be used as the IV. The IV needs to be random.
- Cipher should at least be GCRY_CIPHER_AES256
CVE References
Changed in remote-login-service (Ubuntu): | |
assignee: | nobody → David Barth (dbarth) |
information type: | Private Security → Public Security |
Changed in remote-login-service (Ubuntu): | |
status: | New → Confirmed |
To post a comment you must log in.
David, could you take a look at this, and possibly find someone to fix it?
Thanks!