STE WILLIAMS

PewDiePie-spammers and whale-flingers exploit hole in Atlas game

The newly launched Atlas game has pirates, a fountain of youth, ramshackle sloops, naval battles, submarines, and guillotines.

What Grapeshot Games’s MMO (Massively Multiplayer Online) game is not supposed to have: a flood of whales, spawning in water, on land and sometimes in mid-air.

Image from StreamerHouse playing ATLAS, on Twitch

That, however, is what happened after multiple players found and exploited a vulnerability in the Atlas game itself. On Sunday, an assistant community manager wrote on the Atlas community forum that the game maker had to do “emergency maintenance” at 09:00 am UTC, rolling back the game and wiping out players’ gains in the five and a half hours since the exploit enabled the infliction of whales.

Multiple accounts were eventually banned. But before the game admins had a chance to close the hole, the whale-flingers got bored and they, and/or others, started flooding the servers with dragons… after which some players exploited the vulnerability by spamming players to exhort them to subscribe to PewDiePie… for hours.

Did Atlas get PewDiePie-rolled?

This is par for the course for fans of Swedish video game commentary celebrity Felix “PewDiePie” Kjellberg. Last month, somebody intent on keeping PewDiePie in his position as top YouTube channel hacked printers worldwide to print pro-PewDiePie propaganda.

That propaganda war also included antics such as defacing the Wall Street Journal’s website and hijacking thousands of internet-exposed Chromecasts, smart TVs, and Google Home devices earlier this month. The gadgets were hacked to play yet another PewDiePie channel advertisement.

When it comes to the Atlas exploits, ZDNet’s Catalin Cimpanu suggests that the PewDiePie spam “seems more of a secondary effect” rather than being the main directive.

In fact, PewDiePie subscription spam seems to have become the “de facto prank message and a rite of passage for any wannabe hacker,” Cimpanu said.

Move over, Rickrolling and references to security journalist Brian Krebs. Modern-day pranksters have PewDiePie to drop into website defacements and malware code!

Atlas: Injury added to insult

The exploit of the technical vulnerability in Atlas on Sunday was actually the second time in days that Atlas was compromised, and it’s the second time that Grapeshot Games did a five-and-a-half-hour game rollback.

Early access to Atlas was launched on Steam before Christmas. Last week, on Thursday, hackers allegedly compromised an admin’s Steam account and used it to spawn planes, tanks, and whales in Atlas.

Grapeshot Games, from a post on the community forum on Thursday:

Earlier today, an admin’s steam account was compromised and used to cause some devastation on our Official NA PvP Network. To be clear this was not caused by a hack, third party program, or exploit. We have taken the appropriate steps to ensure this does not happen again. We’ll be rolling back our Official NA PvP Network by approximately 5 and a half hours to a network world save at approximately 11 AM UTC (3 AM PST/6 AM EST). We apologize for the inconvenience and we thank for your patience and understanding during this time.

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

100 million online bets exposed by leaky database

Yet another organisation has been spotted copying important data to Elasticsearch cloud storage without remembering to secure it.

Last week, it was US company VOIPo that accidentally exposed call logs, SMS data, and company credentials in Elasticsearch where it was spotted by researcher Justin Paine.

This week, Paine has returned to tell ZDNet of a second cache of Elasticsearch data he found only days ago that appears to have been connected to online betting sites.

Sensitive data such as:

Real names, home addresses, phone numbers, email addresses, birth dates, site usernames, account balances, IP addresses, browser and OS details, last login information, and a list of played games.

In addition, Paine found 108 million records connected to online bets, deposits, wins and withdrawals, complete with partially redacted payment card data.

According to ZDNet, the betting domains included kahunacasino.com, azur-casino.com, easybet.com, and viproomcasino.net, connected to companies registered in Cyprus and the Caribbean.

It’s not clear how far back the data might go, but anyone who placed bets through these sites would be at risk of having their win and loss information made public, opening users up to potential extortion.

