STE WILLIAMS

Barclays bank bod in the cooler for aiding Dridex money launderers

An employee of Barclays Bank who laundered thousands of pounds on behalf of Moldovan cybercriminals was yesterday sentenced to six years and four months behind bars in Blighty.

According to the Crown Prosecution Service, Jinal Pethad, 29, from Edgware, London, UK, set up more than a hundred false accounts to launder money and maintained almost 200 on behalf of Pavel Gincota and Ion Turcan for two years.

Pethad’s access allowed Gincota and Turcan to withdraw money from these accounts, and to move funds between them in order to launder it.

Pethad pleaded guilty at the opening of his case at the Old Bailey on Monday to conspiracy to conceal, disguise, convert, transfer or remove criminal property, contrary to section 1(1) of the Criminal Law Act 1977.

A UK National Crime Agency statement said that Gincota and Turcan had stolen the cash by using the Dridex malware to record the bank details of people who opened their spam email attachment. Both pleaded guilty to conspiracy to possess false identification and conspiracy to launder money in October 2016. Gincota was jailed for five years and eight months, and Turcan received a seven-year sentence.

Tom Guest, specialist prosecutor, said the CPS had presented evidence that Pethad had facilitated and benefitted from his crimes, and that he had had “abused his position of trust in his job”. ®

Article source: http://go.theregister.com/feed/www.theregister.co.uk/2017/12/13/barclays_employee_sentenced_for_aiding_money_launderers/

OK, OK, MIRA-I DID IT: Botnet-building compsci kid comes clean

A former New Jersey college student has copped to helping create and run the massive Mirai DDoS botnet.

Paras Jha, 21, pleaded guilty this month in an Alaska district court to two counts [PDF, PDF] of conspiracy to commit “fraud and related activity in connection with computers.”

In plea deals with US prosecutors, unsealed today, Jha admitted to being one of three people who created and ran the massive Mirai army of hacked gadgets as a DDoS-for-hire operation and as a click-fraud racket. Each of the charges carries up to five years behind bars, and Jha will also surrender the 13 Bitcoin (currently worth around $214,000) that he made from running the botnet and renting out its services.

The two other men are: Josiah White, 20, of Washington, Pennsylvania, and Dalton Norman, 21, of Metairie, Louisiana. These two also pleaded guilty to playing a role in masterminding Mirai; Dalton additionally admitted helping Jha commit ad-click fraud.

Jha admitted that, beginning in 2016, he, White and Norman began to assemble the Mirai botnet – a substantial army of hijacked Internet-of-Things devices, such as security webcams – that the trio could command at will.

Using the names “Anna Senpai” and “ogmemes,” Jha operated Mirai as both a DDoS cannon that could be rented to attack companies and networks – blowing websites and servers offline – and later as a click-fraud operation that directed the malware-infected gizmos to blindly and automatically click on links in order to generate affiliate advertising money.

Source code unleashed for junk-blasting Internet of Things botnet

READ MORE

The Mirai device swarm made headlines first from its involvement in a string of massive-scale DDoS attacks in the summer of 2016 that rocked the internet, and again later that year when the source code for the malware was released. At the time, researchers speculated the blueprints would be seized upon by miscreants to spawn a new class of incredibly powerful botnets assembled from insecure IoT devices.

Jha, of Fanwood, New Jersey, admitted that he leaked the Mirai source code “in order to create plausible deniability if law enforcement found the code on computers.”

In December 2016 and into the following year, Mirai shifted its focus from DDoS to click fraud. The authorities claimed Jha and the other two operators, Norman and White, were coining it from the botnet’s activities, and cuffed the trio in January 2017.

Jha also admitted a third charge not related to Mirai. According to New Jersey’s Star-Ledger, Jha, who at the time of his arrest was enrolled at Rutgers University studying computer science, pleaded guilty to DDoSing the school’s network on multiple occasions between 2014 and 2016. ®

