Hello Avast fans!
It is my pleasure to officially announce the new Avast bug bounty program. As a security company, we very much realize that security bugs in software are reality. But we also realize that companies that are able to use their user communities to find and fix bugs are generally more successful that those that don’t. Therefore, we have decided to reward individuals who help us find and fix security-related bugs in our own software. This makes us probably the first security vendor with a reward program like this: I think it’s mainly because the other companies generally take the position that ‘Hey, we’re a security company. So we know security and it can’t happen to us.’ But in reality, that’s not what’s happening. Just look at bugtraq or the CVE databases and you will find that security software is no more immune to these issues than any other programs. A bit of irony, given that people generally install security software to fight security issues in the first place, isn’t it?
We at Avast take this very seriously. We know that being a market leader (Avast has more users than any other AV company in the world), we’re a very attractive target for the attackers. So, here’s our call to action: let’s unite and find and fix those bugs before the bad guys do!
Here’s how it works:
- The bounty program is designed for security-related bugs only. Sorry, we’re not paying for other types of issues like bugs in the UI, localization etc. (nevertheless, if you find such a bug, we will of course very much appreciate if you report it).
- This program is currently intended only for our product, i.e. not the website etc.
- We’re generally only interested in these types of bugs (in the order of importance):
- Remote code execution. These are the most critical bugs.
- Local privilege escalation. That is, using Avast to e.g. gain admin rights from a non-admin account.
- Denial-of-service (DoS). In case of Avast, that would typically be BSODs or crashes of the AvastSvc.exe process.
- Escapes from the avast! Sandbox (via bugs in our code)
- Certain scanner bypasses. These include include straightforward, clear bypasses (i.e. scenarios that lead to direct infection, with no additional user input), as opposed to things like deficiencies in the unpacking engine etc. In other words, we’re interested only in cases that cannot be mitigated by adding a new virus definition (please don’t report undetected malware)
- Other bugs with serious security implications (will be considered on a case by case basis).
- The base payment is $200 per bug. Depending on the criticality of the bug (as well as its neatness) the bounty will go much higher (each bug will be judged independently by a panel of experts). Remote code execution bugs will pay at least $3,000 – $5,000 or more.
- We might change these ranges based on the number and quality of incoming reports. Generally, the less reports we will get, the higher the bounty will go.
- We will only pay for bugs in Avast itself. For example, if you find a bug in a Microsoft library (even if it’s used by Avast), please report it to Microsoft instead (it would be great if you could also notify us, but unfortunately, we cannot offer any reward in such cases).
- The program is currently limited to consumer Windows versions of Avast (i.e.: Avast Free Antivirus, Avast Pro Antivirus, and Avast Internet Security). Only bugs in the latest shipping versions of these products will be considered.
- Payment will be done preferably by PayPal. If you can’t accept PayPal (e.g. because it doesn’t work in your country), please get in touch with us and we will try to figure out something else.
- Because of certain legal restrictions, we cannot accept submissions from the following countries: Iran, Syria, Cuba, North Korea and Sudan.
- It is the researcher’s own responsibility to pay any taxes and other applicable fees in their country of residence.
- In order to be eligible for the bounty, the bug must be original and previously unreported.
- If two or more researchers happen to find the same bug, the bounty will be paid only to the one whose submission came in first.
- You must not publicly disclose the bug until after an updated version of Avast that fixes the bug is released. Otherwise, the bounty will not be paid.
- The bounty will be paid only after we fix the issue (or, in specific cases, decide to not fix it).
- Some bugs may take longer to correct. We will do our best to fix any critical bugs in a timely fashion. We appreciate your patience.
- Employees of AVAST and their close relatives (parents, siblings, children, or spouse) and AVAST business partners, agencies, distributors, and their employees are excluded from this program.
- We reserve the right to change the rules of the program or to cancel it at any time.
How to report a bug and qualify for the bounty:
- Please submit the bug to a special email address email@example.com
- If you’d like to encrypt your email (recommended), please use this PGP key.
- A good bug report needs to contain sufficient information to reliably reproduce the bug on our side. Please include all information that may be relevant – your exact environment, detailed bug description, sample code (if applicable) etc. It also needs to contain a decent analysis – this is a program designed for security researchers and software developers and we expect certain quality level.
- You will receive a response from an Avast team member acknowledging receipt of your email, typically within 24 hrs. If you do not receive a response, please do not assume we’re ignoring you – we will do our best to follow up with you asap. Also, in such a case it is possible your email didn’t make it through a spam filter.
Finally, I’d like to say thanks to everyone who helps to find and fix bugs in our products. Hopefully, this new reward program will take this initiative to a whole new level.
P.S. The bug bounty rules are also available on our main website here.
The Avast Research Lab is where some of the Avast’s brightest brains essentially create new ways of detecting malware. These are either features inside the product (such as FileRep and autosandboxing, including all of its recent development) as well as components that run on our backend – i.e. things that users don’t necessarily see but that are equally important for the overall quality of the product.
In fact, working on the backend stuff takes up more of their time these days, as more and more intelligence in Avast is moving to the cloud and/or is being delivered in almost real time via the avast! streaming update technology. Read more…
Today, we have released a brand new avast! program update, version number 7.0.1473. It’s the last program update we plan to do before version 8 (slated for Q1 2013). I’d like to take this opportunity and explain some of its new features.
First and foremost, the new version is fully compatible with Windows 8 – scheduled to finally hit the stores this Friday. The changes we have made went well beyond just making sure everything works. For example, we had to replace the internals of the Network and Web Shields to accommodate the new networking APIs in Windows 8. Also, we had to make sure avast! plays nicely with the new Windows Security Center and that it correctly handles certain scenarios that are new to Windows 8.
This version of avast! will shortly be officially certified with the Windows 8 Compatible logo, and will be included in the new Windows Store.
With the introduction of our new mobile product, avast! Free Mobile Security, we officially entered the mobile security business. While most of the feedback we have seen to date has been very positive, some of the reviews and comments on the Android market indicate that some people are a bit confused about the product and its features. This blog post was meant to explain some of the concepts and hopefully help resolve some of the confusion. It is structured as questions and answers. If you have additional questions, please feel free to post a comment below or head to our forum.
1. Why should I install a security product on my phone? There’s no viruses anyway, right?
First, it’s important to realize that the product goes well beyond malware protection. Components like Anti-theft, Firewall, SMS and call filtering and Application management are very useful irrespective of the malware situation and are all a good reason to install the product.
However, even the malware situation is not that great. To date, we have registered about 4,000 unique apps that exhibit malicious behavior. Most of them were pulled from the market relatively soon (some didn’t even make it to the market), but we dare to say that we can detect them faster.
Also, some of the threats are completely platform independent. A great example is phishing. Here’s how it works: you are sent a link to a website that looks and feels exactly like your online banking site, but in fact it’s a fake site whose purpose is to capture your credentials and steal your money. This has been a long-time classic on the desktop, but as people start browsing the web using their mobile devices it’s also becoming a problem here. Therefore, it does make sense to have an app that will alert you whenever you do something stupid like this (in case of avast! Mobile Security, the Web Shield component takes care phishing URL filtering). Especially given it’s free.
For those interested in all things Android, I have some exciting news. AVAST Software has acquired ITAgents, the Austrian developer of the Theft Aware mobile phone theft protection and recovery system.
The acquisition strengthens AVAST’s technology base and gives us a hands-on security app designed for today’s Android-powered smartphones. Read more…
Virus definition update 110411-1 contained an error that resulted in a good number of innocent sites being flagged as infected. Generally, all sites with a script in a specific format were affected.
Our virus lab staff discovered the problem quickly after releasing the bad update and immediately started working on a fix. The fix was released about 45 minutes after the problematic update and has version number 110411-2. Anyone who still has this problem is kindly asked to manually update the definitions to the latest version, e.g. by right-clicking the avast taskbar icon (the orange (a) ball), and selecting Update -> Engine and Virus Definitions.
We sincerely apologize for the inconvenience. As this typically only affected remote sites (and not local files), simply updating to the latest definitions should completely solve the issue (no local files have been quarantined).
Softpedia recently asked me a few questions about avast and its future, which resulted in this article: http://news.softpedia.com/news/Softpedia-Exclusive-Interview-avast-5-140693.shtml
In case you have some additional questions about our technologies, or our strategy moving forward, I’ll try to answer these in the Comments section below.
During the last few weeks, we have been tweaking the avast! 5 engine; and while doing this, we found out that there were some hidden reserves with respect to its performance (namely, the duration of the on-demand scans).
One of the great new features of avast 5 is the persistent cache, a mechanism which allows us to skip rescanning of certain files. In particular, this applies to files which are on our internal whitelists, as well as files which are digitally signed by trusted publishers (we maintain a relatively short list of software publishers that we trust, and we consider any files produced and digitally signed by these publishers as safe).
This Wednesday, we released a new program update for avast!, version number 5.0.507. It brings a fair amount of fixes and new features (details here) and also 7 new language packs. Namely, the following languages were added:
- Portuguese (Portugal)
I usually don’t bother writing about individual AV tests and how great we did here and there, but this time I’ll make an exception. Malekal Morte, a very well-known (and influential) security person (tester/blogger/expert) from France recently performed a test of all leading free antivirus software products, and I’m very delighted to say that avast 5 was selected as a winner of the test. Read more…