As with the VOIPo data leak, there’s no evidence that the information has fallen into the wrong hands, although isn’t terribly reassuring to online gamblers whose data might be part of this cache.

In a positive development, Paine said the data has been taken down, although whether this was by the affected company (or companies) or hosting provider OVH is unclear.

The elastic snaps

The involvement of Elasticsearch in these incidents is a consequence of the open source search tool’s huge popularity. If something becomes popular enough, eventually someone will misuse or misconfigure it.

What should worry us is that this seems to have been happening a lot recently.

Recent incidents include the exposure of 57 million US citizens in November, as well as similar incidents involving Sky Brasil and last June’s Exactis data broker leak involving a reported 340 million records.

Together, these leaks probably join dots that could connect cybercriminals to hundreds of millions of people.

All of these exposed databases were found by independent researchers using tools anyone, including cybercriminals, can access.

That is the important point – the problem of exposed Elasticsearch data is out of the bag and people with different motivations are now looking for it.

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

Ep. 016 – Email fraud, Android apps, Collection #1 and the 10 year challenge [PODCAST]

In this episode, we look at high-value email crime, talk you through Google’s latest attempt to clean up the Play Store, tell you how to buy a billion email addresses for just $45, and ponder the OMG conspiracy theories that say the “10 year challenge” is a dangerous trap.

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

This week’s links:

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...

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

Black hats are great for language diversity, says Eugene Kaspersky

FIC2019 According to Eugene Kaspersky, founder of the eponymous antivirus company, black-hat hackers are increasingly likely to speak Portuguese and Spanish as well as the traditional English, Russian and Chinese.

Kaspersky was speaking at France’s Forum International de la Cybersécurité (FIC 2019) this morning. He did, however, cheerfully concede that a large amount of hacking is still carried out by his countrymen despite any observed shifts in language popularity.

“For highly sophisticated criminal attacks, all of them speak Russian. Thanks to quality Russian technical education! Russian software engineers are the best; Russian criminals are the worst!”

Eugene also annoyed a Frenchman, General Olivier Bonnet de Paillerets of the French Army’s Cyber Command. The general had been speaking about French efforts to convince local youth tempted by the glamorous hacker lifestyle to join the forces of good instead.

“I have a couple of examples of young people who had developed this talent at one point [and] said ‘That is it, it’s finished, it’s going too far, I want to come back to the normal world’,” said General de Paillerets. “The normal world is of this collective security challenge.”

Amused, Kaspersky retorted in his Russian drawl: “The hackers are not around here! They’re 1,000km away from here. They’re in Latin America, Russian-speaking countries, China, Turkey. They’re living far from France. The French-speaking malware, [there’s] not much actually… First of all there are immigration issues, then they have to study French.”

Florence Parly, France's Defence Secretary

En garde! ‘Cyber-war has begun’ – and France will hack first, its defence sec declares

READ MORE

Already unamused after having been caricatured as a gun-toting killer by the in-house cartoonist*, General de Paillerets frowned but diplomatically held his tongue. Yesterday French defence secretary Florence Parly had spoken at length about the need to grow more French cybersecurity talent.

Kaspersky went on to talk more about the languages his company tends to see in malware used for spying.

“Espionage! Native English, Atlantic zone,” he said in his characteristic broken English. “Native Russian, Eastern Europe zone. But Russian speakers, they’re not active during the Russian winter holidays,” he grinned, allowing himself a theatrical shrug as the audience tittered.

“This is not an attribution issue,” continued Kaspersky once the laughter had died away. “It’s not 100 per cent proof of who’s behind these attacks. And there’s many other languages. Spanish, Portuguese, French, German, Arabic. Many languages are used by the espionage tools.” ®

Bootnote

During the talk, in a large auditorium, the 15-foot projector screen was occasionally filled with drawings made on the fly by a local cartoonist hired by the organisers to spice things up a bit.

