CERTA-2007-AVI-507

Vulnerability from certfr_avis - Published: 2007-11-22 - Updated: 2008-04-16

Une vulnérabilité dans GuppY permet l'exécution de code arbitraire à distance.

Description

Une vulnérabilité a été découverte dans GuppY. Elle affecte le fichier error.php. Cette vulnérabilité est connue depuis janvier 2007 mais n'était pas correctement traitée par la version 4.5.17. L'exploitation de cette vulnérabilité permet l'exécution de code arbitraire à distance.

Solution

Installer la version 4.5.19 ou la version 4.6.4.

None
Impacted products
Vendor Product Description
N/A N/A GuppY versions 4.6.1 à 4.6.3.
N/A N/A GuppY versions 4.5.18 et antérieures ;
References

Show details on source website

{
  "$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
  "affected_systems": [
    {
      "description": "GuppY versions 4.6.1 \u00e0 4.6.3.",
      "product": {
        "name": "N/A",
        "vendor": {
          "name": "N/A",
          "scada": false
        }
      }
    },
    {
      "description": "GuppY versions 4.5.18 et ant\u00e9rieures ;",
      "product": {
        "name": "N/A",
        "vendor": {
          "name": "N/A",
          "scada": false
        }
      }
    }
  ],
  "affected_systems_content": null,
  "content": "## Description\n\nUne vuln\u00e9rabilit\u00e9 a \u00e9t\u00e9 d\u00e9couverte dans GuppY. Elle affecte le fichier\nerror.php. Cette vuln\u00e9rabilit\u00e9 est connue depuis janvier 2007 mais\nn\u0027\u00e9tait pas correctement trait\u00e9e par la version 4.5.17. L\u0027exploitation\nde cette vuln\u00e9rabilit\u00e9 permet l\u0027ex\u00e9cution de code arbitraire \u00e0 distance.\n\n## Solution\n\nInstaller la version 4.5.19 ou la version 4.6.4.\n",
  "cves": [],
  "initial_release_date": "2007-11-22T00:00:00",
  "last_revision_date": "2008-04-16T00:00:00",
  "links": [
    {
      "title": "T\u00e9l\u00e9chargement de GuppY :",
      "url": "http://www.freeguppy.org/download.php"
    }
  ],
  "reference": "CERTA-2007-AVI-507",
  "revisions": [
    {
      "description": "version initiale.",
      "revision_date": "2007-11-22T00:00:00.000000"
    },
    {
      "description": "prise en compte de la branche 4.6.",
      "revision_date": "2008-04-16T00:00:00.000000"
    }
  ],
  "risks": [
    {
      "description": "Ex\u00e9cution de code arbitraire \u00e0 distance"
    }
  ],
  "summary": "Une vuln\u00e9rabilit\u00e9 dans \u003cspan class=\"textit\"\u003eGuppY\u003c/span\u003e permet\nl\u0027ex\u00e9cution de code arbitraire \u00e0 distance.\n",
  "title": "Vuln\u00e9rabilit\u00e9 dans GuppY",
  "vendor_advisories": [
    {
      "published_at": null,
      "title": "Note de version 4.5.19 de GuppY",
      "url": null
    }
  ]
}


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…