Cisco Takes Another Stab at Patching Recent WebEx Vulnerability

Cisco Systems has released a new patch for a remotely exploitable privilege escalation vulnerability after security researchers found that its previous fix was incomplete.

The company first patched the vulnerability, known as WebExec or CVE-2018-15442, Oct. 24. The flaw was located in WebExService, a service installed on Windows machines by the Webex client apps.

The initial bug, identified by researchers from Counter Hack, allowed unprivileged users to start the service and issue an update command with a malicious file. The service executed the supplied file with SYSTEM privileges, allowing a local attacker to take full control of the computer. Even worse, the vulnerability could be exploited remotely over the local network in Active Directory environments.

After Cisco released its patch in October, researchers from another company called SecureAuth found a different way to exploit the vulnerability that relies on a technique known as DLL hijacking.

“The vulnerability can be exploited by copying to a local attacker controlled folder, the ptUpdate.exe binary,” the researchers said in an advisory. “Also, a malicious dll must be placed in the same folder, named wbxtrace.dll. To gain privileges, the attacker must start the service with the command line: sc start webexservice install software-update 1 “attacker-controlled-path” (if the parameter 1 doesn’t work, then 2 should be used).”

Cisco updated its CVE-2018-15442 advisory to warn users that the original patch was insufficient and that it released new patches to close the newly identified attack vector. Users should update the Cisco Webex Meetings Desktop App to version 33.6.4 or later and the Cisco Webex Productivity Tools to version 33.0.6 and later.

NPM Package Backdoored to Steal Cryptocurrency Wallets

A popular JavaScript library used by 1,600 Node.js packages and downloaded almost 2 million times per week has been infected with malicious code designed to steal cryptocurrency wallets.

The attack was performed through a package called event-stream and happened after its creator transferred ownership to another user. The new maintainer then added a component to the package called flatmap-stream and put his malicious code inside.

The rogue code was highly obfuscated and deployed its AES-encrypted payload only under certain conditions. People who analyzed it found that it targeted libraries associated with a Bitcoin wallet called Copay and its goal was to steal the wallet files and send them to a remote server.

“He emailed me and said he wanted to maintain the module, so I gave it to him,” event-stream’s original author said in a discussion on GitHub. “I don’t get anything from maintaining this module, and I don’t even use it anymore, and haven’t for years.”

This is not the first time when hackers have tricked the authors of popular software components to give them up. There are documented cases where attackers set up companies and paid significant amounts of money to buy WordPress plug-ins or Google Chrome extensions from their original developers. After acquiring them, they modified their code to inject spam into websites or users’ browsing sessions.

The problem for end users is that changes in software ownership are rarely announced publicly and are difficult to detect, especially in complex development ecosystems made up of thousands of third-party packages. As this incident shows, a package that has been trusted for years can fall in the hands of malicious users and can become a security risk overnight.

“These supply-chain attacks are only going to become more and more prevalent with time,” Thomas Hunter II, a researcher with security firm Intrinsic, said in a blog post about the event-stream attack. “Targeted attacks, like how this package specifically targets the Copay application, will also become more prevalent.”

Lucian Constantin

Lucian Constantin

Lucian has been covering computer security and the hacker culture for almost a decade, his work appearing in many technology publications including PCWorld, Computerworld, Network World, CIO, CSO, Forbes and The Inquirer. He has a bachelor's degree in political science, but has been passionate about computers and cybersecurity from an early age. Before he chose a career in journalism, Lucian worked as a system and network administrator. He enjoys attending security conferences and delving into interesting research papers. You can reach him at [email protected] or @lconstantin on Twitter. For encrypted email, his PGP key's fingerprint is: 7A66 4901 5CDA 844E 8C6D 04D5 2BB4 6332 FC52 6D42

lucian-constantin has 298 posts and counting.See all posts by lucian-constantin

Cloud Workload Resilience PulseMeter

Step 1 of 8

How do you define cloud resiliency for cloud workloads? (Select 3)(Required)