Article source: http://go.theregister.com/feed/www.theregister.co.uk/2017/12/13/paras_jha_mirai_guilty/

Black Hat Asia 2018: First Briefings Announced

Black Hat Asia returns to Singapore, March 20-23, 2018 with hands-on technical Trainings, cutting-edge Briefings, Arsenal open-source tool demonstrations, top-tier solutions and service providers in the Business Hall, and more.

As our Review Board members continue to work their way through a record number of submissions, we are releasing new selections in batches. Below are the first announced Black Hat Asia 2018 Briefings, with links to their abstracts.

A Deal with the Devil: Breaking Smart Contracts
By David Wong Mason Hemmel

Analyzing Breaking Exploit Mitigations and PRNGs on QNX for Automotive, Industrial, Medical and other Embedded Systems
By Ali Abbasi Jos Wetzels

Breaking State-of-the-Art Binary Code Obfuscation via Program Synthesis
By Moritz Contag Tim Blazytko

Breaking the Attack Graph: How to Leverage Graphs to Strengthen Security in a Domain Environment
By Marina Simakov

Counter-Infiltration: Future-Proof Counter Attacks Against Exploit Kit Infrastructure
By Yin Minn Pa Pa

Cyber Comrades: Alliance-Building in Cyberspace
By Kenneth Geers

Documenting the Undocumented: The Rise and Fall of AMSI
By Tal Liberman

I Don’t Want to Sleep Tonight: Subverting Intel TXT with S3 Sleep
By Jun-Hyeok Park Seunghun Han

Invoke-DOSfuscation: Techniques FOR %F IN (-style) DO (S-level CMD Obfuscation)
By Daniel Bohannon

RustZone: Writing Trusted Applications in Rust
By Eric Evenchick

Black Hat will release new Briefings on a regular basis. Keep an eye out for more announcements and register today to lock in early rates and save.

Article source: https://www.darkreading.com/black-hat/black-hat-asia-2018--first-briefings-announced/d/d-id/1330628?_mc=rss_x_drr_edt_aud_dr_x_x-rss-simple

8 Steps for Building an IT Security Career Path Program

A cybersecurity career-path program can help with talent retention and recruitment.PreviousNext

Image Source: Pixelbliss via Shutterstock

Image Source: Pixelbliss via Shutterstock

Cybersecurity professionals are in steep demand, given the projected shortfall of 1.8 million workers by 2022. But organizations can both retain their coveted cybersecurity team members so they don’t get hired away, as well as attract new talent amid competing job offers – by creating a career path program.

A majority of companies don’t provide such a program for their cybersecurity team, according to IT security career experts. But it’s a key tool to keep in-house security talent fulfilled and challenged in their jobs, and to help recruit additional talent.

“The number one reason people leave their jobs today is their company doesn’t take security seriously. What this means is that they don’t have a plan, which includes a career path plan too,” says Deidre Diamond, founder and CEO of Cyber Security Networks.

Career path programs show existing employees the role they currently hold within the organization and potential positions they may later ascend into through promotions or other moves, depending upon their interests, say cybersecurity career experts. It also gives prospective employees a view of their security career opportunities at an organization. 

Here are eight steps for creating a cybersecurity career-path program. 

 

Dawn Kawamoto is an Associate Editor for Dark Reading, where she covers cybersecurity news and trends. She is an award-winning journalist who has written and edited technology, management, leadership, career, finance, and innovation stories for such publications as CNET’s … View Full BioPreviousNext

Article source: https://www.darkreading.com/attacks-breaches/8-steps-for-building-an-it-security-career-path-program-/d/d-id/1330601?_mc=rss_x_drr_edt_aud_dr_x_x-rss-simple

Google Play Offered Fewer Blacklisted Mobile Apps in Q3

Third-party AndroidAPKDescargar store carried the most blacklisted mobile apps.

Blacklisted mobile apps are on the rise in app stores: a new report shows a 35% increase in the third quarter across 14 different online stores.

