BayPay Forum BayPay Forum

Menu

  • Home
  • Events
    • Past Events
  • News
    • Payments News
    • Crypto News
    • Fintech News
    • Retail News
    • Fraud News
    • Regulation News
    • Security News
    • Markets News
  • Our Podcasts
    • Our Weekly Podcast
    • Our Daily Podcast
  • Join Us
  • Login
BayPay Forum BayPay Forum
  • Home
  • Events
    • Past Events
  • News
    • Payments News
    • Crypto News
    • Fintech News
    • Retail News
    • Fraud News
    • Regulation News
    • Security News
    • Markets News
  • Our Podcasts
    • Our Weekly Podcast
    • Our Daily Podcast
  • Join Us
  • Login

Android Vulnerable to Serious TCP Flaw in Linux

Details
Category: Security News
31 December 1969

Mobility

Advice for Android Users: Employ a VPN Until Manufacturers Patch Jeremy Kirk (jeremy_kirk) • August 22, 2016     Android Vulnerable to Serious TCP Flaw in Linux

About 1.4 billion Android devices are vulnerable to an attack that could allow a remote user to inject malicious code into an unencrypted traffic stream. Google is aware of the problem, and a related patch is being prepared.

See Also: Creating a User-Centric Authentication and Identity Platform for the Healthcare Industry

The flaw, CVE-2016-5696, exists in versions 4.7 and prior of the Linux kernel and was patched in July. But the issue also affects Android, which is based on Linux, and it's not the first time this has happened (see Zero-Day Flaw Found in Linux). In particular, Android versions 4.4 and newer have the new flaw, although it does not yet appear to have been exploited by in-the-wild attacks.

The flaw first appeared about four years ago, when a mechanism for managing Transmission Control Protocol - a fundamental protocol that regulates data packets between computers - was added to the Linux kernel. The feature, called "challenge ACK," was designed to more robustly secure TCP connections - one computer would prompt another with a number that only it would know, allowing a connection to resume. It was intended to prevent a kind of spoofing attack that could lead to an attacker injecting packets.

But an attack against the challenge ACK was described earlier this month in a research paper presented at the Usenix Security Symposium in Austin, Texas. The paper demonstrated how if two hosts are using TCP, it's possible - with enough time and the right kind of consistent connection - to guess the TCP sequence numbers and then inject malicious traffic into the stream.

"As long as you can figure out the source IP and destination IP, you can conduct this kind of attack anywhere in the world," says Andrew Blaich, a staff research engineer with Lookout Mobile Security, in a blog post analyzing the flaw.

No Malicious Links Required

Typically, attackers who want to spy on users need to execute a man-in-the-middle attack, Blaich says. In general, this requires an attacker to have access to the same network as the victim in order to meddle with traffic streams. The new attack, however, is more powerful - no network compromise is required, and the attack also doesn't rely on tricking a victim into downloading malware or clicking on a malicious link.

But there is some good news: The attack doesn't work against encrypted traffic streams, so until Android gets patched - and various manufacturers and carriers apply and release the patch to users and subscribers - the flaw can be mitigated by using a VPN.

The flaw might have been mitigated if more websites used SSL/TLS, which encrypts connections. But many sites today are still not fully encrypted. Moreover, websites that have SSL enabled still deliver ads over unencrypted connections, and that traffic could be tampered with.

For those websites, an attacker using this vulnerability could inject malicious JavaScript into, for example, an advertisement and try to infect a person's computer with malware, Blaich says. But even for HTTPS connections, an attacker could use the flaw to force a connection to terminate - a kind of denial-of-service attack - or else infer what websites a person is visiting.

The attack's success depends on how long someone can observe a TCP connection. Long-lived TCP connections - such as when a person is streaming a video - offer a greater chance of success than short-term connections, Blaich says. "It's not as easy as sending a text message containing a link to video file," he says.

Flaw Could Undermine Tor Privacy

