CERTA-2006-AVI-095

Vulnerability from certfr_avis - Published: 2006-02-28 - Updated: 2006-03-13

Plusieures vulnérabilités dans SquirrelMail permettent à un utilisateur mal intentionné de porter atteinte à l'intégrité ou à la confidentialité des données et également de réaliser une attaque de type Cross-Site Scripting.

Description

Trois vulnérabilités ont été identifiées dans SquirrelMail :

  • La première vulnérabilité est due à un manque de contrôle du paramètre right_main du fichier webmail.php. Elle permet à un utilisateur distant mal intentionné d'injecter du code et de réaliser une attaque de type Cross-Site Scripting par le biais d'un courrier électronique malicieusement construit.
  • La deuxième vulnérabilité est due à un manque de contrôle dans le traitement des lignes de commentaires dans les zones de définition de styles. Elle permet à un utilisateur distant d'injecter du code et de réaliser une attaque de type Cross-Site Scripting par le biais d'un courrier électronique malicieusement construit.
  • La dernière vulnérabilité est due à un manque de contrôle du paramètre sqimap_mailbox_select. Elle permet à un utilisateur local et identifié d'exécuter des commandes IMAP ou SMTP arbitraires et de porter ainsi atteinte à l'intégrité ou la confidentialité des données présentes dans les comptes de messagerie.

Solution

La version CVS de SquirrelMail corrige le problème.

SquirrelMail versions 1.4.5 et antérieures.

Impacted products
Vendor Product Description

Show details on source website