According to new data from RiskIQ, blacklisted mobile apps totaled 51,188 in the third quarter.

Mobile apps are submitted to and analyzed by anti-virus vendors when suspected of malicious behavior, says Mike Wyatt, RiskIQ’s product operations director. If such activity is detected, anti-virus vendors will block, or blacklist, the apps from downloading and running on a user’s device. Every blacklisted app that slips past an app store’s vetting process could potentially cause malicious harm to a user’s device or data.  

AndroidAPKDescargar, which offers Spanish-language mobile apps, fueled the third quarter jump with 20,907 blacklisted mobile apps – more than double its 9,285 in the prior quarter, the report notes.

Google Play, meanwhile, had fewer blacklisted mobile apps: 8,125 in Q3, down from 8,657 in the previous quarter, according to the report.

But more importantly, notes Wyatt, Google cut the percentage of blacklisted apps in Google Play to 4% of its total 204,981 apps in the third quarter – down from 8% in the previous quarter. “The percentage is a more important figure … since it indicates how likely the risk is,” Wyatt says.

Google Play and Apple’s App Store are considered the go-to place for apps by security experts, because both companies vet the apps in their stores. Nonetheless, malware-laden apps have been found in both stores. Android/TrojanDropper.Agent.BKY, for example, was discovered in Google Play.

Although the percentage and total number of blacklisted apps declined in the third quarter, Wyatt notes it is too early to say whether Google Play has improved its security.

“The Google team works hard to ensure bad apps stay out of their store, so they were able to decrease the number in the third quarter. However, we do not see a consistent downward trend, so it remains to be seen if this number will drop again in the fourth quarter,” he says.

AndroidAPKDescargar, meanwhile, did not do so well. Nearly a third of its 68,421 apps in the third quarter were blacklisted apps, a similar slice as its second quarter, the report notes. Mobile game app store 9Game.com had the highest penetration of blacklisted apps on its site in the third quarter, 97% of 5,859 apps.

Wyatt advises CISOs and security teams to educate their BYOD workers to use the official app stores and implement tighter security controls for the devices to reduce introducing a security risk.

BYOD and corporate mobile device users should also be advised to be wary of granting apps extensive permissions and also be leery of downloading apps from pages where there are misspellings on the page, says Wyatt.

Related Content:

 

Dawn Kawamoto is an Associate Editor for Dark Reading, where she covers cybersecurity news and trends. She is an award-winning journalist who has written and edited technology, management, leadership, career, finance, and innovation stories for such publications as CNET’s … View Full Bio

Article source: https://www.darkreading.com/mobile/google-play-offered-fewer-blacklisted-mobile-apps-in-q3/d/d-id/1330624?_mc=rss_x_drr_edt_aud_dr_x_x-rss-simple

Healthcare Faces Poor Cybersecurity Prognosis

Experts say the healthcare industry is underestimating security threats as attackers continue to seek data and monetary gain.

For attackers looking to steal valuable data with minimal effort, the healthcare industry is a prime target. The critical role of medical facilities, combined with poor security practices and lack of resources, make them vulnerable to financially and politically motivated attacks.

“Healthcare is clearly an attractive target and becoming more attractive,” says Viktors Engelbrehts, director of threat intelligence at eSentire. The company today released its Industry Threat Report for healthcare, one of several recent reports on the troubling state of security.

“Any attacks on healthcare can lead to loss of life,” he continues. “That’s something that a significantly higher risk than in any other industries.”

Threat actors rarely attack with the intent of causing physical harm, Engelbrehts points out. Most are looking for financial gain. eSentire reports patient records are worth between $0.05 and $2.42 USD each. Attackers can sell them on the Dark Web, use them for tax fraud or blackmail, or for conducting spearphishing campaigns.

