SoylentNews is people
SoylentNews
Submitted via IRC for TheMightyBuzzard
As if there aren't enough ways to attack a WordPress site, an Israeli researcher has published details of how almost anyone can launch a denial of service (DoS) attack against almost any WordPress with just one computer. That, he suggests, is almost 30% of all websites on the internet.
The attack uses the vulnerability associated with CVE-2018-6389. The CVE database, at the time of writing, has no details, marking it only as 'reserved' for future use. Details, however, can be found in a Barak Tawily blog post published Monday. It is an abuse of the WordPress load-scripts.php function, which exists to allow administrators/web designers to improve website performance by combining multiple JavaScript files into a single request at the server end.
[...] Tawily goes on to show that mitigation isn't really that difficult if you know what to do (which many WordPress users do not). He "forked WordPress project and patched it so no one but authenticated users can access the load-*.php files, without actually harming the wp-login.php file functionality." He goes further to provide a bash script that modifies the relevant files to mitigate the vulnerability.
Source: http://www.securityweek.com/one-computer-can-knock-almost-any-wordpress-site-offline
(Score: 2) by NotSanguine on Wednesday February 07 2018, @07:29PM (1 child)
From TFS:
IIUC, once a vulnerability has been reported, Mitre generally assigns a CVE ID and "reserves" it for that vulnerability until they obtain and have time to include relevant data (usually including specifics of the vulnerability as well as sample exploits). As of this message (7 Feb 2018, 1924 GMT), Mitre appears to have added information about the vulnerability [mitre.org].
The US National Vulnerability Database [nist.gov] *sometimes* has information sooner than the CVE database.
No, no, you're not thinking; you're just being logical. --Niels Bohr
(Score: 3, Informative) by TheRaven on Thursday February 08 2018, @10:08AM
A lot of vulnerabilities are embargoed as well. The CVE is assigned so people know that they're talking about the same thing, but if the discoverer has done responsible disclosure then the details won't be published until after there's been a coordinated patch release.
sudo mod me up