Attacks that exploit the TCP flaw are fairly fast and reliable, according to the researchers' paper. They found that it takes, on average, between 40 seconds to one minute to execute an attack, with a success rate ranging between 88 to 97 percent.

They also tested the attack against Tor, the anonymity network that routes encrypted traffic throughout relays around the world to provide greater privacy for web browsing. Their conclusion was that a denial-of-service attack could be conducted, which might force a user's traffic to rely on certain exit relay machines, according to the paper, thus undermining the anonymity offered by Tor.

Waiting for Patches

Many Android device manufacturers, as well as cellular carriers, are getting better at patching Android devices, but some are better than others (see Four Android Flaws Leave 900M Devices at Risk). A year ago, Google committed to patch its own Nexus devices every month for devices that it still supports. Manufacturers including Samsung and LG have also pledged to issue regular patches. Their moves have come after criticism that Android devices were patched too slowly or, in some cases, not at all.

One year after Google's announcement, however, mobile device manufacturers, such as Samsung, are keeping up, but the same cannot be said of every manufacturer or carrier that releases a customized version of Android, or the millions of devices that are no longer supported.

"There's obviously a large batch of phones that never get updated," Blaich says.

Original link

Analysis: SWIFT-Related Heists: Who's to Blame?

Details
Category: Security News
31 December 1969

Fraud , Payments Fraud

Experts Debate the Security Responsibilities of SWIFT, Member Banks Tracy Kitten (FraudBlogger) • August 22, 2016     Analysis: SWIFT-Related Heists: Who's to Blame?

A Reuters report claiming executives at SWIFT for years neglected the security of its bank-to-bank messaging system has stirred debate among security and anti-fraud experts (see Report: SWIFT Screwed Up).

See Also: Avoid 75% of all Data Breaches by Keeping Privileged Credentials Secure

In the wake of the $81 million SWIFT-related cyberheist waged against the central bank of Bangladesh, and several other similar incidents, many experts acknowledge that much more needs to be done to ensure that interbank transactions routed through SWIFT are properly authenticated, monitored and secured. But while some experts call for SWIFT to take a leadership role on security, others argue that banks, not SWIFT, should take the lead.

William Murray, an independent financial fraud consultant, argues that SWIFT, a bank-owned cooperative based in Brussels formally known as the Society for Worldwide Interbank Financial Telecommunication, is nothing more than a "messenger" whose obligation is to offer a service that moves money from one bank to the next. Thus, he contends, it's not SWIFT's responsibility to ensure that transactions routed on its network are authenticated; that's the originating bank's job.

The Bangladesh Bank heist and other SWIFT-related thefts are "a banking problem, not a messenger problem," he asserts. "Banks write both the policy and the bank-to-bank agreements. The service providers [like SWIFT] do what they are told. ... It is so convenient to blame the messenger. What we are really seeing is management, perhaps governance, failures in a small number of banks."

Nothing that SWIFT did "or failed to do" would have prevented the Bangladesh heist, Murray contends. "SWIFT might add additional security services, e.g., transaction filters, confirmations, etc. But these will be effective only to the extent that SWIFT's [bank] customers, which actually own the network, choose to use them."

But Steve Durbin, managing director of the Information Security Forum, argues that SWIFT could be doing more when it comes to security. He argues that while it may have been "reasonable" for SWIFT to assume that the banks using its network had appropriate controls in place, SWIFT should have vetted those controls before allowing new institutions to sign on. "The answer is increased collaboration, information sharing and heightened controls, with an emphasis on verifying that what should be in place actually is in place," he says.

New Requirements Needed?

Murray acknowledges that banks using the SWIFT network should change their contractural agreements to require recipient banks to verify transactions before those transactions are approved and transmitted.

And financial fraud expert Avivah Litan, an analyst at the consultancy Gartner, says it's time for SWIFT to do some self-assessment. "SWIFT doesn't need to shore up its own security - it needs to figure out what its role is," she says. "Is it going to still be a network for transmitting messages securely, even when those messages are fraudulent, or is it going to take responsibility for making sure those messages are not fraudulent and not tampered with?"