Still, some may seek to cause physical harm. Well-known terrorist organizations are significantly improving their cyber capabilities and the idea of attacking healthcare providers to cause harm, while not imminent, “cannot be excluded in the very near future,” he says.

The threat to healthcare organizations will grow with each successful breach. But where are the biggest security holes, and how are attackers taking advantage?

Diagnosing risk

Cybersecurity is a tough enough problem for businesses to solve, and decentralized data-sharing and network-integrated medical equipment both broaden the attack surface for the healthcare industry. Most IT funds go toward business functions; only a small fraction is allocated to cybersecurity.

“Healthcare is a unique industry in the sense there are a lot of devices talking to each other all the time,” Engelbrehts says. “There is huge data traffic across different computer assets.” Medical devices are constantly sharing data, and reliance on them increases access points.

While the FDA requires security compliance in medical products, those rules are more for patient health and don’t consider the possibility of someone stealing information stored on these devices, or using them as access points into organizations.

Spence Hutchinson, threat intelligence team leader at eSentire, points out that remote access to medical data also increases risk. In his firm’s research, he says, the team noticed a lot of exposure tied back to data sharing and providing access for both patients and external contractors.

“IT resources are often outsourced, and in order to facilitate that, there’s a need for remote access into these networks,” Hutchinson explains.

How attackers take aim

Opportunistic attacks are common because of the amount of vulnerable devices. “With these, they’re generally not targeting you as an organization, they’re targeting you because you’re vulnerable,” says Engelbrehts. These attacks require no effort on the user’s part; attackers need only to find exposed devices and run the exploit.

The low security posture of most healthcare organizations may prove a target demographic for which these attacks are successful, the report states. Businesses need to be harder targets.

Engelbrehts points out the danger of ransomware, which has become a bigger part of the security conversation following major attacks this year. The downside of the publicity is it serves as a “negative commercial” for cybercriminals: if they know it’s successful, they’ll try it.

“Phishing is a big one,” he adds. “It also links to our assumption that education on cybersecurity is lacking in the industry overall.” These attacks are also opportunistic; malicious emails are spammed to thousands of email addresses, which can be found on the Dark Web.

Research from Mimecast and HIMSS emphasizes the danger of email as an attack vector. Providers say email is the biggest potential area for a breach; 9 of 10 respondents said email was critical their organizations. Of those, 43% report email is mission-critical and downtime cannot be tolerated. Attackers know email is a weak spot and are likely to take advantage.

And a new report from Positive Technologies, which focuses on Web application attacks, points out SQL injection attacks fell this quarter for the healthcare sector compared with previous quarters. However, other types of attacks including OS Commanding and Arbitrary Code Execution have grown. Attackers commonly use local file inclusion vulnerabilities, which let them take over a Web app and alter its content.

Bring it to the board

“Healthcare providers need to start realizing the cybersecurity threat for them is imminent,” says Engelbrehts. “It’s not something that might happen in time, it’s something that’s happening now in the healthcare sector.”

If cybersecurity is not top-down; if it’s not a talking point on the board of directors, it’s difficult for security teams to achieve their goals. “Each healthcare provider taking cyber seriously should have a CISO,” he adds.

Hutchinson advises adopting a threat intelligence sharing policy, something that has grown in the financial industry but doesn’t yet exist for healthcare providers. This “would definitely improve the reaction time for new and emerging threats,” he says.

Related Content:

Kelly Sheridan is Associate Editor at Dark Reading. She started her career in business tech journalism at Insurance Technology and most recently reported for InformationWeek, where she covered Microsoft and business IT. Sheridan earned her BA at Villanova University. View Full Bio

Article source: https://www.darkreading.com/vulnerabilities---threats/healthcare-faces-poor-cybersecurity-prognosis-/d/d-id/1330625?_mc=rss_x_drr_edt_aud_dr_x_x-rss-simple

80% of Americans Admit to Risky Cybersecurity Behaviors

Nearly half of survey respondents use unsecured WiFi networks and a third open unsolicited email attachment, a report finds.

