STE WILLIAMS

Ep. 024 – Sextortion, malicious adverts and randomness [PODCAST]

In this Naked Security podcast, we explain how to handle sextortion, look at techniques for getting rid of malvertising, and discuss the things that make randomness hard.

With Anna Brading, Paul Ducklin, Mark Stockley and Matthew Boddy.

This week’s stories:

Related comments – how to report cybercrime online:

If you enjoy the podcast, please share it with other people interested in cybersecurity, and give us a vote on iTunes and other podcasting directories.

Listen and rate via iTunes...
Sophos podcasts on Soundcloud...
RSS feed of Sophos podcasts...


Thanks to Purple Planet for the opening and closing music.


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

Elsevier exposes users’ emails and passwords online

Elsevier – publisher of scientific journals such as The Lancet – has left its users’ passwords and email addresses lying around online.

What Motherboard described as a “rolling list of passwords,” along with password reset links produced when a user requested a change to their login credentials was discovered by cybersecurity company SpiderSilk. It’s unclear how many records were exposed and for how long.

Mossab Hussein, SpiderSilk chief security officer, said that most of the exposed accounts are related to educational institutions, and hence belong to either students or teachers.

To paraphrase a Twitter wit… What could go wrong besides hackers making sure all their journal submissions get accepted?

For one thing, those email addresses/passwords could be used on other, sensitive sites, as Hussein pointed out. With the depressing ubiquity of password reuse, some of them undoubtedly are sprinkled around elsewhere online.

According to Motherboard’s Joseph Cox, the credentials were displayed on Kibana, a popular tool for visualizing and sorting data.

Motherboard verified that the credentials were valid by asking Hussein to reset his own password to a specific phrase fed to him by Motherboard. Cox writes:

A few minutes later, the plain text password appeared on the exposed server.

Elsevier secured the server after getting a heads-up from Motherboard and details from Hussein. An Elsevier spokesperson sent Motherboard a statement in which the publisher blamed a misconfigured server:

The issue has been remedied. We are still investigating how this happened, but it appears that a server was misconfigured due to human error. We have no indication that any data on the server has been misused. As a precautionary measure, we will also be informing our data protection authority, providing notice to individuals and taking appropriate steps to reset accounts.

As others have pointed out, saying that the passwords are no longer exposed doesn’t explain why they were stored in plain text to begin with. Hopefully, Elsevier will pay attention to that, as well as to the misconfigured server that left them hanging on the line like a discarded beach towel.

If you’re an Elsevier user

Reset your passwords, and if you know you’ve used the same password on other website – change those too! Watch out video on how to pick a strong unique password below:

(No video? Watch on YouTube. No audio? Click on the [CC] icon for subtitles.)

And if a website gives you the option to turn on two-factor authentication (2FA or MFA), do that too. Here’s an informative podcast that tells you all about 2FA, if you’d like to learn more:

LISTEN NOW

(Audio player above not working? Download MP3 or listen on Soundcloud.)

 

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

Firefox 66 now blocks autoplaying audio by default

Updated 20 March 2019

It’s been on the to-do list for a while, but Mozilla announced yesterday that with the release of Firefox 66 for desktop and Firefox for Android this week, media autoplay of video or audio is now blocked on websites by default.

According to Mozilla’s developer blog, this means that when users:

Go to a site that plays videos or audio, the Block Autoplay feature will stop the audio and video from automatically playing. If you want to view the video, simply click on the play button to watch it.

Until the user does something to initiate a video or audio stream, the only thing that will be possible is muted autoplay.

If you find it annoying when videos starting of their own accord, this will come as a welcome news. But what about use cases where it’s desirable?

Currently, it is possible to achieve autoplay blocking by toggling a setting from about:config (type that into your Firefox address bar), but that is a global setting and is either on or off.

Under the new regime, there are several options: enabling autoplay once on a website, white-listing websites to always allow autoplay from those sites, or always allow or block autoplay for all websites.

Audio conundrum

When it comes to media autoplay blocking, version 66 seems to be the number to aim for – Google implemented a similar default setting with Chrome 66 in April last year.

Apple has had default blocking since June 2017, while Microsoft offered the ability for users to turn off autoplay last summer (i.e. it’s an option rather than a default).

One thing Firefox doesn’t yet block is audio that is enabled through the JavaScript Web Audio API used by many older games and web apps.

