Categories
Vulnerability

‘Hidden Property Abusing’ Allows Attacks on Node.js Applications

A team of researchers from Georgia Tech find a new attack technique that targets properties in Node.js and plan to publicly release a tool that has already identified 13 new vulnerabilities.

A team made up of security researchers from the Georgia Institute of Technology has found a way to exploit Node.js applications by manipulating the hidden properties used to track internal program states, the group plans to announce at the virtual Black Hat USA security conference next week.

The novel attack technique, dubbed Hidden Property Abusing, allows a remote attacker to inject new values into Node.js programs through passing objects that the framework, under the right circumstances, will treat as internal data. Using a tool to analyze a sample of 60 major Node.js components, the researchers found 13 vulnerabilities — ranging from SQL injection to the ability to bypass input validation.

The tool, dubbed Lynx, will be released at during the virtual Black Hat USA security conference, says Feng Xiao, the primary researcher and a doctoral student in the School of Computer Science at Georgia Tech.
Advertisement. Click for sound.

“Our attacks focuses on certain program states or properties defined by the developers, such as the user ID or other program features,” he says. “We found that this attack pattern is pretty common, but they can be complex to find, so we built the tool to help others.”

Hidden Property Abusing takes advantage of developers’ assumption that the internal program states are unreachable by an external attacker. The root cause of the problem is that “[a]fter the input data is converted to objects, Node.js treats them as legitimate objects like any other internal ones,” the researchers state in a yet-to-be-published paper on the topic.

The attack technique is similar to JavaScript Prototype Pollution, in which an attacker modifies a prototype object that is then merged, changing the base prototype of an object — changes that are then propagated to other JavaScript objects based on that prototype. In the case of Hidden Property Abusing, however, the prototype is not changed, but the properties inherited from a prototype can be overwritten, the researchers say.

“These parameters sometimes associate with some critical program states, but nobody knows their existence until an attacker exploits them, so that is why we call them hidden properties,” Feng says. The research team consists of six students and Wenke Lee, a professor of computer science at Georgia Tech.

Node.js is an extremely popular platform for running JavaScript code in a server environment for cloud-enabled applications, with more than 51% of developers claiming to use Node.js on a regular basis, according to the 2020 StackOverflow Developer Survey. Some 70% of developers have designated Node.js as their primary application platform, according to security firm Snyk’s open source technologies survey. Companies from Netflix to Trello to Microsoft’s LinkedIn use, or have used, Node.js as a framework for some of part of their services.

Making the impact worse, Node.js relies heavily on dependencies. A single component can import dozens of other components, and if one of those packages are vulnerable, the original component will be vulnerable as well. In a recent report, software security firm Veracode found that the average JavaScript program imported 377 libraries.

read more here

Categories
Security Vulnerability

Thousands of websites at risk from critical WordPress plugin vulnerability

A critical vulnerability in a third-party plugin installed on over 70,000 websites running WordPress could allow hackers to execute malicious code remotely.

The vulnerability, discovered by security researchers at Wordfence, hides in a vulnerable version of the wpDiscuz commenting plugin and enables hackers to upload arbitrary files to targeted websites, including executable PHP files.

wpDiscuz offers an alternative (and some would argue more stylish) way for people to leave feedback on blog posts than JetPack Comments, Disqus, and WordPress’s own built-in commenting system, and has received praise from some for its handling of comments in real-time through Ajax, comment rating system, and its support for storing comments on the site’s local servers rather than on a third-party service.

However, Wordfence’s researchers told wpDiscuz’s developers in June that it had found a flaw, which – due to a lack of security precautions – allowed unauthenticated users to upload to a comment any type of file (including PHP files).

The problem was found in version 7 of wpDiscuz which added a feature allowing users to upload images alongside their comments. However, Wordfence discovered that there was a failure to properly identify if uploaded files were really images or not, allowing the upload of potentially malicious code.

According to Wordfence, a successful attack could leave an attacker with control of every website on the server:

“If exploited, this vulnerability could allow an attacker to execute commands on your server and traverse your hosting account to further infect any sites hosted in the account with malicious code.” 

wpDiscuz’s developers initially told Wordfence that the flaw would be fixed in version 7.0.4 of the plugin, which was eventually released on July 20 2020.

Unfortunately, Wordfence found that that update did not sufficiently patch the security hole, and a new (properly working) version of wpDiscuz was released on July 23 2020.

Wordfence recommends that all administrators of self-hosted WordPress-powered websites that are running the wpDiscuz plugin update to the latest version as a matter of priority.

read more here