A majority of Americans acknowledge they engage in behavior that puts their cybersecurity at risk, a new report from Netsparker reveals.

Based on an online survey of 2,006 US adults, the 2017 Cybersecurity Survey finds 80% admit to risky cybersecurity practices that touch on a number of areas:

  • 40% use open, unsecured networks
  • 35% click on unfamiliar links on social media
  • 31% download third-party sourced files
  • 31% open unsolicited email attachments
  • 28% fail to install Web-based security software

Survey respondents’ password protection practices are also lacking, the report finds. Thirty-four percent of respondents use the same password for all logins, while 58% admit to using fewer than four passwords for all of their online accounts.

Read more about the survey results here, when the report publishes on Thursday.   

Dark Reading’s Quick Hits delivers a brief synopsis and summary of the significance of breaking news events. For more information from the original source of the news item, please follow the link provided in this article. View Full Bio

Article source: https://www.darkreading.com/attacks-breaches/80--of-americans-admit-to-risky-cybersecurity-behaviors/d/d-id/1330627?_mc=rss_x_drr_edt_aud_dr_x_x-rss-simple

Former Rutgers Student, Two Others Plead Guilty to Operating Mirai Botnet

Trio faces up to five years in federal prison and fines of up to $250,000

Two co-founders of a DDoS mitigation firm in the New York City area and another accomplice have pleaded guilty to their role in creating and using the Mirai botnet to launch massive distributed denial-of-service attacks on several large Internet companies in 2016.

Paras Jha, 21 of Fanwood, NJ, Josiah White, 20, of Washington, Pennsylvania, and Dalton Norman, 21, of Metairie, Louisiana, each face up to five years in prison and $250,000 in fines when they come up for sentencing next year.

Jha and Norman have also pleaded guilty to renting out the botnet to other cybercriminals for click-fraud purposes- another crime with a potential five-year sentence and $250,000 fine. The three plea agreements were entered in the US District Court for the District of Alaska Dec. 8 and unsealed Wednesday.

Separately, Jha on Dec. 13 also pleaded guilty in a Trenton federal court to repeatedly crashing the computer network at Rutgers University between 2014 and 2016 while he was computer science major there. Jha, who is out an a $25,000 bond, faces up to 10 years in prison for his attacks on Rutgers, but will likely get less under the terms of his plea agreement.

Raj Samani, chief scientist at McAfee, says developments like this week’s plea agreements are important to fighting cybercrime. “Actions such as these send a clear message, whether you are carrying out the campaigns or enabling such activities that there is no such thing as zero risk,” he says.

McAfee recently polled ransomware developers on why they were involved in the activity and many saw it as a high-reward, low-risk activity, Samani says. “The growth in the as-a-service economy is one of the main motivating factors on the increase of attacks, and this recent news sends a clear message.”

The Mirai botnet was the first large-scale DDoS attack network comprised almost entirely of infected Internet of Things (IoT) devices such as home routers and Web-connected security cameras and DVRs. Among other things, the malware was designed to conduct attacks against a target’s entire range of IP addresses.

DDoS attacks that were launched with the Mirai botnet crippled or disrupted services at many large Internet companies in fall 2016. One of them, on Domain Name Services provider Dyn, affected multiple websites including those belonging to CNN, Twitter, Okta, Netfix, and Reddit. Some of the attacks generated DDoS traffic in excess of 1 Tbps, several magnitudes bigger than average DDoS attacks.

In their plea agreement, Jha and White – who operated a small DDoS mitigation firm called ProTraf Solutions – and Norman, admitted to developing the Mirai malware and using it to build a massive botnet of infected devices. During a period between July 2016 and late fall 2016, the Mirai co-authors scanned for and ultimately infected some 300,000 IoT devices worldwide, by exploiting previously known and unknown vulnerabilities in the products.

