CERTA-2011-AVI-380

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

Plusieurs vulnérabilités dans phpMyAdmin permettent à un utilisateur distant d'exécuter du code arbitraire, de porter atteinte à l'intégrité ou à la confidentialité de certaines données.

Description

Plusieurs vulnérabilités sont présentes dans phpMyAdmin :

  • la première permet de modifier le contenu de certaines variables de session et ce faisant d'exécuter du code arbitraire ;
  • la seconde concerne un manque de contrôle sur certaines URL passées au serveur et permet d'exécuter du code arbitraire à distance ;
  • la troisième vulnérabilité relative à un manque de contrôle des expressions régulières permet de conduire des attaques de type traversée de répertoire ;
  • la dernière concerne également un problème de traversée de répertoire lié à la gestion de certains types MIME.

Solution

Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation).

None
Impacted products
Vendor Product Description
phpMyAdmin phpMyAdmin phpMyAdmin versions 3.4.3.0 et antérieures.
phpMyAdmin phpMyAdmin phpMyAdmin versions 3.3.10.1 et antérieures ;
References

Show details on source website
To clipboard 

{
  "$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
  "affected_systems": [
    {
      "description": "phpMyAdmin versions 3.4.3.0 et ant\u00e9rieures.",
      "product": {
        "name": "phpMyAdmin",
        "vendor": {
          "name": "phpMyAdmin",
          "scada": false
        }
      }
    },
    {
      "description": "phpMyAdmin versions 3.3.10.1 et ant\u00e9rieures ;",
      "product": {
        "name": "phpMyAdmin",
        "vendor": {
          "name": "phpMyAdmin",
          "scada": false
        }
      }
    }
  ],
  "affected_systems_content": null,
  "content": "## Description\n\nPlusieurs vuln\u00e9rabilit\u00e9s sont pr\u00e9sentes dans phpMyAdmin :\n\n-   la premi\u00e8re permet de modifier le contenu de certaines variables de\n    session et ce faisant d\u0027ex\u00e9cuter du code arbitraire ;\n-   la seconde concerne un manque de contr\u00f4le sur certaines URL pass\u00e9es\n    au serveur et permet d\u0027ex\u00e9cuter du code arbitraire \u00e0 distance ;\n-   la troisi\u00e8me vuln\u00e9rabilit\u00e9 relative \u00e0 un manque de contr\u00f4le des\n    expressions r\u00e9guli\u00e8res permet de conduire des attaques de type\n    travers\u00e9e de r\u00e9pertoire ;\n-   la derni\u00e8re concerne \u00e9galement un probl\u00e8me de travers\u00e9e de\n    r\u00e9pertoire li\u00e9 \u00e0 la gestion de certains types MIME.\n\n## Solution\n\nSe r\u00e9f\u00e9rer au bulletin de s\u00e9curit\u00e9 de l\u0027\u00e9diteur pour l\u0027obtention des\ncorrectifs (cf. section Documentation).\n",
  "cves": [
    {
      "name": "CVE-2011-2508",
      "url": "https://www.cve.org/CVERecord?id=CVE-2011-2508"
    },
    {
      "name": "CVE-2011-2505",
      "url": "https://www.cve.org/CVERecord?id=CVE-2011-2505"
    },
    {
      "name": "CVE-2011-2506",
      "url": "https://www.cve.org/CVERecord?id=CVE-2011-2506"
    },
    {
      "name": "CVE-2011-2507",
      "url": "https://www.cve.org/CVERecord?id=CVE-2011-2507"
    }
  ],
  "initial_release_date": "2011-07-05T00:00:00",
  "last_revision_date": "2011-07-05T00:00:00",
  "links": [
    {
      "title": "Bulletins de s\u00e9curit\u00e9 phpMyAdmin PMASA-2011-7 du 02 juillet    2011 :",
      "url": "http://www.phpmyadmin.net/home_page/security/PMASA-2011-7.php"
    },
    {
      "title": "Bulletins de s\u00e9curit\u00e9 phpMyAdmin PMASA-2011-6 du 02 juillet    2011 :",
      "url": "http://www.phpmyadmin.net/home_page/security/PMASA-2011-6.php"
    },
    {
      "title": "Bulletins de s\u00e9curit\u00e9 phpMyAdmin PMASA-2011-5 du 02 juillet    2011 :",
      "url": "http://www.phpmyadmin.net/home_page/security/PMASA-2011-5.php"
    },
    {
      "title": "Bulletins de s\u00e9curit\u00e9 phpMyAdmin PMASA-2011-8 du 02 juillet    2011 :",
      "url": "http://www.phpmyadmin.net/home_page/security/PMASA-2011-8.php"
    }
  ],
  "reference": "CERTA-2011-AVI-380",
  "revisions": [
    {
      "description": "version initiale.",
      "revision_date": "2011-07-05T00:00:00.000000"
    }
  ],
  "risks": [
    {
      "description": "Ex\u00e9cution de code arbitraire \u00e0 distance"
    },
    {
      "description": "Atteinte \u00e0 l\u0027int\u00e9grit\u00e9 des donn\u00e9es"
    },
    {
      "description": "Atteinte \u00e0 la confidentialit\u00e9 des donn\u00e9es"
    }
  ],
  "summary": "Plusieurs vuln\u00e9rabilit\u00e9s dans phpMyAdmin permettent \u00e0 un utilisateur\ndistant d\u0027ex\u00e9cuter du code arbitraire, de porter atteinte \u00e0 l\u0027int\u00e9grit\u00e9\nou \u00e0 la confidentialit\u00e9 de certaines donn\u00e9es.\n",
  "title": "Multiples vuln\u00e9rabilit\u00e9s dans phpMyAdmin",
  "vendor_advisories": [
    {
      "published_at": null,
      "title": "Bulletins de s\u00e9curit\u00e9 phpMyAdmin du 03 juillet 2011",
      "url": null
    }
  ]
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

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.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Loading timeline…




    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.