{
  "$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
  "affected_systems": [],
  "affected_systems_content": "\u003cTT\u003eSquirrelMail\u003c/TT\u003e versions 1.4.5 et  ant\u00e9rieures.",
  "content": "## Description\n\nTrois vuln\u00e9rabilit\u00e9s ont \u00e9t\u00e9 identifi\u00e9es dans SquirrelMail :\n\n-   La premi\u00e8re vuln\u00e9rabilit\u00e9 est due \u00e0 un manque de contr\u00f4le du\n    param\u00e8tre right_main du fichier webmail.php. Elle permet \u00e0 un\n    utilisateur distant mal intentionn\u00e9 d\u0027injecter du code et de\n    r\u00e9aliser une attaque de type Cross-Site Scripting par le biais d\u0027un\n    courrier \u00e9lectronique malicieusement construit.\n-   La deuxi\u00e8me vuln\u00e9rabilit\u00e9 est due \u00e0 un manque de contr\u00f4le dans le\n    traitement des lignes de commentaires dans les zones de d\u00e9finition\n    de styles. Elle permet \u00e0 un utilisateur distant d\u0027injecter du code\n    et de r\u00e9aliser une attaque de type Cross-Site Scripting par le biais\n    d\u0027un courrier \u00e9lectronique malicieusement construit.\n-   La derni\u00e8re vuln\u00e9rabilit\u00e9 est due \u00e0 un manque de contr\u00f4le du\n    param\u00e8tre sqimap_mailbox_select. Elle permet \u00e0 un utilisateur local\n    et identifi\u00e9 d\u0027ex\u00e9cuter des commandes IMAP ou SMTP arbitraires et de\n    porter ainsi atteinte \u00e0 l\u0027int\u00e9grit\u00e9 ou la confidentialit\u00e9 des\n    donn\u00e9es pr\u00e9sentes dans les comptes de messagerie.\n\n## Solution\n\nLa version CVS de SquirrelMail corrige le probl\u00e8me.\n",
  "cves": [
    {
      "name": "CVE-2006-0195",
      "url": "https://www.cve.org/CVERecord?id=CVE-2006-0195"
    },
    {
      "name": "CVE-2006-0377",
      "url": "https://www.cve.org/CVERecord?id=CVE-2006-0377"
    },
    {
      "name": "CVE-2006-0188",
      "url": "https://www.cve.org/CVERecord?id=CVE-2006-0188"
    }
  ],
  "initial_release_date": "2006-02-28T00:00:00",
  "last_revision_date": "2006-03-13T00:00:00",
  "links": [
    {
      "title": "Bulletin de s\u00e9curit\u00e9 SquirrelMail du 15 f\u00e9vrier 2006 :",
      "url": "http://www.squirrelmail.org/security/issue/2006-02-15"
    },
    {
      "title": "Bulletin de s\u00e9curit\u00e9 Mandriva du 27 f\u00e9vrier 2006 :",
      "url": "http://wwwnew.mandriva.com/security/advisories?name=MDKSA-2006:049"
    },
    {
      "title": "Site de SquirrelMail :",
      "url": "http://www.squirrelmail.org"
    },
    {
      "title": "Bulletin de s\u00e9curit\u00e9 SquirrelMail du 10 f\u00e9vrier 2006 :",
      "url": "http://www.squirrelmail.org/security/issue/2006-02-10"
    },
    {
      "title": "Bulletin de s\u00e9curit\u00e9 Debian DSA-988 du 08 mars 2006 :",
      "url": "http://www.debian.org/security/2006/dsa-988"
    },
    {
      "title": "Bulletin de s\u00e9curit\u00e9 Gentoo GLSA 200603-09 du 12 mars 2006    :",
      "url": "http://www.gentoo.org/security/en/glsa/glsa-200603-09.xml"
    },
    {
      "title": "Bulletin de s\u00e9curit\u00e9 SUSE SUSE-SR:2006:005 du 03 mars 2006    :",
      "url": "http://www.novell.com/linux/security/advisories/2006_05_sr.html"
    },
    {
      "title": "Bulletin de s\u00e9curit\u00e9 FreeBSD pour squirrelmail du 24    f\u00e9vrier 2006 :",
      "url": "http://www.vuxml.org/freebsd/pkg-squirrelmail.html"
    },
    {
      "title": "Bulletin de s\u00e9curit\u00e9 SquirrelMail du 01 f\u00e9vrier 2006 :",
      "url": "http://www.squirrelmail.org/security/issue/2006-02-01"
    }
  ],
  "reference": "CERTA-2006-AVI-095",
  "revisions": [
    {
      "description": "version initiale.",
      "revision_date": "2006-02-28T00:00:00.000000"
    },
    {
      "description": "ajout de la r\u00e9f\u00e9rence au bulletin de s\u00e9curit\u00e9 FreeBSD.",
      "revision_date": "2006-03-08T00:00:00.000000"
    },
    {
      "description": "ajout de la r\u00e9f\u00e9rence au bulletin de s\u00e9curit\u00e9 Debian.",
      "revision_date": "2006-03-09T00:00:00.000000"
    },
    {
      "description": "ajout des r\u00e9f\u00e9rences aux bulletins de s\u00e9curit\u00e9 SUSE et Gentoo.",
      "revision_date": "2006-03-13T00:00:00.000000"
    }
  ],
  "risks": [
    {
      "description": "Atteinte \u00e0 l\u0027int\u00e9grit\u00e9 des donn\u00e9es"
    },
    {
      "description": "Attaque de type cross-site scripting"
    },
    {
      "description": "Atteinte \u00e0 la confidentialit\u00e9 des donn\u00e9es"
    }
  ],
  "summary": "Plusieures vuln\u00e9rabilit\u00e9s dans SquirrelMail permettent \u00e0 un utilisateur\nmal intentionn\u00e9 de porter atteinte \u00e0 l\u0027int\u00e9grit\u00e9 ou \u00e0 la confidentialit\u00e9\ndes donn\u00e9es et \u00e9galement de r\u00e9aliser une attaque de type Cross-Site\nScripting.\n",
  "title": "Multiples vuln\u00e9rabilit\u00e9s dans Squirrelmail",
  "vendor_advisories": [
    {
      "published_at": null,
      "title": "Bulletins de s\u00e9curit\u00e9 SquirrelMail du 15 f\u00e9vrier 2006",
      "url": null
    },
    {
      "published_at": null,
      "title": "Bulletins de s\u00e9curit\u00e9 SquirrelMail du 10 f\u00e9vrier 2006",
      "url": null
    },
    {
      "published_at": null,
      "title": "Bulletins de s\u00e9curit\u00e9 SquirrelMail du 01 f\u00e9vrier 2006",
      "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.