I have released a new Captcha Intruder (CINtruder) code. It includes a
complete Web User Interface (GUI) and some advanced features for:
update, manage dictionaries, etc.
Desc:
An independent research uncovered a critical vulnerability in zend-mail, a
Zend Framework’s component that could potentially be used by (unauthenticated)
remote attackers to achieve remote arbitrary code execution in the context
of the web server user and remotely compromise…
Thanks for backing me up on a number of things. Only one response below.
The site you linked mentioned 64bit block ciphers are vulnerable, even
in CTR mode. Obviously the birthday “paradox” applies. Regardless of
how right or wrong you are about Sweet32, this far from the most
important thing *implementors* should be worried about. Obviously if
they start with AES, then the birthday paradox issues are vastly
reduced. Any…
An independent research uncovered a critical vulnerability in SwiftMailer that
could potentially be used by (unauthenticated) remote attackers to achieve
remote arbitrary code execution in the context of the web server user and
remotely compromise the target web…
That is wrong. CBC mode allows attacks such as “Sweet32”
(https://sweet32.info/), which is not possible with CTR mode.
Correct again, but too simple minded. Any encryption without integrity
protection does not provide confidentiality against an active attacker.
Using the wrong mode with a block cipher can render authentication
irrelevant in attacks on confidentiality.
All traditional modes that lack integrity protection are vulnerable to
chosen-ciphertext attacks in these kinds of scenarios. CFB isn’t
immune and CTR is catastrophically weak. All traditional modes need a
MAC or similar integrity protection. In light of that, there’s
nothing particularly wrong with using CBC, if it is implemented well.
At least, using it is not *more* wrong than using OFB, CFB, or CTR
without integrity protection….