Article source: http://go.theregister.com/feed/www.theregister.co.uk/2019/01/23/eugene_kaspersky_hacker_language_diversity/

Discover New Tools for Network Testing & Defense at Black Hat Asia

Find yourself some of the latest and most exciting cybersecurity tools at the Arsenal, where you can meet and chat with their creators.

Every pass sold to Black Hat Asia in Singapore this March entitles the bearer to (among other things) access the Arsenal, and there’s no better place to watch experts demonstrate new and exciting open-source cybersecurity tools.

For example, “Mr.SIP: SIP-Based Audit and Attack Tool” offers you a practical look at Mr.SIP, a tool developed to audit and simulate SIP (Session Initiation Protocol) attacks. In the current state, it comprises four sub-modules named SIP-NES (a network scanner), SIP-ENUM (enumerator), SIP-DAS (DoS attack simulator), and SIP-ASP (attack scenario player).

Originally designed for use in academic work developing novel SIP-based DDoS attacks, it’s since been developed into a fully functional SIP-based penetration testing tool that you can use in your own work!

If you’re looking to add a little more automated help to your network testing arsenal, check out the Arsenal demo of “OWASP Nettacker: Automated Penetration Testing Framework.” Designed to automate information gathering, vulnerability scanning, and penetration testing, this tool utilizes TCP SYN, ACK, ICMP and many other protocols in order to detect and bypass Firewall/IDS/IPS devices.

There’s plenty of network defense tools in this year’s Arsenal as well, including “VoIP Wireshark Attack-Defense Toolkit”, a collection of Wireshark plugins which enables you to analyze VoIP traffic.

Notably, this toolkit can provide a summary of VoIP traffic, automatically decrypt VoIP calls wherever possible, export the call audio to popular formats, detect attacks/misconfigurations, and highlight the DTMF/SMS interactions. This eliminates the need for a separate software/framework to analyze VoIP traffic. The plugins are written in Lua and are easy to add to Wireshark. And, the toolkit, just like Wireshark, is platform independent!

For a bit of personal security, don’t miss the appropriately titled “NFC Scrambler” Arsenal demo. A simple tool, this Android app aims to emulate an RFID card to try and prevent NFC skimming. Identity theft is a huge problem that’s not going away, and not everyone can afford (or wants to carry) an RFID blocker card or wallet. If you don’t, this simple app might make a great addition to your toolkit.

Black Hat Asia returns to the Marina Bay Sands in Singapore March 26-29, 2019. Early registration pricing for Briefings Trainings ends Friday, January 18, so register before then to get the best price!

For more information on what’s happening at the event and how to register, check out the Black Hat website.

Article source: https://www.darkreading.com/black-hat/discover-new-tools-for-network-testing-and-defense-at-black-hat-asia/d/d-id/1333698?_mc=rss_x_drr_edt_aud_dr_x_x-rss-simple

Enterprise Malware Detections Up 79% as Attackers Refocus

A new report on the state of malware shows a spike in B2B malware, with former banking Trojans Emotet and TrickBot topping the list.

Enterprise threats ramped up toward the end of 2018 as cybercriminals shifted their strategies to hit business victims with unpatched, insecure networks – and found plenty of targets.

That’s one of the key findings from Malwarebytes Labs’ “State of Malware Report 2019,” which analyzes threats from January through November 2018 and compares them with the same period from 2017. After cryptomining exploded near the end of 2017, the next year began with attackers broadening their strategies to hit Mac and Android devices and use browser-based threats.

But cryptomining began to slow down by the second quarter of 2018, researchers report, and a new set of attacks took its place. Former banking Trojans Emotet and TrickBot evolved into droppers with several modules for spam production, network propagation, and data skimming. New malware variants targeted the enterprise, hunting sensitive data they could sell for profit.

Criminals have historically gone after consumers, says Malwarebytes CEO Marcin Kleczynski, but the past year has shown they’ve found value in targeting the enterprise. One corporate login can grant them access to troves of far more valuable information, and it’s not hard to get.