Litan argues, however, that SWIFT doesn't have the authority to enforce security measures. "That's the regulators' jobs, and one day the regulators may eventually wake up to the need for them to do just that," she says.

Analysis of SWIFT's Security

The Reuters report, based on interviews with more than a dozen senior-level SWIFT managers and board members, details how SWIFT apparently failed to proactively eliminate known vulnerabilities related to how its smaller banking customers use SWIFT messaging terminals. Furthermore, according to the report, in 17 years of annual reports and strategic plans, SWIFT never mentioned security once, except for in its 2015 annual report, which was issued after the Bangladesh Bank heist. In that 2015 report, SWIFT said it would be helping "our community to strengthen their own infrastructure," the report notes.

Between 1994 and 2016, the number of countries and territories covered by SWIFT jumped from 126 to 212, Reuters reports. Most of that increase came from the addition of smaller banking institutions to the SWIFT network in developing countries, where security practices and regulatory oversight are deemed to be far less stringent than they are in economically developed countries.

Former SWIFT board member Arthur Cousins told Reuters that SWIFT believed banking regulators were responsible for ensuring and auditing security procedures at smaller banks. In contrast, Leonard Schrank, who served as CEO of SWIFT from 1992-2007, argued that SWIFT should have done more to ensure transactions running across its network were legitimate.

"The board took their eye off the ball," Schrank told Reuters. "They were focusing on other things, and not about the fundamental, sacred role of SWIFT, which is the security and reliability of the system."

Could SWIFT Have Done More?

SWIFT is not legally or contractually obligated to ensure that transactions routed across its network are legitimate, several security experts tell Information Security Media Group. That's the responsibility of the banks that originate the transactions.

Nevertheless, some experts suggest SWIFT could have done more to ensure that banking institutions using its network were taking specific steps to properly protect and verify payments. Others argue, however, that SWIFT did not drop the ball by depending on its bank members to ensure the authenticity and security of payments routed through the SWIFT network.

Cybersecurity attorney Chris Pierson, general counsel and CISO at invoicing and payments provider Viewpost, contends SWIFT could do more to vet the security of the banks that sign on to use its network.

"The SWIFT network is only as strong as its weakest link," he says. "SWIFT has a responsibility to ensure the network is safe and communications trusted, and that proper authentication protocols are put in place. As the network expanded, this responsibility and the governance over security protocols may be an area that receives extra attention during the root-cause analysis. All threats change over time, and unless the controls are constantly improved, weak links will be exploited."

But Andrew Davies, a fraud-prevention expert at core banking services provider Fiserv, says the banks, not SWIFT, have to invest in more fraud monitoring.

"Financial institutions and corporations of every size can take steps to help protect themselves," Davies says. "Organizations originating transactions, in particular high-value international transactions, should deploy technology and advanced analytic models that are designed specifically to detect fraudulent activity and anomalies of this type."

It's time for banks to make the necessary investments to ensure the security of bank-to-bank transactions, Gartner's Litan says. "The easiest thing to do from a technology viewpoint is to implement analytics and anomaly detection at the recipient banks so they can see if they are receiving an anomalous transaction for any given payer. They have the most readily available access to the data to do this."

SWIFT's Actions

Since news of the Bangladesh heist broke in March, SWIFT has launched a new digital forensics and customer security intelligence team. It also has announced that it is strengthening communication with its member banks to help them better understand how the SWIFT Relationship Management Application can be used to filter messages. Banks can filter messages "to ensure that message traffic is only permitted with trusted parties," SWIFT says, and revoke communications with any organization in cases of suspected fraud.

Additionally, SWIFT has introduced other security features, including mandatory updates for two-factor authentication as well as stronger default-password management and enhanced integrity-checking features.

Those are all good steps, Litan says, because attacks against SWIFT transactions are likely to continue. "But eventually, SWIFT will have to enforce security measures at its member banks, i.e. on the originator side," she adds.

