CERTA-2006-AVI-280

Vulnerability from certfr_avis - Published: 2006-07-11 - Updated: 2006-07-11

None

Description

WinGate est une passerelle applicative offrant plusieurs services de communication. Une vulnérabilité a été identifiée dans celle-ci, au niveau du service de messagerie IMAP (pour Internet Message Access Protocol) servant à rapatrier des courriers électroniques. Il ne controle pas correctement certaines commandes comme "CREATE", "SELECT", "DELETE", "RENAME", "COPY", "APPEND" ou "LIST". Un utilisateur malveillant distant peut profiter de cette vulnérabilité pour consulter ou modifier les courriers d'autres utilisateurs. Il pourrait aussi créer ou accéder à certains répertoires sur le système vulnérable.

Solution

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

Les versions antérieures à 6.1.4 Build 1099.

Impacted products
Vendor Product Description
References

Show details on source website

{
  "$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
  "affected_systems": [],
  "affected_systems_content": "\u003cP\u003eLes versions ant\u00e9rieures \u00e0 6.1.4 Build 1099.\u003c/P\u003e",
  "content": "## Description\n\nWinGate est une passerelle applicative offrant plusieurs services de\ncommunication. Une vuln\u00e9rabilit\u00e9 a \u00e9t\u00e9 identifi\u00e9e dans celle-ci, au\nniveau du service de messagerie IMAP (pour Internet Message Access\nProtocol) servant \u00e0 rapatrier des courriers \u00e9lectroniques. Il ne\ncontrole pas correctement certaines commandes comme \"CREATE\", \"SELECT\",\n\"DELETE\", \"RENAME\", \"COPY\", \"APPEND\" ou \"LIST\". Un utilisateur\nmalveillant distant peut profiter de cette vuln\u00e9rabilit\u00e9 pour consulter\nou modifier les courriers d\u0027autres utilisateurs. Il pourrait aussi cr\u00e9er\nou acc\u00e9der \u00e0 certains r\u00e9pertoires sur le syst\u00e8me vuln\u00e9rable.\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-2006-2917",
      "url": "https://www.cve.org/CVERecord?id=CVE-2006-2917"
    }
  ],
  "initial_release_date": "2006-07-11T00:00:00",
  "last_revision_date": "2006-07-11T00:00:00",
  "links": [
    {
      "title": "Mise \u00e0 jour WinGate de Qbik du 10 juillet 2006 :",
      "url": "http://www.wingate.com/download.php"
    }
  ],
  "reference": "CERTA-2006-AVI-280",
  "revisions": [
    {
      "description": "version initiale.",
      "revision_date": "2006-07-11T00:00:00.000000"
    }
  ],
  "risks": [
    {
      "description": "Atteinte \u00e0 l\u0027int\u00e9grit\u00e9 des donn\u00e9es"
    },
    {
      "description": "Contournement de la politique de s\u00e9curit\u00e9"
    },
    {
      "description": "Atteinte \u00e0 la confidentialit\u00e9 des donn\u00e9es"
    }
  ],
  "summary": null,
  "title": "Vuln\u00e9rabilit\u00e9 de Qbik WinGate",
  "vendor_advisories": [
    {
      "published_at": null,
      "title": "Bulletin de mise \u00e0 jour WinGate",
      "url": null
    }
  ]
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

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.

Events included in the timeline

Loading timeline…


    Loading…

    Loading…

    Loading…

    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.