A Pivot Toward the Enterprise
Most attackers don’t plan to hit specific companies, Kleczynski points out. They start by casting a wide net, conducting online research to see who’s most vulnerable, then pursuing them. Business malware detections rose 79% over the last year, report Malwarebytes researchers, who link the rise to an increase in backdoors, miners, spyware, and information stealers.

While 2017 can be considered the year of global outbreaks – WannaCry and NotPetya made sure of it – 2018 was the “year of the mega breach.” Attackers hit major corporations, including Facebook, Marriott, Exactis, MyHeritage, and Quora, affecting hundreds of millions of customers and driving the numbers of compromised records up 133% compared with 2017.

Companies may worry about becoming the next Marriott, Kleczynski says, but most of the attacks Malwarebytes sees aren’t the big ones. Many businesses are affected with popular strains of malware like Emotet, which he explains is “going around like the flu.” Trojan detections were up 132%, a rise led by the prevalence of the Emotet, which, like other info-stealing malware, uses exploits to move across corporate networks and brute-forces credentials.

Backdoors increased 173% among enterprise victims, spyware was up 142%, and RiskwareTool rose by 126%, researchers report. They attribute the rise in spyware to similar variants and families of Emotet and TrickBot being identified as spyware in the wild – a sign attackers have focused on information stealing and creating footholds in corporate networks, they explain.

Common attack vectors like spam “work so well” on business victims, Kleczynski says. “At the end of the day, it’s still very common to spread an attack like Emotet,” he adds, just by getting more people to click on a malicious email. It doesn’t help that company websites and platforms like LinkedIn expose useful information (full names, job titles) that help make attacks targeted.

Emotet and Trickbot topped the threats of 2018 and found success in malspam, a technique that disguises the threats as a legitimate email. What made their attacks successful was how they spread.For Emotet, this meant infected attachments and embedded URLs, with social engineering tactics designed to make targets believe messages come from trusted sources.

While businesses saw more malware detections, consumers saw fewer. In 2017, there were 775,327,346 consumer detections, Malwarebytes reports. The most recent year brought about 25 million fewer instances and a 3% decline – “a healthy decrease,” percentages aside.

“Always, at the end of the day, [it’s] around money and the value of some of these assets,” Kleczynski says of cyberattackers eyeing enterprise data. “I would claim that credit card and Social Security and passport numbers aren’t as valuable as they were 10 years ago.”

Ransomware: It’s Complicated
Toward the end of 2017, security experts predicted the cryptomining crazy would continue. Indeed, 2018 brought the decline of ransomware and rise of cryptominers, following a spike in Bitcoin value at the end of 2017. Criminals seeking financial gain jumped on the trend, hitting Mac, Windows, and Android devices with software- and browser-based cryptomining attacks.

However, cryptomining only increased 7% last year as the second half of 2018 brought its decline. It’s still one of the major malware trends of 2018, but the drop in cryptocurrency value has slowed it down. “Bitcoin losing more than 80% of its value over the last year has led cybercriminals to pivot,” Kleczynski explains.

As the trend lagged, cybercriminals shifted their ransomware techniques from malvertising exploits and ransomware payloads to manual, targeted ransomware attacks. While it’s not the wide-ranging threat it was in 2017, it’s still a threat to keep in mind. Trends show an increase in focused, sophisticated attacks geared toward the enterprise and lack of interest in consumers.

Businesses, unlike individuals, have the potential funds to pay a ransom and several pressing reasons to get back up and running after a ransomware attack. Delays caused by ransomware can be incredibly expensive, researchers say, especially when the victim has a wealth of infected endpoints and no backup plan in place. Incident response is costlier than paying up.

