CERTA-2009-AVI-324

Vulnerability from certfr_avis - Published: 2009-08-12 - Updated: 2009-08-12

Une vulnérabilité dans ASP.NET permet à un utilisateur malveillant de réaliser un déni de service à distance.

Description

Le composant Microsoft .NET Framework de Microsoft Windows ne gère pas correctement les files de requêtes quand Internet Information Services 7.0 (IIS) est installé et que ASP.NET est configuré pour utiliser le mode « intégré » et non le mode « classique ». Un attaquant peut créer des requêtes HTTP anonymes spécialement conçues pour épuiser les ressources du serveur Web vulnérable.

Les versions Vista Starter et Familiale Basique ne sont pas concernées car elles ne supportent pas IIS 7.

Solution

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

Plateformes :

  • Microsoft .NET Framework 2.0 SP1 et SP2 ;
  • Microsoft .NET Framework 3.5 et 3.5 SP1.
sur systèmes d'exploitation :
  • Windows Vista et Vista SP1, versions x64 comprises ;
  • Windows Server 2008 pour architectures 32 bits, x64 et Itanium.

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\u003ePlateformes :  \u003cUL\u003e    \u003cLI\u003eMicrosoft .NET Framework 2.0 SP1 et SP2 ;\u003c/LI\u003e    \u003cLI\u003eMicrosoft .NET Framework 3.5 et 3.5 SP1.\u003c/LI\u003e  \u003c/UL\u003esur syst\u00e8mes d\u0027exploitation :  \u003cUL\u003e    \u003cLI\u003eWindows Vista et Vista SP1, versions x64 comprises ;\u003c/LI\u003e    \u003cLI\u003eWindows Server 2008 pour architectures 32 bits, x64 et    Itanium.\u003c/LI\u003e  \u003c/UL\u003e\u003c/p\u003e",
  "content": "## Description\n\nLe composant Microsoft .NET Framework de Microsoft Windows ne g\u00e8re pas\ncorrectement les files de requ\u00eates quand Internet Information Services\n7.0 (IIS) est install\u00e9 et que ASP.NET est configur\u00e9 pour utiliser le\nmode \u00ab int\u00e9gr\u00e9 \u00bb et non le mode \u00ab classique \u00bb. Un attaquant peut cr\u00e9er\ndes requ\u00eates HTTP anonymes sp\u00e9cialement con\u00e7ues pour \u00e9puiser les\nressources du serveur Web vuln\u00e9rable.\n\nLes versions Vista Starter et Familiale Basique ne sont pas concern\u00e9es\ncar elles ne supportent pas IIS 7.\n\n## Solution\n\nSe r\u00e9f\u00e9rer au bulletin de s\u00e9curit\u00e9 MS09-036 de Microsoft pour\nl\u0027obtention des correctifs (cf. section Documentation).\n",
  "cves": [
    {
      "name": "CVE-2009-1536",
      "url": "https://www.cve.org/CVERecord?id=CVE-2009-1536"
    }
  ],
  "initial_release_date": "2009-08-12T00:00:00",
  "last_revision_date": "2009-08-12T00:00:00",
  "links": [],
  "reference": "CERTA-2009-AVI-324",
  "revisions": [
    {
      "description": "version initiale.",
      "revision_date": "2009-08-12T00:00:00.000000"
    }
  ],
  "risks": [
    {
      "description": "D\u00e9ni de service \u00e0 distance"
    }
  ],
  "summary": "Une vuln\u00e9rabilit\u00e9 dans ASP.NET permet \u00e0 un utilisateur malveillant de\nr\u00e9aliser un d\u00e9ni de service \u00e0 distance.\n",
  "title": "Vuln\u00e9rabilit\u00e9 dans ASP.NET de Microsoft Windows",
  "vendor_advisories": [
    {
      "published_at": null,
      "title": "Bulletin de s\u00e9curit\u00e9 Microsoft MS09-036 du 11 ao\u00fbt 2009",
      "url": "http://www.microsoft.com/technet/security/Bulletin/MS09-036.mspx"
    }
  ]
}



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.