Stated Mozilla:

We expect to ship with autoplay Web Audio content blocking enabled by default sometime in 2019.

It’s an area where browser makers have to tread carefully, as Google found out to its cost when it included Web Audio API blocking by default to Chrome 66 and was assailed with complaints about broken software.

This article was originally published on 6 February 2019

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

Hacked tornado warning systems leave Texans in the dark

Last week, around 2:30 a.m., blaring emergency sirens woke the people of two Texas towns… and then, until about 4:00 a.m., the alarms kept sounding, on and off, until crews finally managed to turn them off.

The towns of DeSoto and Lancaster are both in Tornado Alley: one of two regions of the US that have a disproportionately high frequency of tornadoes (the other being Florida). The outdoor alerts are meant to warn people to get to safety. But there were no tornados on 12 March: just the noise of false alarms that had been set off by hackers, as officials of the two towns concluded.

Over 30 sirens kept going on and off, with 10 in DeSoto and 20 in Lancaster.

The city of DeSoto said in a statement that there was no malfunction in the warning system. The false alarms set off in both cities seem to have been triggered intentionally. The matter’s been turned over to the affected cities’ police departments for investigation.

City residents took to Twitter to try to figure out what was going on:

Lancaster officials warned that whoever’s responsible is looking at arrest and prosecution:

Based on the widespread impact to the outdoor sirens located in two separate cities, including Lancaster, it has become evident that a person or persons with hostile intent deliberately targeted our combined outdoor warning siren network.

Sabotage against a public warning system is more than vandalism. It is a criminal act and those responsible are subject to arrest and prosecution.

The cities managed to take the hacked systems offline the next morning, and as of Monday this week, they were still offline.

Fortunately, the residents of the two cities lucked out. Severe storms, and possibly tornados, had been announced for the entire week in North Texas. But although a severe thunderstorm did hit the two cities on the night following the false alarms, it brought no tornado with it.

It if had, they wouldn’t have been able to warn residents with the external alerts. There are backup systems, though, for residents to stay informed and to receive warnings. DeSoto officials said:

The main purpose of these sirens is to alert people who are outside during inclement weather to seek shelter inside. Once a person is safe inside, the most important thing that they can do is to secure the most current and accurate weather information possible. The first step should be for all DeSoto residents to sign up for the Code Red emergency weather warning system which was not impacted. […]

We will continue to make every effort to safely restore our outdoor siren system and to work with our law enforcement agencies in any follow-up investigations that are conducted.

The city of Lancaster likewise said that it’s consulting with technical experts about the warning systems and following up with police on the investigation into the hacking. Lancaster, like DeSoto, said that it’s relying on the Code Red emergency weather warning system, the city website, and social media for communications.

Take a spin on the Fear-o-rama

Texans have seen their share of fear-and-panic-spreading public systems hacks before.

On a Friday night in April 2017, 18 minutes before midnight, every single one of Dallas’s 156 emergency weather sirens started doing this:

They blared for an hour and a half – “to the annoyance, terror or amusement of 1.3 million residents,” as the Washington Post reported. It took months to encrypt all the sirens and get them up and running again.

In that instance, a hacker exploited a “radio issue” to set off the sirens in the middle of the night. Dallas responded by adding encryption to the radio signal that controlled the city’s sirens, preventing any amateur radio enthusiasts from again hijacking the control signal.

Other warning systems have likewise been hacked to trigger false alarms, including a fake missile alert in Hawaii in January 2018.

People sought shelter by crawling under tables in cafes, were ushered into military hangars, and huddled around TVs to watch the news for the latest developments. Some put their kids into the bathtub, others sought shelter in tunnels, while some tried to get to the airport to clear out before the heavens rained down.

That one was immediately followed by Japan doing the same thing: because of a switching error, another fake missile alert was sent out. The false alert said that North Korea had probably launched a missile and warned people in Japan to take cover.

Then, in January 2019, a much more domestic but just as terrifying false alert was blasted out to a family by way of their security camera. The hacker took over a family’s Nest security camera to broadcast a fake warning about three incoming intercontinental ballistic missiles (ICBM) launched from North Korea, sending a family into “five minutes of sheer terror.”