SamSam, which hit the city of Atlanta and medical organizations across the US in 2018, was revamped to charge victims a more moderate price compared with recovery methods that businesses would otherwise have to pay. The change led to operators making more overall. GandCrab, the top ransomware variants of Q2 2018, adopted the Magnitude exploit kit, which plagued network admins and home users with its unusual malware-loading method.

High Risk Meets Few Resources
Kleczynski says many companies have stepped up their security game despite struggling with a lack of resources. Despite attacks over the past decade, he says, the pressure on security teams to request sufficient resources from their organizations is still relevant. In the education and state/local government sectors, for example, budgets are a significant concern.

“It’s interesting to see companies doing what they can with as little as they have,” he says.

Security-focused conversations are also making their way to the board, where execs are concerned about being hit with the next major breach. “I think the weight of the topic is significant,” he adds. It’s especially difficult for companies with small security teams, which struggle to cover every aspect of security with few people. Open source software, free tools, and outsourcing have helped drive security efforts, Kleczynski adds.

Read the report here.

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/attacks-breaches/enterprise-malware-detections-up-79--as-attackers-refocus/d/d-id/1333705?_mc=rss_x_drr_edt_aud_dr_x_x-rss-simple

Build the wall… around your DNS settings, US govt IT staff urged by Homeland Security amid domain hijackings

America’s Homeland Security has urged US government departments and federal agencies to shore up their DNS control panels after hackers successfully stormed the barricades.

In an emergency directive issued within the past few hours, IT staff still manning their posts during the partial US government shutdown are advised to lock down their domain name settings for their .GOVs and other official web addresses.

Uncle Sam’s techies have been told to use fresh, strong passwords for DNS settings, enable multi-factor authentication to thwart unauthorized changes to their domains, make sure web addresses resolve to the correct IP addresses, and monitor logs for signs of shenanigans.

The instructions were issued after Homeland Security’s Cybersecurity and Infrastructure Security Agency (CISA) became aware of miscreants compromising the DNS infrastructure for “multiple executive branch agencies.” The total number is at least six, according to Washington DC-based CyberScoop.

A security guard asleep

*taps on glass* Hellooo, IRS? Anyone in? Anyone guarding taxpayers’ data from crooks? Hellooo?

READ MORE

Earlier this month, infosec biz FireEye reported a very similar domain hijacking campaign, quite possibly orchestrated by Iran, that redirected Middle Eastern government emails through Iranian IP addresses.

Once hackers get hold of DNS account passwords, or bruteforce weak ones, they can change name servers, domain and sub-domain records, and MX settings so that netizens connecting to a government website or server are instead redirected to malicious systems that masquerade as the legit site. This allows stuff like emails, usernames, and passwords to be potentially harvested. HTTPS encryption really won’t help, the advisory added, because attackers can obtain valid certificates for the hijacked domain names.

This is why America’s chiefs want agencies – and presumably those following along at home – to use strong passwords and multi-factor authentication for their domain management accounts to prevent domain hijackings. CISA added these DNS joyrides are “a risk that persists beyond the period of traffic redirection.”

Here’s the key lines from the directive, and it won’t hurt to implement these yourself:

* Within 10 business days, for all .gov or other agency-managed domains, audit public DNS records on all authoritative and secondary DNS servers to verify they resolve to the intended location. If any do not, report them to CISA.

* Within 10 business days, update the passwords for all accounts on systems that can make changes to your agency’s DNS records.

* Within 10 business days, implement multi-factor authentication (MFA) for all accounts on systems that can make changes to your agency’s DNS records. If MFA cannot be enabled, provide CISA with the names of systems, why it cannot be enabled within the required timeline, and when it could be enabled.

Some agencies may struggle somewhat to comply: as you can see, the emergency directive requires these actions to be undertaken within 10 business days, something that may be difficult amid President Trump and Senate majority leader Mitch McConnell (R-KY)’s ongoing partial government shutdown. Last week, Netcraft noted the shutdown had prevented renewal of more than 130 US government-owned-TLS certificates.

