CERTA-2005-ALE-013

Vulnerability from certfr_alerte - Published: 2005-10-07 - Updated: 2013-06-06

Une vulnérabilité dans certains produits Citrix permet à un utilisateur mal intentionné de contourner la politique de sécurité.

Description

Une vulnérabilité découverte dans la politique de filtrage basée sur la variable client name permet à un utilisateur distant mal intentionné de contourner la politique de sécurité. Une personne malveillante peut s'authentifier auprès du serveur après avoir habilement modifié le fichier launch.ica.

Contournement provisoire

Changer la politique de sécurité de l'application Citrix de manière à ce que l'authentification ne se fasse pas par le biais de la variable client name.

Solution

Ce produit n'est plus maintenu par l'éditeur. Il convient de migrer vers une version soutenue du produit. Se référer au bulletin de sécurité de l'éditeur pour plus d'informations (cf. section Documentation).

None
Impacted products
Vendor Product Description
Citrix N/A Citrix Présentation Server 4.x.
Citrix N/A Citrix Metaframe Presentation Server 3.x ;
References

Show details on source website

{
  "$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
  "affected_systems": [
    {
      "description": "Citrix Pr\u00e9sentation Server 4.x.",
      "product": {
        "name": "N/A",
        "vendor": {
          "name": "Citrix",
          "scada": false
        }
      }
    },
    {
      "description": "Citrix Metaframe Presentation Server 3.x ;",
      "product": {
        "name": "N/A",
        "vendor": {
          "name": "Citrix",
          "scada": false
        }
      }
    }
  ],
  "affected_systems_content": null,
  "closed_at": "2013-06-06",
  "content": "## Description\n\nUne vuln\u00e9rabilit\u00e9 d\u00e9couverte dans la politique de filtrage bas\u00e9e sur la\nvariable client name permet \u00e0 un utilisateur distant mal intentionn\u00e9 de\ncontourner la politique de s\u00e9curit\u00e9. Une personne malveillante peut\ns\u0027authentifier aupr\u00e8s du serveur apr\u00e8s avoir habilement modifi\u00e9 le\nfichier launch.ica.\n\n## Contournement provisoire\n\nChanger la politique de s\u00e9curit\u00e9 de l\u0027application Citrix de mani\u00e8re \u00e0 ce\nque l\u0027authentification ne se fasse pas par le biais de la variable\nclient name.\n\n## Solution\n\nCe produit n\u0027est plus maintenu par l\u0027\u00e9diteur. Il convient de migrer vers\nune version soutenue du produit. Se r\u00e9f\u00e9rer au bulletin de s\u00e9curit\u00e9 de\nl\u0027\u00e9diteur pour plus d\u0027informations (cf. section Documentation).\n",
  "cves": [
    {
      "name": "CVE-2005-3134",
      "url": "https://www.cve.org/CVERecord?id=CVE-2005-3134"
    }
  ],
  "initial_release_date": "2005-10-07T00:00:00",
  "last_revision_date": "2013-06-06T00:00:00",
  "links": [
    {
      "title": "Site Internet de l\u0027\u00e9diteur :",
      "url": "http://support.citrix.com"
    }
  ],
  "reference": "CERTA-2005-ALE-013",
  "revisions": [
    {
      "description": "version initiale.",
      "revision_date": "2005-10-07T00:00:00.000000"
    },
    {
      "description": "ajout CVE et fermeture de l\u0027alerte.",
      "revision_date": "2013-06-06T00:00:00.000000"
    }
  ],
  "risks": [
    {
      "description": "Contournement de la politique de s\u00e9curit\u00e9"
    }
  ],
  "summary": "Une vuln\u00e9rabilit\u00e9 dans certains produits Citrix permet \u00e0 un utilisateur\nmal intentionn\u00e9 de contourner la politique de s\u00e9curit\u00e9.\n",
  "title": "Vuln\u00e9rabilit\u00e9 dans Citrix Metaframe Presentation",
  "vendor_advisories": [
    {
      "published_at": null,
      "title": "Bulletin de s\u00e9curit\u00e9 Citrix #CTX107705 du 27 septembre 2005",
      "url": "http://support.citrix.com/article/CTX107705"
    }
  ]
}



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.