To paraphrase one Tweet on the subject of the North Texas tornado system hacks, it takes one hell of a keyboard-thumping lump – one who lacks humanity – to leave people sitting in the dark like that, a life-threatening storm potentially headed their way.

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

Researchers fret over Netflix interactive TV traffic snooping

No sooner has Netflix made an interactive TV show than people are pulling apart its privacy implications and fretting about its potential to leak private information. Research published last week said that it is possible to deduce viewers’ choices from the platform’s interactive TV shows, like Bandersnatch.

After a couple of smaller projects, Bandersnatch was Netflix’s first big foray into interactive TV. Based in 1984, the episode in Charlie Brooker’s Black Mirror series lets the reader control the actions of a young video games programmer Stefan Butler, who idolises established games programmer Colin Ritman. Throughout the episode, the viewer gets to control his actions, including seemingly innocuous choices such as which cereal to eat. The choices guide you down a range of paths concluding in one of several endings for the story.

It’s an idea that anyone who grew up on the Choose Your Own Adventure and Fighting Fantasy book series will warm to. Unlike the books, Netflix records your story choices digitally, and the researchers believe that could pose a privacy problem.

According to their paper, although Netflix uses end-to-end encryption to send those choices from your viewing device to its servers, communication flaws still make it possible to snoop on what you choose. The paper says:

Recent advancements in the domain of encrypted network traffic analysis make it possible to infer basic information about the preferences of Netflix viewers.

The researchers realised that viewers’ devices indicated their choices by sending a JSON file (JSON is a human-readable text file commonly used in cloud-based software queries). It would send one of two different JSON files for each choice, based on what the user chose. By working out the JSON file type and the point in the program when it was sent, they could work out the users’ choices.

Netflix encrypts those JSON files using the SSL encryption mechanism, but they got around that by looking at the record length of each SSL request in bytes. The lengths almost always fell into distinct ranges, meaning that they could identify the two types of JSON files – and therefore the viewer’s choice – 96% of the time.

The problem is readily fixable, the researchers concluded:

An easy fix for the problem would be to either split the JSON file or to compress it so that it becomes indistinguishable.

Does it matter?

So, that’s the technical bit done with. The real question is: who cares? The research team thinks that it’s a potential issue:

The choices made and the path followed can potentially reveal viewer information that ranges from benign (e.g., their food and music preferences) to sensitive (e.g., their affinity to violence and political inclination).

True, the choices you make in Bandersnatch could identify you as a Thompson Twins or a ‘Now That’s What I Call Music’ fan (that’s one of the choices you get to make). Some would argue that this doesn’t matter all that much. However, the paranoid may worry that future shows – and Netflix is planning more – could get you to reveal more about yourself.

While it’s possible that third-party network providers could slurp your SSL packets to work out your choices and use them to try to infer things about you, it’s more likely that Netflix itself would use this data to understand the choices its audiences make at an aggregate level – and of course it doesn’t need to snoop on its own data.

This could enable its production partners to factor that feedback into their writing. Are more people choosing confrontational or peaceful paths? What percentage of its audience choose the romantic ending rather than the sad one?

The best comment on the whole affair comes from one Register reader in the comment section:

Maybe Charlie Brooker should write an episode of Black Mirror about how someone’s Bandersnatch choices turned them into a social pariah.

What do you think? Are you worried about Netflix – or anyone else – monitoring your interactive TV choices?

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

Google researcher discovers new type of Windows security weakness

Microsoft has said it plans to patch a new class of Windows security bug discovered by a Google Project Zero researcher despite finding no conclusive evidence that it poses a threat to users.

The unusual and complicated weakness appears to have been sitting unnoticed in Windows since as far back as XP and will be patched in the next version of Windows 10, currently named 19H1 (aka version 1903).

But if it’s not a clear threat, why patch it at all? For the answer to that, we need to explore the backstory.

According to Project Zero researcher James Forshaw, he first discovered what he assumed was a relatively straightforward kernel-mode drive Elevation of Privileges (EoP) issue in 2016, eventually fixed by Microsoft as CVE-2016-3219.

Following up a year later, however, he realised he’d stumbled upon a larger logic hole that might allow malware running in user mode (which limits privileges) to sneak privileges through the interaction of Microsoft and third-party kernel-mode drivers and the Windows I/O manager subsystem.