CISA also said that within 10 business days, it will “begin regular delivery of newly added certificates to Certificate Transparency (CT) logs for agency domains, via the Cyber Hygiene service.” Once it starts distributing those logs, agencies are directed to monitor them to spot any certificates they didn’t issue.

Given the lack of IT staff on hand to do the job, the directive’s requirements are unlikely to be followed through by all departments. Attackers will, no doubt, be banking on Americans being distracted by arguments over a physical wall, allowing the miscreants to slip through the firewalls instead. ®

Article source: http://go.theregister.com/feed/www.theregister.co.uk/2019/01/23/dhs_issues_emergency_directive/

White-listing Azure cloud connections to grease your Office 365 wheels? About that…

Microsoft has been accused of ignoring an IT security risk that could be exploited to create legit-looking malware-laden webpages that sport seemingly trusted Azure and Office 365 domain names. Alternatively, the domains potentially could be used to stealthily leak stolen data from networks.

It’s not a world-shattering threat by a long shot, though if you’re a sysadmin – and we know a good bunch of you are – it’s quite possibly something to bear in mind when configuring your network security, proxy boxes, and gateways.

Software developer Patrick Dwyer reckons anyone with an Azure subscription can, or at least could at time of writing, register a *.azureedge.net or *.blob.core.windows.net address, such as the convincing tokyo-1-mail-server.azureedge.net. These can be pointed at arbitrary content. For example, Dwyer created patros-issue-233.azureedge.net/index.html and patrosissue233.blob.core.windows.net/index/index.html to prove his point…

And here’s where it gets a bit unfortunate: Microsoft encourages organizations to white-list and perhaps even prioritize Office 365 connections by identifying and green-lighting traffic to and from these cloud-based endpoints, and these endpoints include gems like mlccdnprod.azureedge.net and *.blob.core.windows.net. A full list for worldwide customers is here, for example.

Thus it is possible for someone to request and obtain their own custom blahblahblah.blob.core.windows.net domain, host bad things on it, such as malware and spear-phishing pages, and watch a corporate firewall allow a victim’s PC connect to it, via an email or other link, because *.blob.core.windows.net has been white-listed for Office 365. If a netadmin has white-listed all of azureedge.net, then that’s another way in. This is all according to Dwyer.

We appreciate that you may have defenses in place to catch exploit kits, malware, phishing pages, and other nasties from being fetched and opened on workstations, of course, besides blocking malicious Azure sub-domains.

Leaks

Additionally, we’re told the trusted domains could potentially be used by network intruders and rogue employees to covertly move stolen data out of an organization: there’s nothing suspicious in information trickling out to a legit-looking azureedge.net machine, your firewall security may think.

“To optimize Office 365 traffic, in our case to fix issues with Skype, that list of endpoints is used,” Dwyer told The Register on Tuesday in discussing the find. “And by optimize you bypass your normal proxy and perimeter security devices. So if you decide to trust that list, anyone can create an Azure CDN or Azure Blob Storage account and use it to download whatever malware, exploit, tools they want onto your network.

“Perhaps the more potentially problematic scenario is that post exploit, an attacker could use an Azure Blob Storage account to exfiltrate all your corporate data and you might not even know, or even have a record of it, because it is going straight out bypassing your normal network perimeter security.”

Redmond is remaining mostly tight-lipped on the matter. Dwyer said that, after reporting the issue back in November, Microsoft sent him a “thanks for sharing” note, a promise to look into it, and a followup claim that it isn’t a problem. The issue was eventually closed as a WONTFIX at the end of last week.

“Because Microsoft owns the azureedge.net DNS domain and the DNS servers resolving names in that domain, only Microsoft can create new names and host new CDN profiles in that domain,” Microsoftie Joe Davis said.

Dwyer hit back, though: “Anyone with an Azure subscription can request one via the portal to be created by Microsoft automatically. I have concerns that organisations will give *.azureedge.net more trust than it deserves when configuring network perimeter devices like firewalls and proxy servers.

