CERTA-2006-AVI-451

Vulnerability from certfr_avis - Published: 2006-10-12 - Updated: 2006-10-12

De multiples vulnérabilité ont été découvertes dans IBM Websphere. L'exploitation de ces vulnérabilités conduit au contournement de la politique de sécurité et/ou à la divulgation d'informations sensibles.

Description

Trois vulnérabilités ont été découvertes dans IBM Webspher Application Server :

  • la première découle d'une erreur présente au niveau du traitement de certaines requêtes HTTP. L'exploitation de cette vulnérabilité conduit à l'accès au code source d'une page JSP ;
  • la deuxième découle d'une erreure inconnue dans WSN. Un utilisateur mal intentionné peut exploiter cette vulnérabilité afin d'obtenir un accès à la machine vulnérable sans fournir d'identifiant ;
  • la troisième permet à un utilisateur mal intentionné d'accéder de manière illégitime à des données.

Solution

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

IBM WebSphere Application Server 6.1.x

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\u003eIBM WebSphere Application Server 6.1.x\u003c/p\u003e",
  "content": "## Description\n\nTrois vuln\u00e9rabilit\u00e9s ont \u00e9t\u00e9 d\u00e9couvertes dans IBM Webspher Application\nServer :\n\n-   la premi\u00e8re d\u00e9coule d\u0027une erreur pr\u00e9sente au niveau du traitement de\n    certaines requ\u00eates HTTP. L\u0027exploitation de cette vuln\u00e9rabilit\u00e9\n    conduit \u00e0 l\u0027acc\u00e8s au code source d\u0027une page JSP ;\n-   la deuxi\u00e8me d\u00e9coule d\u0027une erreure inconnue dans WSN. Un utilisateur\n    mal intentionn\u00e9 peut exploiter cette vuln\u00e9rabilit\u00e9 afin d\u0027obtenir un\n    acc\u00e8s \u00e0 la machine vuln\u00e9rable sans fournir d\u0027identifiant ;\n-   la troisi\u00e8me permet \u00e0 un utilisateur mal intentionn\u00e9 d\u0027acc\u00e9der de\n    mani\u00e8re ill\u00e9gitime \u00e0 des donn\u00e9es.\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-4223",
      "url": "https://www.cve.org/CVERecord?id=CVE-2006-4223"
    }
  ],
  "initial_release_date": "2006-10-12T00:00:00",
  "last_revision_date": "2006-10-12T00:00:00",
  "links": [],
  "reference": "CERTA-2006-AVI-451",
  "revisions": [
    {
      "description": "version initiale.",
      "revision_date": "2006-10-12T00:00:00.000000"
    }
  ],
  "risks": [
    {
      "description": "Contournement de la politique de s\u00e9curit\u00e9"
    },
    {
      "description": "Atteinte \u00e0 la confidentialit\u00e9 des donn\u00e9es"
    }
  ],
  "summary": "De multiples vuln\u00e9rabilit\u00e9 ont \u00e9t\u00e9 d\u00e9couvertes dans IBM Websphere.\nL\u0027exploitation de ces vuln\u00e9rabilit\u00e9s conduit au contournement de la\npolitique de s\u00e9curit\u00e9 et/ou \u00e0 la divulgation d\u0027informations sensibles.\n",
  "title": "Multiples vuln\u00e9rabilit\u00e9s dans IBM Websphere",
  "vendor_advisories": [
    {
      "published_at": null,
      "title": "Bulletin de mise \u00e0 jour IBM Websphere",
      "url": "http://www-1.ibm.com/support/docview.wss?rs=180\u0026uid=swg24013142"
    }
  ]
}



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.