Between August and September last year, the trio then used the botnet to attack several websites and webhosting companies in the US and elsewhere and sought to profit from it by offering DDoS mitigation services to some of the victims.

Security blog KrebsOnSecurity, which was the first to identify Jha as being one of those potentially behind the attacks, described Jha and White as using the botnet to primarily target the operators of large online gaming servers to try and extort money from them. In addition to using the botnet themselves, the pair actively tried to lease the botnet out to other cybercriminals by among things, advertising it on underground forums.

Cover-Up Attempt

Around Sept. 2016, Jha, White, and Norman released Mirai code into the open in an apparent attempt to create plausible deniability and then took steps to destroy all evidence of their connection to the malware. The public release of the malware online in turn resulted in the creation of several Mirai variants that were then used by others in separate attacks.

In addition to operating the botnet for DDoS purposes, Jha and Norman also sought to profit from Mirai in other ways. Between Dec. 2016 and February 2017, the two individuals infected some 100,000 IoT devices primarily in the US and used them for click fraud purposes. Basically, the two individuals used the infected devices to send high volumes of view requests to webpages with affiliate advertising content to make it appear like real users had clicked on the ads. Jha and Norman made the equivalent of some $180,000 in bitcoin from the click fraud.

Jha’s attacks on Rutgers University’s computer network, meanwhile, took place between Nov. 2014 and Sept. 2016, and appeared designed to create maximum disruption for the institution. Among other things, the attacks shut down the university’s central authentication server and a portal for delivering assignments and assessments, sometimes for multi-day periods.

John Pescatore, director of emerging security threats at the SANS Institute, says that as with the real world, the real deterrent for cybercrime is the possibility of getting caught.

“Whether it is shoplifting, bank robbery, counterfeiting, or ransomware, if the probability of getting caught is seen to be real low, it doesn’t matter if the fine is $5 or $5 million,” he says. “In cybercrime, it has been all too easy to get away with. Publicity over those getting caught is important and I think acts as more of a deterrent than does the size of the fine or jail sentence.”

Related Content:

 

Jai Vijayan is a seasoned technology reporter with over 20 years of experience in IT trade journalism. He was most recently a Senior Editor at Computerworld, where he covered information security and data privacy issues for the publication. Over the course of his 20-year … View Full Bio

Article source: https://www.darkreading.com/attacks-breaches/former-rutgers-student-two-others-plead-guilty-to-operating-mirai-botnet/d/d-id/1330633?_mc=rss_x_drr_edt_aud_dr_x_x-rss-simple

Google Sheds Light on Data Encryption Practices

Google explains the details of how it secures information in the cloud and encrypts data in transit.

Following a year of major cyberattacks and security threats, Google has published two whitepapers to explain how it secures data. One focuses on encryption of data in transit; the other on service-to-service communication using Application Layer Transport Security (ALTS).

Google gets a lot of questions from customers on how it protects data, says Maya Kaczorowski, Google Cloud security and privacy product manager. Today’s release details the steps taken to protect authenticity, integrity, and privacy by verifying data sources, ensuring data arrives unchanged, and keeping data confidential while in transit.

Encryption in transit refers to “how data moves from a user to Google, and how it moves within Google’s infrastructure,” she explains. When a user sends data to the Google Cloud, it’s encrypted in transit by default using HTTPS and TLS. Both of these are common practice; Google introduces more security for data traveling outside its infrastructure.

Google Cloud encrypts and authenticates all data in transit, at multiple network layers, when it moves outside physical boundaries not under Google’s control. Data within these boundaries is authenticated but not always encrypted because strong security measures are already in place.

“When running at Google’s scale, performance is important,” Kaczorowski says. “Different modes of protection we use depend on the threat model and performance requirements that we have.”

To protect against potential threats, she continues, Google assumes the external wide-area network “is only semi-trusted.” Encrypting data protects it from active adversaries who could spy, inject, or alter traffic on the wire, Kaczorowski explains in a blog post on today’s release.

