CERTA-2012-AVI-658
Vulnerability from certfr_avis

De multiples vulnérabilités ont été corrigées dans IBM Tivoli Monitoring. Certaines d'entre elles permettent à un attaquant d'exécuter du code arbitraire à distance et de contourner la politique de sécurité de la "sandbox" au moyen de fichiers .jar spécialement conçus.

Solution

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 Tivoli Monitoring IBM Tivoli Monitoring de la version 6.2.2 à la version 6.2.2 Fix Pack 09
IBM Tivoli Monitoring IBM Tivoli Monitoring de la version 6.2.0 à la version 6.2.0 Fix Pack 03
IBM Tivoli Monitoring IBM Tivoli Monitoring de la version 6.2.3 à la version 6.2.3 Fix Pack 02
IBM Tivoli Monitoring IBM Tivoli Monitoring de la version 6.2.1 à la version 6.2.1 Fix Pack 04
References

Show details on source website

To clipboard 

{
  "$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
  "affected_systems": [
    {
      "description": "IBM Tivoli Monitoring de la version 6.2.2 \u00e0 la version 6.2.2 Fix Pack 09",
      "product": {
        "name": "Tivoli Monitoring",
        "vendor": {
          "name": "IBM",
          "scada": false
        }
      }
    },
    {
      "description": "IBM Tivoli Monitoring de la version 6.2.0 \u00e0 la version 6.2.0 Fix Pack 03",
      "product": {
        "name": "Tivoli Monitoring",
        "vendor": {
          "name": "IBM",
          "scada": false
        }
      }
    },
    {
      "description": "IBM Tivoli Monitoring de la version 6.2.3 \u00e0 la version 6.2.3 Fix Pack 02",
      "product": {
        "name": "Tivoli Monitoring",
        "vendor": {
          "name": "IBM",
          "scada": false
        }
      }
    },
    {
      "description": "IBM Tivoli Monitoring de la version 6.2.1 \u00e0 la version 6.2.1 Fix Pack 04",
      "product": {
        "name": "Tivoli Monitoring",
        "vendor": {
          "name": "IBM",
          "scada": false
        }
      }
    }
  ],
  "affected_systems_content": null,
  "content": "## 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-2012-4823",
      "url": "https://www.cve.org/CVERecord?id=CVE-2012-4823"
    },
    {
      "name": "CVE-2012-4820",
      "url": "https://www.cve.org/CVERecord?id=CVE-2012-4820"
    },
    {
      "name": "CVE-2012-4821",
      "url": "https://www.cve.org/CVERecord?id=CVE-2012-4821"
    },
    {
      "name": "CVE-2012-4822",
      "url": "https://www.cve.org/CVERecord?id=CVE-2012-4822"
    }
  ],
  "initial_release_date": "2012-11-16T00:00:00",
  "last_revision_date": "2012-11-16T00:00:00",
  "links": [],
  "reference": "CERTA-2012-AVI-658",
  "revisions": [
    {
      "description": "version initiale.",
      "revision_date": "2012-11-16T00:00:00.000000"
    }
  ],
  "risks": [
    {
      "description": "Ex\u00e9cution de code arbitraire \u00e0 distance"
    },
    {
      "description": "Contournement de la politique de s\u00e9curit\u00e9"
    }
  ],
  "summary": "De multiples vuln\u00e9rabilit\u00e9s ont \u00e9t\u00e9 corrig\u00e9es dans \u003cspan\nclass=\"textit\"\u003eIBM Tivoli Monitoring\u003c/span\u003e. Certaines d\u0027entre elles\npermettent \u00e0 un attaquant d\u0027ex\u00e9cuter du code arbitraire \u00e0 distance et de\ncontourner la politique de s\u00e9curit\u00e9 de la \"sandbox\" au moyen de fichiers\n\u003cspan class=\"textit\"\u003e.jar\u003c/span\u003e sp\u00e9cialement con\u00e7us.\n",
  "title": "Multiples vuln\u00e9rabilit\u00e9s dans IBM Tivoli Monitoring",
  "vendor_advisories": [
    {
      "published_at": null,
      "title": "Bulletin de s\u00e9curit\u00e9 IBM swg21616490 du 15 novembre 2012",
      "url": "http://www-01.ibm.com/support/docview.wss?uid=swg24033800"
    }
  ]
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.