However, Forshaw was still unable to create a working proof-of-concept (many aspects of these deeper code interactions are difficult without proprietary knowledge), forcing him to contact Microsoft for help:

This led to meetings with various teams at Bluehat 2017 in Redmond where a plan was formed for Microsoft to use their source code access to discover the extent of this bug class in the Windows kernel and driver code base.

After a lot of work running numerous code interactions through static analysis tools, Microsoft decided:

There appeared to be no combination of initiator and receiver [jargon for API functions] present in currently supported versions of Windows that could be used for local privilege escalation out of the box.

However, because there are numerous third-party drivers that might be exploitable, and because the class of bug found by Forshaw seemed so new and unexpected, Microsoft decided to take a cautious approach and patch the issue anyway.

One possibility was making a full-scale API change, but this was ruled out because it risked breaking existing software.

As well as issuing a fix in the next Windows version due in April, Microsoft plans to update its programming documentation to draw attention to the issue and wants developers to review their code…

…to ensure correct processing of IRP requests and defensive use of the file open APIs.

Peace breaks out

Considering the way that the two companies have bickered in the past over the issue of Google’s strict 90-day disclosure timetable, the praise for Forshaw from Microsoft is unexpectedly warm:

One researcher who consistently reports high-quality, interesting vulnerabilities to us is James Forshaw of Google Project Zero.

Even so, Google’s Forshaw couldn’t resist a tiny dig regarding specific elements of the weakness:

It’s worth noting that while I applied the standard 90-day disclosure deadline to the SMB server report, I didn’t apply an explicit deadline to the bug class report.

High-fives all around, then – for now at least.

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

Silence of the WANs: FBI DDoS-for-hire greaseball takedowns slash web flood attacks ‘by 11%’

The FBI’s takedown of a group of prolific DDoS-for-hire websites has single-handedly helped to drop attack levels globally.

This is according to a report (registration required) from distributed-denial-of-service (DDoS) mitigation provider NexusGuard, who say that both the overall number of attacks and the volume of duff data fired at targets to overwhelm them are down, thanks to the December 2018 push that saw the feds wipe out 15 DDoS mercenary sites.

Those outfits, run in part in America, allowed people to purchase temporary use of massive botnets of compromised devices that were, in turn, commanded to generate massive loads of network traffic at targeted websites and services, overloading and knocking them offline.

It seemed those 15 DDoS services were so prolific (at the time of the takedown the FBI estimated that the group had carried out more than 300,000 attacks over the last five years) that simply taking them offline has caused a noticeable drop in global activity for the entire fourth quarter.

Compared to the same quarter last year, NexusGuard says that the number of attacks fell by 11 per cent. What’s more, the size of each attack (the traffic load directed at the target) took a nosedive, with the average rate dropping 85 per cent and the maximum size down 24 per cent from Q4 2017.

These numbers are particularly noteworthy given the takedown happened with just ten days left in the quarter- though it should be noted that the days around Christmas and New Year’s are by far the busiest for DDoS attacks, and attacks typically surge in the back half of December.

Put down the champagne

The huge dip in attacks may not last, however. NexusGuard says it expects new DDoS-for-hire services to soon step in and fill the void left by those taken down by the FBI, and at that point attack levels will likely rise.

Not surprisingly, IoT botnet attacks were all the rage last quarter, according to the report. Simple Service Discovery Protocol (SSDP) amplification attacks from UPnP devices – such as IP-enabled cameras, printers, and routers – were up a staggering 3,122 percent from last year, it is claimed, and accounted for nearly half (48 percent) of all attacks seen on the quarter.

Essentially, you launch a load of small requests at a bunch of devices on SSDP UDP port 1900, spoofing the source IP address as your victim’s IP address. The devices all respond to the victim, flooding it with data. The amount of information sent from the gadgets to the victim is huge compared to the initial request wave, hence an amplification attack.

Dude in jail

Brit hacker hired by Liberian telco to nobble rival now behind bars

READ MORE

“Perpetrators first discover and scan all exploitable devices and then use botnets to send UDP packets with a target’s spoofed IP address to UDP port 1900 of all exploitable devices,” NexusGuard said in explaining the technique. “In turn, the devices respond massively, causing the target to become inundated with a large volume of replies.”

The growth in SSDP attacks meant more conventional techniques all went down compared to the year-ago quarter.