“You’re even encouraging network perimeter device vendors to treat my content, and the content of however many Azure CDN customers there are, as Office 365 traffic.”

A Microsoft spokesperson was unable to comment before publication. If you have any thoughts, hints and tips, or similar warnings of other security snafus, please do share in the comments… ®

Article source: http://go.theregister.com/feed/www.theregister.co.uk/2019/01/23/office_365_network_hole/

Heads up: Debian’s package manager is APT for root-level malware injection… Fix out now to thwart MITM hijacks

The Debian Project has patched a security flaw in its software manager Apt that can be exploited by network snoops to execute commands as root on victims’ boxes as they update or install packages.

The Linux distro’s curators have pushed out an fix to address CVE-2019-3462, a vulnerability uncovered and reported by researcher Max Justicz.

The flaw is related to the way Apt and apt-get handle HTTP redirects when downloading packages. Apt fetches packages over plain-old HTTP, rather than a more secure HTTPS connection, and uses cryptographic signatures to check whether the downloaded contents are legit and haven’t been tampered with.

This unfortunately means a man-in-the-middle (MITM) miscreant who was able to intercept and tamper with a victim’s network connection could potentially inject a redirect into the HTTP headers to change the URL used to fetch the package.

And the hacker would be able to control the hashes used by Apt to check the downloaded package, passing the package manager legit values to masquerade the fetched malware as sanctioned software.

All in all, users can be fed malware that’s run as root during installation, allowing it to commandeer the machine.

Penguin with video photo via Shutterstock

The D in SystemD stands for Dammmit… Security holes found in much-adored Linux toolkit

READ MORE

“I found a vulnerability in apt that allows a network man-in-the-middle (or a malicious package mirror) to execute arbitrary code as root on a machine installing any package,” explained Justicz.

Debian developer Yves-Alexis Perez noted: “This vulnerability could be used by an attacker located as a man-in-the-middle between APT and a mirror to inject malicious content in the HTTP connection. This content could then be recognized as a valid package by APT and used later for code execution with root privileges on the target machine.”

Debian has released an update for Apt to address the vulnerability.

As an added wrinkle, Apt is updated by Apt itself. And seeing as the update mechanism is insecure, folks need to take extra steps to install the security fix securely. Admins will want to first disable redirects (see below) and then go through the usual apt update and upgrade steps.

$ sudo apt update -o Acquire::http::AllowRedirect=false
$ sudo apt upgrade -o Acquire::http::AllowRedirect=false

Justicz noted that the use of HTTP for updates in itself isn’t a bad practice, as long as there are cryptographic checks at the end. HTTPS at least wraps the connection in cryptography that, among other things, can be used to detect whether or not someone is twiddling with your data while it is in transit.

“Supporting HTTP is fine,” Justicz said. “I just think it’s worth making HTTPS repositories the default – the safer default – and allowing users to downgrade their security at a later time if they choose to do so.” ®

Article source: http://go.theregister.com/feed/www.theregister.co.uk/2019/01/22/debian_package_manager_flaws/

Wow, fancy that. Web ad giant Google to block ad-blockers in Chrome. For safety, apparently

Google engineers have proposed changes to the open-source Chromium browser that will break content-blocking extensions, including various ad blockers.

Adblock Plus will most likely not be affected, though similar third-party plugins will, for reasons we will explain. The drafted changes will also limit the capabilities available to extension developers, ostensibly for the sake of speed and safety. Chromium forms the central core of Google Chrome, and, soon, Microsoft Edge.

In a note posted Tuesday to the Chromium bug tracker, Raymond Hill, the developer behind uBlock Origin and uMatrix, said the changes contemplated by the Manifest v3 proposal will ruin his ad and content blocking extensions, and take control of content away from users.

Content blockers may be used to block ads, but they have broader applications. They’re predicated on the notion that users, rather than anyone else, should be able to control how their browser presents and interacts with remote resources.

