CERTA-2007-AVI-421

Vulnerability from certfr_avis - Published: - Updated:

Plusieurs vulnérabilités des serveurs IBM HTTP et WebSphere permettent à un utilisateur malveillant de réaliser un déni de service, local ou à distance, ou de réaliser de l'injection de code indirecte.

Description

Plusieurs vulnérabilités affectent les produits IBM WebSphere :

  • une erreur dans la gestion du jeu de caratères utilisé est présente dans le module mod_status . Elle permet à un utilisateur malveillant de réaliser, dans des circonstances particulières, de l'injection de code indirecte ;
  • une erreur de traitement par le module mod_cache des requêtes malformées permet à un utilisateur malveillant de réaliser un déni de service à distance, dans certaines circonstances ;
  • un manque de vérification de la nature des processus fils du serveur web permet à un utilisateur malveillant local de réaliser un déni de service ;
  • une erreur du module mod_proxy permet à un utilisateur malintentionné de provoquer un arrêt inopiné (crash) du serveur, à distance.

Solution

Le correctif APAR PK52702 corrige ces problèmes. Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation).

None
Impacted products
Vendor Product Description
IBM WebSphere IBM HTTP Server 6.1.x.
IBM WebSphere IBM WebSphere Application Server 6.1.x ;
References

Show details on source website
To clipboard 

{
  "$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
  "affected_systems": [
    {
      "description": "IBM HTTP Server 6.1.x.",
      "product": {
        "name": "WebSphere",
        "vendor": {
          "name": "IBM",
          "scada": false
        }
      }
    },
    {
      "description": "IBM WebSphere Application Server 6.1.x ;",
      "product": {
        "name": "WebSphere",
        "vendor": {
          "name": "IBM",
          "scada": false
        }
      }
    }
  ],
  "affected_systems_content": null,
  "content": "## Description\n\nPlusieurs vuln\u00e9rabilit\u00e9s affectent les produits IBM WebSphere :\n\n-   une erreur dans la gestion du jeu de carat\u00e8res utilis\u00e9 est pr\u00e9sente\n    dans le module mod_status . Elle permet \u00e0 un utilisateur malveillant\n    de r\u00e9aliser, dans des circonstances particuli\u00e8res, de l\u0027injection de\n    code indirecte ;\n-   une erreur de traitement par le module mod_cache des requ\u00eates\n    malform\u00e9es permet \u00e0 un utilisateur malveillant de r\u00e9aliser un d\u00e9ni\n    de service \u00e0 distance, dans certaines circonstances ;\n-   un manque de v\u00e9rification de la nature des processus fils du serveur\n    web permet \u00e0 un utilisateur malveillant local de r\u00e9aliser un d\u00e9ni de\n    service ;\n-   une erreur du module mod_proxy permet \u00e0 un utilisateur\n    malintentionn\u00e9 de provoquer un arr\u00eat inopin\u00e9 (crash) du serveur, \u00e0\n    distance.\n\n## Solution\n\nLe correctif APAR PK52702 corrige ces probl\u00e8mes. Se r\u00e9f\u00e9rer au bulletin\nde s\u00e9curit\u00e9 de l\u0027\u00e9diteur pour l\u0027obtention des correctifs (cf. section\nDocumentation).\n",
  "cves": [
    {
      "name": "CVE-2007-3847",
      "url": "https://www.cve.org/CVERecord?id=CVE-2007-3847"
    },
    {
      "name": "CVE-2007-3304",
      "url": "https://www.cve.org/CVERecord?id=CVE-2007-3304"
    },
    {
      "name": "CVE-2007-1863",
      "url": "https://www.cve.org/CVERecord?id=CVE-2007-1863"
    },
    {
      "name": "CVE-2006-5752",
      "url": "https://www.cve.org/CVERecord?id=CVE-2006-5752"
    }
  ],
  "links": [
    {
      "title": "Bulletin de s\u00e9curit\u00e9 IBM swg1PK50467 du 04 septembre 2007 :",
      "url": "http://www-1.ibm.com/support/docview.wss?uid=swg1PK50467"
    },
    {
      "title": "Bulletin de s\u00e9curit\u00e9 IBM swg1PK49295 du 16 ao\u00fbt 2007 :",
      "url": "http://www-1.ibm.com/support/docview.wss?uid=swg1PK49295"
    },
    {
      "title": "Bulletin de s\u00e9curit\u00e9 IBM swg1PK52702 du 26 septembre 2007 :",
      "url": "http://www-1.ibm.com/support/docview.wss?uid=swg1PK52702"
    },
    {
      "title": "Bulletin de s\u00e9curit\u00e9 IBM swg1PK50469 du 04 septembre 2007 :",
      "url": "http://www-1.ibm.com/support/docview.wss?uid=swg1PK50469"
    },
    {
      "title": "Bulletin de s\u00e9curit\u00e9 IBM swg1PK49355 du 16 ao\u00fbt 2007 :",
      "url": "http://www-1.ibm.com/support/docview.wss?uid=swg1PK49355"
    }
  ],
  "reference": "CERTA-2007-AVI-421",
  "revisions": [
    {
      "description": "version initiale.",
      "revision_date": "2007-09-28T00:00:00.000000"
    }
  ],
  "risks": [
    {
      "description": "D\u00e9ni de service \u00e0 distance"
    },
    {
      "description": "Injection de code indirecte \u00e0 distance (XSS)"
    },
    {
      "description": "Ex\u00e9cution de code arbitraire \u00e0 distance"
    }
  ],
  "summary": "Plusieurs vuln\u00e9rabilit\u00e9s des serveurs IBM HTTP et WebSphere permettent \u00e0\nun utilisateur malveillant de r\u00e9aliser un d\u00e9ni de service, local ou \u00e0\ndistance, ou de r\u00e9aliser de l\u0027injection de code indirecte.\n",
  "title": "Multiples vuln\u00e9rabilit\u00e9s de WebSphere",
  "vendor_advisories": [
    {
      "published_at": null,
      "title": "Bulletins de s\u00e9curit\u00e9 d\u0027IBM",
      "url": null
    }
  ]
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




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.

Loading timeline…




    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.