Less surprising was the distribution of where those attacks were coming from (as in where the bots launching it were based.) China was the most common, accounting for 23 per cent, followed by the US, with 18 per cent. This is to be expected, notes NexusGuard, as the US and China also account for around a third of the total online population.

France (7 per cent), Russia (4 per cent), and Brazil (2.5 per cent) rounded out the top five. ®

Sponsored:
Becoming a Pragmatic Security Leader

Article source: http://go.theregister.com/feed/www.theregister.co.uk/2019/03/19/fbi_ddos_for_hire/

DDoS Attack Size Drops 85% in Q4 2018

The sharp decline follows an FBI takedown of so-called “booter,” or DDoS-for-hire, websites in December 2018.

The average distributed denial-of-service (DDoS) attack size shrunk 85% in the fourth quarter of 2018 following an FBI takedown of “booter,” or DDoS-for-hire, websites, in December 2018, researchers report.

Late last year, United States authorities seized 15 popular domains as part of an international crackdown on booter sites. Cybercriminals can use booter websites (also known as “stresser” websites) to pay to launch DDoS attacks against specific targets and take them offline. Booter sites open the door for lesser-skilled attackers to launch devastating threats against victim websites.

About a year before the takedown, the FBI issued an advisory detailing how booter services can drive the scale and frequency of DDoS attacks. These services, advertised in Dark Web forums and marketplaces, can be used to legitimately test network resilience but also make it easy for cyberattackers to launch DDoS attacks against an existing network of infected devices.

The shutdown of prominent booter sites made a pronounced difference in DDoS attack trends for the fourth quarter of 2018, researchers report in Nexusguard’s DDoS Threat Report 2018 Q4. During the most recent quarter, the number of DDoS attacks fell nearly 11% year-over-year, and the maximum attack size decreased nearly 24%. The biggest difference was in attack size, which dropped 85%.

Booter sites are the origin for many DDoS attacks as they make it “fairly simple” for amateur hackers to take down websites, explains Donny Chong, product director at Nexusguard. While the shutdown of booter sites had a positive effect on DDoS trends year-over-year, the growing prevalence of the “bit-and-piece” technique caused attacks to grow quarter-over-quarter.

The bit-and-piece tactic avoids detection by injecting small pieces of malicious code into legitimate traffic across hundreds of IP prefixes, Chong explains. By using small bits of junk, adversaries avoid sounding the alarms that large traffic spikes would set off. Between third and fourth quarters of 2018, this method caused the number of attacks, and the maximum and average attack sizes, to increase 36%, 49%, and 3.75%, respectively, Nexusguard researchers found.

Nexusguard noticed the bit-and-piece trend emerge in the third quarter, when it was the focus of its threat report. Unlike in a typical DDoS attack, in which an actor identifies and targets a particular IP address, bit-and-piece attacks are spread across multiple IP addresses on the same prefix. Diffused traffic can cause service providers to miss large-scale DDoS attacks in progress.

SSDP Amplification Attacks Ramp Up
SSDP amplification attacks are the most popular bit-and-piece attack vector and increased by 3,122% year-over-year and 91.2% quarter-over-quarter, Nexusguard reports. This type of attack, which made up 48.3% of DDoS attacks overall, is launched over UDP via Universal Plug and Play devices (printers, webcams, routers, and servers, for example).

In SSDP amplification attacks, adversaries first scan exploitable devices and use botnets to send UDP packets with a target’s spoofed IP address to UDP Port 1900 of all vulnerable devices. Devices “respond massively,” researchers explain, and the target is overwhelmed with replies.

Will cybercriminals leverage bit-and-piece attacks in lieu of DDoS attacks following the booter site shutdown? “It’s going to be very dependent on who they are attacking,” says Chong. In the world of DDoS, where attackers really study their targets, some attacks could be more effective. He calls it a “cat-and-mouse” game between cyberattackers and defenders: Even as criminals adopt SSDP and UDP attacks, targets will start to catch on to their patterns and block them.

Chong believes DDoS-for-hire websites are sure to make a comeback. “Definitely,” he notes, adding that the decline in DDoS attack size is likely to reverse itself in the future. “These booters represent only a surface of the entire problem. [They’re] payment gateways, the shopping carts by which you activate those botnets.” Further, he explains, the growth of consumer Internet of Things contributes to the number of vulnerable devices exposed to cyberattacks.