Manifest v3 refers to the specification for browser extension manifest files, which enumerate the resources and capabilities available to browser extensions. Google’s stated rationale for making the proposed changes is to improve security, privacy and performance, and supposedly to enhance user control.

“Users should have increased control over their extensions,” the design document says. “A user should be able to determine what information is available to an extension, and be able to control that privilege.”

But one way Google would like to achieve these goals involves replacing the webRequest API with a new one, declarativeNetRequest.

The webRequest API allows extensions to intercept network requests, so they can be blocked, modified, or redirected. This can cause delays in web page loading because Chrome has to wait for the extension. In the future, webRequest will only be able to read network requests, not modify them.

The declarativeNetRequest allows Chrome (rather than the extension itself) to decide how to handle network requests, thereby removing a possible source of bottlenecks and a potentially useful mechanism for changing browser behavior.

“The declarativeNetRequest API provides better privacy to users because extensions can’t actually read the network requests made on the user’s behalf,” Google’s API documentation explains.

Whose privacy exactly?

But “better privacy” here means privacy as defined by Google rather than privacy defined by a third-party extension developer. That’s fine in scenarios where Google is more trustworthy than a third-party developer; but if Google and its ecosystem of publishers and advertisers are the problem, then users may prefer allowing a third-party to filter network requests, even to the extent such intervention interferes with webpage functionality.

“If this (quite limited) declarativeNetRequest API ends up being the only way content blockers can accomplish their duty, this essentially means that two content blockers I have maintained for years, uBlock Origin (‘uBO’) and uMatrix, can no longer exist,” said Hill.

The proposed changes will diminish the effectiveness of content blocking and ad blocking extensions, though they won’t entirely eliminate all ad blocking. The basic filtering mechanism supported by Adblock Plus should still be available. But uBlock Origin and uMatrix offer far more extensive controls, without trying to placate publishers through ad whitelisting.

This is a key point to note: Google and other internet advertising networks apparently pay Adblock Plus to whitelist their online adverts, hence the special love for this particular plugin – and the middle finger to everyone else. Meanwhile, Google has bunged its own basic ad blocking into its browser.

Image by ART production http://www.shutterstock.com/gallery-3278237p1.html

It’s official. Microsoft pushes Google over the Edge, shifts browser to Chromium engine

READ MORE

Several other developers commenting on the proposed change expressed dismay, with some speculating that Google is using privacy as a pretext for putting the interests of its ad business over those of browser users.

Hill, who said he’s waiting for a response from the Google software engineer overseeing this issue, said in an email to The Register: “I understand the point of a declarativeNetRequest API, and I am not against such API. However I don’t understand why the blocking ability of the webRequest API – which has existed for over seven years – would be removed (as the design document proposes). I don’t see what is to be gained from doing this.”

Hill observes that several other capabilities will no longer be available under the new API, including blocking media elements larger than a specified size, disable JavaScript execution by injecting Content-Security-Policy directives, and removing the outgoing Cookie headers.

And he argues that if these changes get implemented, Chromium will no longer serve users.

“Extensions act on behalf of users, they add capabilities to a ‘user agent’, and deprecating the blocking ability of the webRequest API will essentially decrease the level of user agency in Chromium, to the benefit of web sites which obviously would be happy to have the last word in what resources their pages can fetch/execute/render,” he said.

“With such a limited declarativeNetRequest API and the deprecation of blocking ability of the webRequest API, I am skeptical ‘user agent’ will still be a proper category to classify Chromium.”

Google, however, may yet be willing to address developers’ concerns. “These changes are in the design process, as mentioned in the document and the Chromium bug,” a Google spokesperson told The Register via email. “Things are subject to change and we will share updates as available.” ®

Article source: http://go.theregister.com/feed/www.theregister.co.uk/2019/01/22/google_chrome_browser_ad_content_block_change/