CERTA-2011-AVI-398

Vulnerability from certfr_avis - Published: - Updated:

ArcSight Connector Appliance est vulnérable à une injection de code indirecte à distance.

Description

Le module Windows Event Log SmartConnector inclus dans ArcSight Connector Appliance est vulnérable à une injection de code indirecte à distance lors de la génération de rapport.

Solution

Contacter l'éditeur pour l'obtention du correctif permettant de mettre à jour en version 6.1.

HP ArcSight Connector Appliance version 6.0.0.60023.2.

Impacted products
Vendor Product Description

Show details on source website

{
  "$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
  "affected_systems": [],
  "affected_systems_content": "\u003cP\u003eHP ArcSight Connector Appliance version 6.0.0.60023.2.\u003c/P\u003e",
  "content": "## Description\n\nLe module Windows Event Log SmartConnector inclus dans ArcSight\nConnector Appliance est vuln\u00e9rable \u00e0 une injection de code indirecte \u00e0\ndistance lors de la g\u00e9n\u00e9ration de rapport.\n\n## Solution\n\nContacter l\u0027\u00e9diteur pour l\u0027obtention du correctif permettant de mettre \u00e0\njour en version 6.1.\n",
  "cves": [
    {
      "name": "CVE-2011-0770",
      "url": "https://www.cve.org/CVERecord?id=CVE-2011-0770"
    }
  ],
  "links": [
    {
      "title": "Note de vuln\u00e9rabilit\u00e9 de l\u0027US-CERT VU#122054 du 15 juillet    2011 :",
      "url": "http://www.kb.cert.org/vuls/id/122054"
    }
  ],
  "reference": "CERTA-2011-AVI-398",
  "revisions": [
    {
      "description": "version initiale.",
      "revision_date": "2011-07-19T00:00:00.000000"
    }
  ],
  "risks": [
    {
      "description": "Injection de code indirecte \u00e0 distance"
    }
  ],
  "summary": "ArcSight Connector Appliance est vuln\u00e9rable \u00e0 une injection de code\nindirecte \u00e0 distance.\n",
  "title": "Vuln\u00e9rabilit\u00e9 dans ArcSight Connector Appliance",
  "vendor_advisories": [
    {
      "published_at": null,
      "title": "Note de vuln\u00e9rabilit\u00e9 de l\u0027US-CERT VU#122054 du 15 juillet 2011",
      "url": null
    }
  ]
}



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.