F-Secure Anti-Virus: Remote Code Execution via Solid RAR Unpacking
1–10 of 30 posts
Re: F-Secure Anti-Virus: Remote Code Execution via Solid RAR Unpacking
#2Re: F-Secure Anti-Virus: Remote Code Execution via Solid RAR Unpacking
#3Re: F-Secure Anti-Virus: Remote Code Execution via Solid RAR Unpacking
#4F-Secure
RAR
ASLR
massage the heap (what heap, where)
ROP chain
RarVM
etc.
Re: F-Secure Anti-Virus: Remote Code Execution via Solid RAR Unpacking
#5What are each of F-Secure RAR ASLR massage the heap (what heap, where) ROP chain RarVM etc.
F-Secure: an antivirus
RAR: an ancient archival format
ASLR: address space layout randomization, a system which loads code at unpredictable locations to make exploits harder to write (as you don't know where to jump)
ROP chain: Return Oriented Programming. A way to circumvent non-executable memory protection and ASLR by manipulating the call stack to jump into to existing executable code segments (called gadgets) and chain them together as each returns to the next.
RarVM: an ill concieved mechanism allowing code to be embedded in RAR archives.
Re: F-Secure Anti-Virus: Remote Code Execution via Solid RAR Unpacking
#6Re: F-Secure Anti-Virus: Remote Code Execution via Solid RAR Unpacking
#7And MalwareBytes is still using 7zip 18.01
Re: F-Secure Anti-Virus: Remote Code Execution via Solid RAR Unpacking
#8And MalwareBytes is still using 7zip 18.01
7-zip is licensed LGPL, so you should be able to replace the 7z support library with a newer version.
The LGPL makes it perfectly legal for the closed-source antivirus component to not load any 7zip .so binary that is not signed by the antivirus vendor, of a known hash, or so on... and the code loading said shared-object need not be available or modifiable, just the code for the vulnerable .so they do ship.
Re: F-Secure Anti-Virus: Remote Code Execution via Solid RAR Unpacking
#9Earlier quoted context omitted.
7-zip is licensed LGPL, so you should be able to replace the 7z support library with a newer version.
That is false. It's likely the end-user can update it, but the LGPL does not prevent it from being impossible. The LGPL makes it perfectly legal for the closed-source antivirus component to not load any 7zip .so binary that is not signed by the antivirus vendor, of a known hash, or so on... and the code loading said shared-object need not be available or modifiable, just the code for the vulnerable .so they do ship.