Having recently ruffled Microsoft’s feathers by (responsibly) disclosing three unpatched vulnerabilities in Windows to the general public, Google’s Project Zero team has now turned its attention to the other side of the PC-Mac divide. The outfit recently spilled the beans on three zero-day vulnerabilities in Apple’s OS X operating system.
The concept of a bug bounty program is nothing new, and even Facebook will line your pockets with cash if you discover a qualifying security vulnerability in the social network or select acquisitions it's made. Until now, however Oculus Rift was exempt. Facebook has now extended its bug bounty program to Oculus Rift, which joins other Facebook acquisitions such as Instagram, Parse, Onavo, and Moves.
Nearly 900 million devices running Android 1.6 or later at risk
The Black Hat USA 2013 security conference does not get underway until July 27, 2013, but there is already plenty to look forward to, with the folks at Bluebox Security dropping a bombshell by claiming to have unearthed a yawning hole in Android’s security fabric and promising to shed some technical light on the vulnerability during the upcoming conference.
We can't stop playing Skyrim. Well, except for when it forces us to stop -- for instance, with a show-stopping crash or, er, a physics-defying dragon. Bethesda's already patched its massively single-player RPG opus once (to mixed results), but it's not sheathing its bug-smashing mallet any time soon. That said -- much as we appreciate patch notes like “Fixed occasional issue where a guest would arrive to the player’s wedding dead” -- small tweaks to Bethesda's enormous game are hardly the only things we have to look forward to.
It’s easy to forget sometimes that Google is not a giant monolithic entity that eats your search data, but is in fact, run by people. And people can make mistakes; like for instance releasing a much anticipated app with a crippling bug. That’s what’s going down today as Google has had to pull the just released Gmail iOS app after a bug was found that rendered notifications non-functional.
We have a feeling that someone sarcastically uttered the phrase “What could possibly go wrong?” before pressing Dead Island's big, red “launch on Steam” button, because how else could things have gone this wrong? Dead Island released in a fittingly festering state, ridden with wriggly, sometimes game-breaking bugs. After a bit of digging, intrepid Steam forum-goers discovered the culprit: a bit of game code that read “Xbox Live Submission Project Version.” Whoops.
Bug hunters never had it so good. As it stands, Google routinely pays sizable sums for bringing security flaws to its attention, and following suit is Facebook. The social networking site posted a "Security Bug Bounty" page in which it details rules and awards for tracking down "qualifying security bugs." A typical bounty is $500, though if you find a particularly juicy one, Facebook says it will consider increasing the payout. Ready to go bug hunting? Here's what you need to know.
Mozilla's Firefox started out as the little browser that could and has since grown into a full-fledged market force in its own right. But behind Mozilla's pretty little Persona-sporting smile lies a terrible secret – a secret that's been there almost from the beginning. A secret that can sometimes cripple the otherwise spunky browser. You see, just like poor old confused Aunt Dorothy, Firefox has a memory leak. That's not news. What is news is the fact that Mozilla might finally be stepping up to the plate to fix the problem.
Microsoft took great pains to talk up the ease of the Windows Phone update process when announcing the OS. It was their intention to draw a clear distinction between WP7, and the haphazard Android update process. Despite what we can only assume is their best effort, some serious issues are cropping up with this first small update.
According to ZD Net, some Android users are becoming frustrated with the lack of progress on a particularly annoying bug. Many users have reported that an SMS bug in the mobile OS can cause messages to be sent to the wrong number in some instances. A search of the Google Code site indicates this has been an issues ever since the first Froyo builds rolled out back in June. It is currently listed as 'Medium' priority.
The degree to which this bug crops up seems to vary wildly. Some users report being able to reproduce it upon request with a series of somewhat complicated steps. Another piece of the puzzle is more common, and involves simply being routed to the wrong place. Tapping on the Messaging icon, or a message notification can sometimes route the user to the wrong Messaging thread. It could be easy to fire off a text here without noticing.
We've never experienced the first bug on our Android phones. The second, and less severe SMS bug has come up occasionally, but not often. Have any of you Android users noticed any SMS being sent to the wrong person?