CERTA-2010-AVI-616

Vulnerability from certfr_avis - Published: 2010-12-17 - Updated: 2010-12-17

Une porte dérobée, déposée dans un fichier source de phpMyFAQ, permet de provoquer de l'exécution de code arbitraire à distance.

Description

Suite à la compromission du serveur principal du projet phpMyFAQ, une porte dérobée a été déposée dans les fichiers sources des versions 2.6.11 et 2.6.12. Ces versions compromises, distribuées entre le 4 et le 15 décembre 2010 permettent à un utilisateur malveillant distant d'inclure du code PHP de façon arbitraire.

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
N/A N/A phpMyFAQ 2.6.11.
N/A N/A phpMyFAQ 2.6.12 ;
References

Show details on source website

{
  "$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
  "affected_systems": [
    {
      "description": "phpMyFAQ 2.6.11.",
      "product": {
        "name": "N/A",
        "vendor": {
          "name": "N/A",
          "scada": false
        }
      }
    },
    {
      "description": "phpMyFAQ 2.6.12 ;",
      "product": {
        "name": "N/A",
        "vendor": {
          "name": "N/A",
          "scada": false
        }
      }
    }
  ],
  "affected_systems_content": null,
  "content": "## Description\n\nSuite \u00e0 la compromission du serveur principal du projet phpMyFAQ, une\nporte d\u00e9rob\u00e9e a \u00e9t\u00e9 d\u00e9pos\u00e9e dans les fichiers sources des versions\n2.6.11 et 2.6.12. Ces versions compromises, distribu\u00e9es entre le 4 et le\n15 d\u00e9cembre 2010 permettent \u00e0 un utilisateur malveillant distant\nd\u0027inclure du code PHP de fa\u00e7on arbitraire.\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": [],
  "initial_release_date": "2010-12-17T00:00:00",
  "last_revision_date": "2010-12-17T00:00:00",
  "links": [],
  "reference": "CERTA-2010-AVI-616",
  "revisions": [
    {
      "description": "version initiale.",
      "revision_date": "2010-12-17T00:00:00.000000"
    }
  ],
  "risks": [
    {
      "description": "Ex\u00e9cution de code arbitraire \u00e0 distance"
    }
  ],
  "summary": "Une porte d\u00e9rob\u00e9e, d\u00e9pos\u00e9e dans un fichier source de phpMyFAQ, permet de\nprovoquer de l\u0027ex\u00e9cution de code arbitraire \u00e0 distance.\n",
  "title": "Vuln\u00e9rabilit\u00e9 dans phpMyFAQ",
  "vendor_advisories": [
    {
      "published_at": null,
      "title": "Bulletin de s\u00e9curit\u00e9 phpMyFAQ du 15 d\u00e9cembre 2010",
      "url": "http://www.phpmyfaq.de/advisory_2010-12-15.php"
    }
  ]
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

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.


Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…