Related Content:

Kelly Sheridan is the Staff Editor at Dark Reading, where she focuses on cybersecurity news and analysis. She is a business technology journalist who previously reported for InformationWeek, where she covered Microsoft, and Insurance Technology, where she covered financial … View Full Bio

Article source: https://www.darkreading.com/vulnerabilities---threats/ddos-attack-size-drops-85--in-q4-2018/d/d-id/1334197?_mc=rss_x_drr_edt_aud_dr_x_x-rss-simple

Microsoft Office Dominates Most Exploited List

Lone Android vulnerability among the top 10 software flaws most abused by cybercriminals.

It should come as no surprise that cybercriminals favored Microsoft Office vulnerabilities in their cyberattacks last year, given the rise in phishing attacks that included rigged Word and Excel Office file attachments.

Eight of the top 10 most exploited vulnerabilities in 2018 were Office bugs, according to a new study by Recorded Future. An Adobe Flash bug (No. 2) and an Android flaw (No. 10) also made the list, which led with a Windows remote code execution exploit that was found in several exploit kits, including Fallout, KaiXin, LCG Kit, Magnitude, RIG, Trickbot, and Underminer.

It’s a natural progression given the shift from cybercriminals employing Web exploit kits to waging more phishing campaigns in 2018, notes Alan Liska, threat intelligence analyst at Recorded Future.

The shift away from browser exploits is due to developers better securing and enforcing updates to their browser software, he says. Just three of the top 10 vulns on the list were browser-related, involving older versions of Internet Explorer. “That means there are a whole lot of older systems still running unpatched [browsers],” he says.

Meanwhile, just five new exploit kits arrived in 2018, down from 10 new ones in 2017 and 62 in 2016, according to the study, which analyzed code repositories, Dark Web forum postings and sites, as well as other metadata. And just two new exploit kits – Fallout and LCG Kit – made the Top 10 most exploited vulns list for 2018.

While Recorded Future excluded nation-state groups from the list, the study also comes amid a throwback to old-school hacking by both cybercriminals and nation-states: using stolen user credentials, including Remote Desktop Protocol (RDP) and VPN logins or credential-stuffing attacks to hit a targeted organization, rather than throwing malware at the victim.

“I think the trend line of fewer exploit kits” supports this, Liska says. “There are other points of entry taking away from where we see vulns being deployed. If you focus on brute-force attacks and using tools to enable that, you’re not necessarily going to need to use an exploit kit or these vulns if you can walk in with credentials.”

Source: Recorded Future

“We spend a lot on threat-sharing,” notes John Bambenek, director of cybersecurity research at ThreatStop. “But if there are no indicators to share except people sharing credentials, there’s no real defense except not to have [weak] passwords.”  

And exploit tools, including zero-day vulnerabilities, increasingly are only being used by nation-states, not cybercriminals. “Zero-days are immensely valuable resources. Why throw them into an exploit kit when you can sell them to an intel agency for seven figures?” he explains. “Criminals are getting their payday, anyway … just having email lists and mail servers,” for example, he says.

Android Cracks the Top 10
The only mobile device flaw on the Recorded Future top 10 list was a critical 2015 local elevation of privilege vulnerability in the kernel of some Android devices. It made the list for the first time and for the same basic reason Microsoft Office did, according to Liska: It’s a popular platform with a wide attack surface. And some Android devices are more secure than others, he notes of the open-source mobile platform.

“The most exploitation we saw with the Android vuln occurs in various Android stories – through bad apps or rigged apps,” Liska says. 

Mobile remains a small portion of the attack surface to date, though. A recent study by Sophos found that 10% of cybercriminal attacks are discovered on mobile devices, while 37% are detected at the server and 37% at the network. “We don’t see a lot of compromises [via] mobile. We don’t see a lot of big incidents starting with the phone,” says Chester Wisniewski, principal research scientist for Sophos.

Meanwhile, “Double Kill,” the Microsoft IE flaw that holds the No. 1 slot for the most exploited, operates over multiple versions of IE and Windows, which made it especially popular, according to Liska. “The way its kit works is that it sends a probe – usually a JavaScript [one] – and queries information on the browser to find out as much as it can about the operating system, browser version, and patches installed” on the victim’s machine, he says. “Then it chooses the exploit to throw at it. It’s so easy to use.”