On a network level, Google Cloud’s virtual network infrastructure automatically encrypts data moving between virtual machines if it crosses a physical boundary Google doesn’t control.

“Once the data is inside Google, the first thing to understand is not all data in transit within Google is protected the same way,” says Kaczorowski.

The ALTS protocol, discussed in detail in the second whitepaper, is a mutual authentication and transport encryption system. Google usually uses it to secure Remote Procedure Call (RPC) communications from service to service within its infrastructure. Each of these internal services has a service account identity with cryptographic credentials used for authentication.

ALTS is similar to TLS but designed specifically for Google’s data centers. It relies on two protocols, the Handshake and Record protocols, both of which dictate how sessions are established, authenticated, encrypted, and resumed, as explained in the paper.

The trust models of TLS with HTTPS semantics, and ALTS, are significantly different, Google says in the paper. The former binds server identities to a specific name and associated naming schemes. The latter uses the same identity for multiple naming schemes, adding flexibility and simplifying the process of load balancing, microservice replication, and scheduling between hosts. ALTS is simpler in design and implementation, Google says, making it easier to monitor for bugs and vulnerabilities using manual source code inspection or fuzzing.

There are a few trade-offs to using ALTS over TLS, the company points out. For example, it’s not designed to conceal the internal services communicating; as a result, it doesn’t encrypt handshake messages to hide identities.

The ALTS handshake protocol is also susceptible to Key Compromise Impersonation attacks. If an attacker compromises the Diffie-Hellman key used during the handshake, or the resumption key of a workload, they can use that key to make illegitimate workloads appear authentic.

On top of default protections, Google lists additional options to encrypt data in transit: IPsec tunnels, free and automated TLS certificates, and Istio, an open-source service mesh developed by Google and other companies, including Lyft and IBM, to help with service discovery.

Related Content:

Kelly Sheridan is Associate Editor at Dark Reading. She started her career in business tech journalism at Insurance Technology and most recently reported for InformationWeek, where she covered Microsoft and business IT. Sheridan earned her BA at Villanova University. View Full Bio

Article source: https://www.darkreading.com/cloud/google-sheds-light-on-data-encryption-practices/d/d-id/1330634?_mc=rss_x_drr_edt_aud_dr_x_x-rss-simple

Apple plugs IoT HomeKit hole

Apple just can’t seem to get away from the theme of security flaws right now.

Last month it was the macOS 10.13 root password issue, hot on the heels of the news that the iPhone’s X’s much-vaunted Face ID authentication could be bypassed using a prosthetic mask.

And it only seems fair to mention the small matter of the ‘show your password hint in encrypted APFS volumes’ issue macOS High Sierra users were told about in October.

Even Google’s Project Zero has got in on the act, publishing news of a jailbreaking proof-of-concept for iOS and macOS that seemed designed to draw attention to unexpected weaknesses in once-impregnable Apple software.

Now a researcher has discovered that Apple’s HomeKit Internet of Things (IoT) framework has a vulnerability serious enough to allow an attacker to control IoT devices using its protocol, such as thermostats, lights, power points, air conditioners, as well as smart home locks and garage door openers.

Who would secure their home with an IoT smart lock that can be disabled remotely? Probably nobody would. But the mere fact such a thing is even possible is a poor advert for the future of the smart home.

Apple has plugged the hole by temporarily disabling HomeKit’s shared remote users feature, which will be restored this week when iOS is updated.

In HomeKit’s defence, the vulnerability is described as being “difficult to reproduce,” but that won’t buy it much sympathy.

It’s clear that researchers are going after Apple in the same way as any big company.

As Naked Security has pointed out before, despite the embarrassing headlines, this is good news. If there’s one thing that’s worse than researchers tearing a company’s software open, it’s researchers not tearing it open until it’s too late.


Article source: http://feedproxy.google.com/~r/nakedsecurity/~3/w2uwb98mcfg/