CERTA-2007-AVI-210

Vulnerability from certfr_avis - Published: 2007-05-09 - Updated: 2007-05-09

Des vulnérabilités sur Trend Micro ServerProtect permettent à une personne malintentionnée distante d'exécuter du code arbitraire.

Description

Des vulnérabilités de type débordement de mémoire ont été identifiées sur Trend Micro ServerProtect. Les modules concernés sont stcommon.dll, stcommon.dll, eng50.dll, earthagent.exe, et AgRpcCln.dll. Ces fichiers appellent des fonctions ne gérant pas correctement certains messages RPC spécialement construits. Un attaquant exploitant l'une de ces vulnérabilités pourrait exécuter du code arbitraire à distance.

Solution

Les mises à jour Security Patch 2 et Security Patch 3 de l'éditeur corrigent ces vulnérabilités.

Trend Micro ServerProtect versions 5.58 et antérieures sur Microsoft Windows.

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\u003eTrend Micro ServerProtect versions 5.58 et ant\u00e9rieures sur  Microsoft Windows.\u003c/P\u003e",
  "content": "## Description\n\nDes vuln\u00e9rabilit\u00e9s de type d\u00e9bordement de m\u00e9moire ont \u00e9t\u00e9 identifi\u00e9es\nsur Trend Micro ServerProtect. Les modules concern\u00e9s sont stcommon.dll,\nstcommon.dll, eng50.dll, earthagent.exe, et AgRpcCln.dll. Ces fichiers\nappellent des fonctions ne g\u00e9rant pas correctement certains messages RPC\nsp\u00e9cialement construits. Un attaquant exploitant l\u0027une de ces\nvuln\u00e9rabilit\u00e9s pourrait ex\u00e9cuter du code arbitraire \u00e0 distance.\n\n## Solution\n\nLes mises \u00e0 jour Security Patch 2 et Security Patch 3 de l\u0027\u00e9diteur\ncorrigent ces vuln\u00e9rabilit\u00e9s.\n",
  "cves": [
    {
      "name": "CVE-2007-2508",
      "url": "https://www.cve.org/CVERecord?id=CVE-2007-2508"
    },
    {
      "name": "CVE-2007-2528",
      "url": "https://www.cve.org/CVERecord?id=CVE-2007-2528"
    }
  ],
  "initial_release_date": "2007-05-09T00:00:00",
  "last_revision_date": "2007-05-09T00:00:00",
  "links": [
    {
      "title": "R\u00e9f\u00e9rence CVE CVE-2007-2508 :",
      "url": "http://nvd.nist.gov/nvd.cfm?cvename=CVE-2007-2508"
    },
    {
      "title": "R\u00e9f\u00e9rence CVE CVE-2007-2528 :",
      "url": "http://nvd.nist.gov/nvd.cfm?cvename=CVE-2007-2528"
    },
    {
      "title": "Mises \u00e0 jour pour Trend Micro ServerProtect :",
      "url": "http://www.trendmicro.com/download_beta/product.asp?productid=17"
    }
  ],
  "reference": "CERTA-2007-AVI-210",
  "revisions": [
    {
      "description": "version initiale.",
      "revision_date": "2007-05-09T00:00:00.000000"
    }
  ],
  "risks": [
    {
      "description": "Ex\u00e9cution de code arbitraire \u00e0 distance"
    }
  ],
  "summary": "Des vuln\u00e9rabilit\u00e9s sur \u003cspan class=\"textit\"\u003eTrend Micro\nServerProtect\u003c/span\u003e permettent \u00e0 une personne malintentionn\u00e9e distante\nd\u0027ex\u00e9cuter du code arbitraire.\n",
  "title": "Vuln\u00e9rabilit\u00e9s dans Trend Micro ServerProtect",
  "vendor_advisories": [
    {
      "published_at": null,
      "title": "Mises \u00e0 jour de Trend Micro ServerProtect",
      "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.