Original link

Making USB Great Again

Details
Category: Security News
31 December 1969

A report analyzing the development of a defense against attackers who exploit USB devices to hack into computers leads the latest edition of the ISMG Security Report.

In the report, you'll hear:

The ISMG Security Report appears on this and other ISMG websites on Tuesdays and Fridays. Be sure to check out our Aug. 16 and Aug. 19 reports, which respectively analyze the mysterious increase in traffic that forced the Australian government to shutter a census website and the confusion surrounding the data dump by the mysterious group Shadow Brokers, and possible links to the U.S. National Security Agency and Russian intelligence. The next ISMG Security Report will be Friday, Aug. 26.

Theme music for the ISMG Security Report is by Ithaca Audio under the Creative Commons license.

Original link

Providing Frictionless ID Management

Details
Category: Security News
31 December 1969

Passwords' days are numbered as businesses attempt to deliver a better user experience to their online customers, says CA's Paul Briault.

"A lot of organizations are looking at ... how to give their customers a better or frictionless experience, but they also see the importance of keeping their customer data secure, protecting their assets and their information," he says.

As a result, more organizations are trying to help their customers complete tasks on their websites via as few clicks - or barriers - as possible. "Valid transactions should go through very simply [thanks to] lots of analysis and analytics on the back end," he says. "But if there is a need to step up authentication, then actually consumers don't mind doing that," for example, if they're in a foreign country, or doing something unusual, he adds.

In this interview with Information Security Media Group at the Infosecurity Europe conference in London, Briault also discusses:

The rise of payment protection and risk analytics for online channels, for example, at Nationwide Building Society; The increased use of privileged identity management inside the enterprise; The growth of a data breach protection and breach prevention culture inside European organizations, thanks to the EU General Data Protection Regulation.

Briault is senior director for digital security at CA. He previously served as a sales manager for HP Enterprise Security Services, head of public sector for EMC's RSA Security, strategic business director for the public sector at BEA systems, and assistant director at the U.K. Cabinet Office, where he was responsible for setting policy for security technology and standards across the U.K. government.

Original link

Tackling the Rising Cost of Security

Details
Category: Security News
31 December 1969

For many organizations, security spending - as a percentage of IT budgets - has gotten out of hand, says Chris Richter of Level 3 Communications. "Security costs are creeping up, and in some cases they're rocketing up," he says.

"If you go back five or 10 years ago, what was considered to be a normal percentage of an overall IT budget for security was around 3 percent to 6 percent," Richter says. "But now, on average, IDC reports that security budgets are in excess of 21 percent of an IT budget, and in some cases they're 50 percent to 60 percent."

This situation isn't sustainable, Richter says, because security is increasingly cutting into IT budgets to the point where it diverts resources from revenue-generating projects.

Of course, organizations will look to new technologies to help blunt hackers' increasing sophistication. But there are multiple non-technology steps organizations must take. "It all starts with governance," he says, including generating risk profiles, identifying where the most valuable data gets stored, as well as focusing on education.

In this interview with Information Security Media Group (see audio player below photo) conducted at the Infosecurity Europe conference, Richter also discusses:

The importance of governance, including ongoing education; The cost upsides of cloud-based security products; The information sharing imperative; The role of enterprise security gateways.

Richter is senior vice president, managed security services at Level 3 Communications, where he's responsible for the company's global managed and professional security services business. With 30 years of experience in IT, Richter has held a number of leadership positions in managed security, IT consulting and sales with several technology product and services organizations. His most recent previous position was vice president, managed security services, at CenturyLink.

Original link

More Articles …

  1. Equation Group Hacking Tool Dump: 5 Lessons
  2. New York Times Reportedly Targeted by Russian Hackers
  3. Ashley Madison Slammed by Regulators
  4. Epic Games Forums Breached Again
  • 3482
  • 3483
  • 3484
  • 3485
  • 3486
  • 3487
  • 3488
  • 3489
  • 3490
  • 3491

Page 3487 of 3546