CERTA-2011-AVI-318

Vulnerability from certfr_avis - Published: 2011-05-27 - Updated: 2011-05-27

Plusieurs vulnérabilités ont été corrigées dans WordPress 3.1.3 qui permettent à un utilisateur malintentionné de contourner la politique de sécurité ou d'effectuer une attaque de type injection de code indirecte.

Description

Plusieurs vulnérabilités ont été corrigées dans WordPress 3.1.3. Elles permettent, notamment, de récupérer la liste des utilisateurs qui ne sont pas des auteurs. Une protection a également été ajoutée dans les pages d'authentification et d'administration afin de se protéger contre des attaques de type injection de requêtes illégitime par rebond (CSRF) en utilisant le champ 'X-Frame-Options' lorsque le navigateur le supporte.

Solution

Mettre WordPress à jour en version 3.1.3.

WordPress versions 3.1.2 et antérieures.

Impacted products
Vendor Product Description
References

Show details on source website
To clipboard 

{
  "$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
  "affected_systems": [],
  "affected_systems_content": "\u003cP\u003eWordPress versions 3.1.2 et ant\u00e9rieures.\u003c/P\u003e",
  "content": "## Description\n\nPlusieurs vuln\u00e9rabilit\u00e9s ont \u00e9t\u00e9 corrig\u00e9es dans WordPress 3.1.3. Elles\npermettent, notamment, de r\u00e9cup\u00e9rer la liste des utilisateurs qui ne\nsont pas des auteurs. Une protection a \u00e9galement \u00e9t\u00e9 ajout\u00e9e dans les\npages d\u0027authentification et d\u0027administration afin de se prot\u00e9ger contre\ndes attaques de type injection de requ\u00eates ill\u00e9gitime par rebond (CSRF)\nen utilisant le champ \u0027X-Frame-Options\u0027 lorsque le navigateur le\nsupporte.\n\n## Solution\n\nMettre WordPress \u00e0 jour en version 3.1.3.\n",
  "cves": [
    {
      "name": "CVE-2011-3127",
      "url": "https://www.cve.org/CVERecord?id=CVE-2011-3127"
    },
    {
      "name": "CVE-2011-3126",
      "url": "https://www.cve.org/CVERecord?id=CVE-2011-3126"
    },
    {
      "name": "CVE-2011-3129",
      "url": "https://www.cve.org/CVERecord?id=CVE-2011-3129"
    },
    {
      "name": "CVE-2011-3125",
      "url": "https://www.cve.org/CVERecord?id=CVE-2011-3125"
    },
    {
      "name": "CVE-2011-3122",
      "url": "https://www.cve.org/CVERecord?id=CVE-2011-3122"
    },
    {
      "name": "CVE-2011-3130",
      "url": "https://www.cve.org/CVERecord?id=CVE-2011-3130"
    },
    {
      "name": "CVE-2011-3128",
      "url": "https://www.cve.org/CVERecord?id=CVE-2011-3128"
    }
  ],
  "initial_release_date": "2011-05-27T00:00:00",
  "last_revision_date": "2011-05-27T00:00:00",
  "links": [],
  "reference": "CERTA-2011-AVI-318",
  "revisions": [
    {
      "description": "version initiale.",
      "revision_date": "2011-05-27T00:00:00.000000"
    }
  ],
  "risks": [
    {
      "description": "Injection de requ\u00eates ill\u00e9gitimes par rebond (CSRF)"
    },
    {
      "description": "Contournement de la politique de s\u00e9curit\u00e9"
    }
  ],
  "summary": "Plusieurs vuln\u00e9rabilit\u00e9s ont \u00e9t\u00e9 corrig\u00e9es dans WordPress 3.1.3 qui\npermettent \u00e0 un utilisateur malintentionn\u00e9 de contourner la politique de\ns\u00e9curit\u00e9 ou d\u0027effectuer une attaque de type injection de code indirecte.\n",
  "title": "Vuln\u00e9rabilit\u00e9s dans WordPress",
  "vendor_advisories": [
    {
      "published_at": null,
      "title": "Annonce de la version 3.1.3 de Wordpress du 25 mai 2011",
      "url": "http://wordpress.org/news/2011/05/wordpress-3-1-3/"
    }
  ]
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.



Detection rules are retrieved from Rulezet.