New issue
Advanced search Search tips
Starred by 12 users
Status: Fixed
Owner:
Closed: Oct 2015
Cc:

Restricted
  • Only users with Commit permission may comment.



Sign in to add a comment
Avast Antivirus: X.509 Error Rendering Command Execution
Project Member Reported by taviso@google.com, Sep 25 2015 Back to list
Avast will render the commonName of X.509 certificates into an HTMLLayout frame when your MITM proxy detects a bad signature. Unbelievably, this means CN="<h1>really?!?!?</h1>" actually works, and is pretty simple to convert into remote code execution.

To verify this bug, I've attached a demo certificate for you. Please find attached key.pem, cert.pem and cert.der. Run this command to serve it from a machine with openssl:

$ sudo openssl s_server -key key.pem -cert cert.pem -accept 443

Then visit that https server from a machine with Avast installed. Click the message that appears to demonstrate launching calc.exe.

Thanks, Tavis.

This bug is subject to a 90 day disclosure deadline. If 90 days elapse
without a broadly available patch, then the bug report will automatically
become visible to the public.


 
Project Member Comment 1 by taviso@google.com, Sep 25 2015
Attaching testcases.
cert.der
884 bytes Download
cert.pem
1.2 KB Download
key.pem
887 bytes Download
Project Member Comment 2 by taviso@google.com, Sep 25 2015
Screenshot for reference.
Avast-2015-09-25-11-02-34.png
629 KB View Download
Comment 3 Deleted
Project Member Comment 4 by taviso@google.com, Sep 30 2015
Avast are currently planning to push an update for this issue today.
Project Member Comment 5 by taviso@google.com, Oct 1 2015
Labels: -Restrict-View-Commit
The patch for this issue is live, removing view restrictions.
Comment 6 by athmi...@gmail.com, Oct 7 2015
Will there ever be a CVE for this issue?
Good Work, bug we are sad because there are so much people that thinks the antivirus is the best data shield. Greets
Comment 8 by rmkhur...@gmail.com, Oct 12 2015
Google! Please make Free and dependable antivirus for us.. 
Project Member Comment 9 by hawkes@google.com, Oct 12 2015
Status: Fixed
Comment 10 Deleted
Project Member Comment 11 by taviso@google.com, Nov 13 2015
Labels: Restrict-AddIssueComment-Commit
Sign in to add a comment