The No. 2 vuln exploited last year was CVE-2018-4878, an Adobe Flash Player use-after-free flaw that was packaged in several exploit kits, including Fallout and the former Nuclear kit. Fallout spreads the prolific GandCrab ransomware, which increasingly is being deployed in targeted attacks against large organizations to get a better bang for the buck for the attackers.

Adobe plans to kill off the historically flawed and targeted Flash Player in 2020. Meanwhile, though, Flash holds the dubious record for the fastest exploitation of flaws: Once Adobe reveals and issues a patch for one of Flash’s bugs, on average it gets exploited within two days, according to Liska.

A remote-access Trojan also made Recorded Future’s most exploited list: CVE-2017-8570, an Office remote execution flaw, comes with the Sisfader RAT.

Same Old, Same Old
While the top 10 most exploited vulnerabilities list is intended to help organizations prioritize their patching rollouts, Recorded Future’s recommendations for preventing attacks from these exploits are the usual security hygiene checklist: Steer clear of Flash on websites, use browser ad blockers to protect from malvertising, execute frequent backups, and train users on phishing awareness and other scams via email. The company also advises running Google Chrome browser, which is considered one of the most secure.

Related Content:

 

 

Join Dark Reading LIVE for two cybersecurity summits at Interop 2019. Learn from the industry’s most knowledgeable IT security experts. Check out the Interop agenda here.

Kelly Jackson Higgins is Executive Editor at DarkReading.com. She is an award-winning veteran technology and business journalist with more than two decades of experience in reporting and editing for various publications, including Network Computing, Secure Enterprise … View Full Bio

Article source: https://www.darkreading.com/vulnerabilities---threats/microsoft-office-dominates-most-exploited-list/d/d-id/1334198?_mc=rss_x_drr_edt_aud_dr_x_x-rss-simple

Microsoft won’t patch Windows registry warning problem

A security researcher has found a way to tinker with Windows’ core settings while persuading users to accept the changes, it emerged this week – and Microsoft has no intention of patching the issue.

The attack was discovered by John Page, who goes by the name hyp3rlinkx. It focuses on the Windows registry, which is a database of configuration settings for software programs, hardware devices, user preferences and the operating system itself.

Users can make changes to the registry using the Registry Editor program that ships with Windows, but this isn’t something that non-power users would normally do. Messing with the registry can cripple your machine or introduce security risks.

In most cases, when a Windows user really must make changes to the registry, they’ll do it by clicking on a file with a .reg extension. These files, provided by a trusted third party, alter the registry without the user having to enter anything.

This is why a dialog box appears when opening a .reg file, asking users if they trust the source and if they want to continue. It will then offer a ‘yes’ or ‘no’ choice.

Page’s attack changes that. In a document describing the process, he explains:

…we can inject our own messages thru the filename to direct the user to wrongly click “Yes”, as the expected “Are you sure you want to continue?” dialog box message is under our control.

He does this by using a carefully-crafted filename that uses characters encoded with the % symbol. The right character combination can delete the warning message and questions in the dialog box, replacing it with text that the attacker has put in the .reg filename. He continues:

This spoofing flaw lets us spoof the “Are you sure you want to continue?” warning message to instead read “Click Yes” or whatever else we like. Potentially making a user think they are cancelling the registry import as the security warning dialog box is now lying to them.

Users of older Windows versions may still get suspicious, because pre-Windows 10 versions present a second dialog box confirming the registry change. However, Page was able to get rid of that box in Windows 10 by including a character combination to indicate null at the end of the filename.

The attack works with non-privileged (that is, non-administrator) users. If attempted by a user with administrator privileges, it will launch a User Account Control (UAC) dialog box asking if they want to make changes to the machine, Page points out in his description. This means an attacker would have to bypass UAC somehow to successfully compromise a user with administrative privileges.

Microsoft wasn’t impressed, Page reported. The company told him:

A registry file was created with the title you suggested, but the error message was clear.

Threatpost received a response from Microsoft senior security director Jeff Jones, explaining:

The issue submitted does not meet the severity bar for servicing via a security update.

A successful registry change could enable an attacker to change a variety of settings including file associations, Control Panel settings, and windows components. The registry is also a popular destination for malware droppers, which can store code there enabling malware to persist by running automatically on startup.

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