Unauthenticated encryption is vulnerable to chosen ciphertext attacks, bitflipping attacks about aescrypt HOT 6 OPEN

Is that something, that we can avoid using Random IV?

from aescrypt.

No, failure to use a random IV (#4) is a separate, unrelated, but still very bad problem.

from aescrypt.

@tarcieri Thanks for the info.

from aescrypt.

FYI, in case you're trying to follow the same path as me:

• Create a CVE request at http://cve.mitre.org/ - You'll get a CVE ID a day or so later.
• Create a report at https://rubysec.com/, quoting the CVE ID (they really need it even if it's not a required field)
• If people use https://github.com/rubysec/bundler-audit (they should), the reports will crop up.

from aescrypt.

I'm just sad it took me four years to figure out that this path works just fine... ugh. It should not have surprised me.

from aescrypt.

@jfinkhaeuser That web form is a new thing created this year, in response to MITRE failing to issue IDs in a timely fashion via e-mail.

from aescrypt.