AuthorTopic: Critical WordPress REST API Bug: Prevent Your Blog From Being Hacked!  (Read 428 times)

Offline Palloy2

  • Administrator
  • Sous Chef
  • *****
  • Posts: 6097
    • View Profile
    • Palloy's Blog
Since WordPress v4.7.0, critical updates get applied automatically, so we are on v4.7.2 and safe.  On the downside, we are even more dependent on WP working out the patches and applying them automatically.  You can't win.

http://thehackernews.com/2017/02/wordpress-exploit-patch.html
Critical WordPress REST API Bug: Prevent Your Blog From Being Hacked!
February 01, 2017
Swati Khandelwal

Last week, WordPress patched three security flaws, but just yesterday the company disclosed about a nasty then-secret zero-day vulnerability that let remote unauthorized hackers modify the content of any post or page within a WordPress site.

The nasty bug resides in Wordpress REST API that would lead to the creation of two new vulnerabilities: Remote privilege escalation and Content injection bugs.

Wordpress is the world's most popular content management system (CMS) used on millions of websites. The CMS recently added and enabled REST API by default on WordPress 4.7.0.

Flaw lets Unauthorised Hacker Redirect Visitors to Malicious Exploits

The vulnerability is easy to exploit and affects versions 4.7 and 4.7.1 of the Wordpress content management system (CMS), allowing an unauthenticated attacker to modify all pages on unpatched sites and redirect visitors to malicious exploits and a large number of attacks.

The vulnerability was discovered and reported by Marc-Alexandre Montpas from Sucuri to the WordPress security team who handled the matter very well by releasing a patch, but not disclosing details about the flaw in an effort to keep hackers away from exploiting the bug before millions of websites implement the patch.

    "This privilege escalation vulnerability affects the WordPress REST API," Montpas writes in a blog post. "One of these REST endpoints allows access (via the API) to view, edit, delete and create posts. Within this particular endpoint, a subtle bug allows visitors to edit any post on the site."


Why WordPress Delayed the Vulnerability Disclosure

The issue was discovered on January 22nd, patched on January 26th and the fix was made available in release 4.7.2 to websites using the popular CMS.

Sucuri security providers and hosts worked closely with Wordpress security team for over a week to install the patch, ensuring that the issue was dealt with in short order before it became public.

The company also tipped off security companies including SiteLock, Cloudflare, and Incapsula over 9 days between disclosure and patch.

Here's what the Wordpress core contributor Aaron Campbell says about the delay in the vulnerability disclosure:

    "We believe transparency is in the public's best interest...[and]... in this case, we intentionally delayed disclosing the issue by one week to ensure the safety of millions of additional WordPress sites."

    "Data from all four WAFs and WordPress hosts showed no indication that the vulnerability had been exploited in the wild. As a result, we made the decision to delay disclosure of this particular issue to give time for automatic updates to run and ensure as many users as possible were protected before the issue was made public."


Patch your CMS Now!


The flaw has been rated critical, although the fix has automatically been deployed on millions of WordPress installations in the few hours after the patch was issued.

For a more technical explanation about the vulnerability, you can head on the Sucuri's official blog post.

WordPress admins who have not yet implemented the patch against the nasty vulnerability are strongly advised to update their CMS to Wordpress version 4.7.2.
"The State is a body of armed men."

Offline Palloy2

  • Administrator
  • Sous Chef
  • *****
  • Posts: 6097
    • View Profile
    • Palloy's Blog
Re: Critical WordPress REST API Bug: Prevent Your Blog From Being Hacked!
« Reply #1 on: February 08, 2017, 01:17:49 PM »
Keep your updates up to date - once a bug has been found and patches issued and made public, unpatched websites will be attacked within days.  WordPress hosted sites (like something.wordpress.com) and patched automatically, and sites hosted elsewhere (like doomsteaddiner.net) will be updated automatically since v4.7.0, UNLESS you switch it off.

http://thehackernews.com/2017/02/wordpress-hack-seo.html
Thousands of WordPress Sites Hacked Using Recently Disclosed Vulnerability
February 07, 2017
Swati Khandelwal
 
Last week, we reported about a critical zero-day flaw in WordPress that was silently patched by the company before hackers have had their hands on the nasty bug to exploit millions of WordPress websites.

To ensure the security of millions of websites and its users, WordPress delayed the vulnerability disclosure for over a week and worked closely with security companies and hosts to install the patch, ensuring that the issue was dealt with in short order before it became public.

But even after the company's effort to protect its customers, thousands of admins did not bother to update their websites, which are still vulnerable to the critical bug and has already been exploited by hackers.

While WordPress includes a default feature that automatically updates unpatched websites, some admins running critical services disable this feature for first testing and then applying patches.

Even the news blog of one of the famous Linux distribution OpenSUSE (news.opensuse.org) was also hacked, but restored immediately without breach of any other part of openSUSE's infrastructure, CIO reports.

The vulnerability resided in Wordpress REST API that would lead to the creation of new flaws, allowing an unauthenticated attacker to delete pages or modify all pages on unpatched websites and redirect their visitors to malicious exploits and a large number of attacks.

The security researcher at Sucuri, who privately disclosed the flaw to WordPress, said they started noticing the attacks leveraging this bug less than 48 hours after disclosure. They noticed at least four different campaigns targeting still unpatched websites.

In one such campaign, hackers were successful in replacing the content of over 66,000 web pages with "Hacked by" messages. Rest campaigns have targeted roughly 1000 pages in total.

Besides defacing websites, such attacks appear to be carried out mostly for black hat SEO campaign in order to spread spam and gain ranking in search engine, which is also known as search engine poisoning.

    "What we expect to see is a lot more SEO spam (Search Engine Poisoning) attempts moving forward," explained Daniel Cid, CTO, and founder of Sucuri.

    "There’s already a few exploit attempts that try to add spam images and content to a post. Due to the monetization possibilities, this will likely be the #1 route to abuse this vulnerability."

So, site administrators who have not yet updated their websites to the latest WordPress release 4.7.2 are urged to patch them immediately before becoming next target of SEO spammers and hackers.
"The State is a body of armed men."

 

Related Topics

  Subject / Started by Replies Last post
1 Replies
648 Views
Last post April 12, 2016, 03:37:17 PM
by Palloy
0 Replies
147 Views
Last post June 28, 2017, 03:29:18 PM
by Palloy2
1 Replies
217 Views
Last post May 15, 2018, 02:47:19 PM
by Palloy2