Samsung Patching Security Hole Found in Exynos SoCs

Latest Videos FromTom's Hardware
Kevin Parrish
Contributor

Kevin Parrish has over a decade of experience as a writer, editor, and product tester. His work focused on computer hardware, networking equipment, smartphones, tablets, gaming consoles, and other internet-connected devices. His work has appeared in Tom's Hardware, Tom's Guide, Maximum PC, Digital Trends, Android Authority, How-To Geek, Lifewire, and others.

  • house70
    CM team 1 - Samsung team 0
    CM team unpaid - Samsung team paid

    WTF?
    Reply
  • azraa
    So what?
    Its still better to have it open source, so people can read every last intruction. With other systems we never hear of bugs because probably those are all covered up.

    Good to hear they found that mistake, this kind of stuff keeps engineers up to date and more aware at their tasks.
    Reply
  • InvalidError
    Computer-illiterate technology journalists/sensationalists mis-attributing a software design flaw to hardware...

    I hate when journalists write about something they clearly have no clue about just for the headline.
    Reply
  • rantoc
    azraaSo what?Its still better to have it open source, so people can read every last intruction.
    Its both ways - A skilled hacker (not speaking script kiddies here) could with less effort find weaknesses in the open source's code than closed source that requires some additional steps to identify the weaknesses - The same goes the other way. If its open source there are more eyes on the code and thus also more likely to find the weak spots and plug them...

    So yeah its both ways when speaking about security!
    Reply
  • A Bad Day
    azraaSo what?Its still better to have it open source, so people can read every last intruction. With other systems we never hear of bugs because probably those are all covered up.Good to hear they found that mistake, this kind of stuff keeps engineers up to date and more aware at their tasks.
    For example, Citi Bank had a major URL flaw where hackers could simply replace some numbers in the URL and log into random accounts. Then then built an automated number generator/enterer to break into hundreds of thousands of accounts.

    The website designer stated that security and features are incompatible.

    But no one in the public knew about the flaw, because the bank never revealed it for obvious reasons.
    Reply
  • house70
    rantocIts both ways - A skilled hacker (not speaking script kiddies here) could with less effort find weaknesses in the open source's code than closed source that requires some additional steps to identify the weaknesses - The same goes the other way. If its open source there are more eyes on the code and thus also more likely to find the weak spots and plug them... So yeah its both ways when speaking about security!It is both ways, but not equally so - an open-source Linux distro is considered far more secure than other OSes. Even the fact that the CM devs were able to plug the hole faster than Samsung itself speaks for the advantage of open-source.
    My first comment was directed at Samsung - looks like they need new blood in their software division.
    Reply
  • dark_knight33
    A Bad DayFor example, Citi Bank had a major URL flaw where hackers could simply replace some numbers in the URL and log into random accounts. Then then built an automated number generator/enterer to break into hundreds of thousands of accounts.The website designer stated that security and features are incompatible.But no one in the public knew about the flaw, because the bank never revealed it for obvious reasons.
    That's still highly irresponsible. With all of the website hacking going on, a flaw like that could expose millions of people to theft and fraud. Something Citi would eventually be found negligent for. OTH, if Citi had used OSS, a hole of that magnitude would likely have been found and fixed before the code ever went live. OSS will always be more secure, and fixed faster than close source.
    Reply
  • mouse24
    A Bad DayFor example, Citi Bank had a major URL flaw where hackers could simply replace some numbers in the URL and log into random accounts. Then then built an automated number generator/enterer to break into hundreds of thousands of accounts.The website designer stated that security and features are incompatible.But no one in the public knew about the flaw, because the bank never revealed it for obvious reasons.
    If no one in the public knew about it than how do you know about it?
    Reply