CERTFR-2022-AVI-061
Vulnerability from certfr_avis - Published: 2022-01-20 - Updated: 2022-01-20
De multiples vulnérabilités ont été découvertes dans TrendMicro Deep Security Agent. Elles permettent à un attaquant de provoquer une exécution de code arbitraire, une atteinte à la confidentialité des données et une élévation de privilèges.
Solution
Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation).
None| Vendor | Product | Description | ||
|---|---|---|---|---|
| Trend Micro | Deep Security Agent | TrendMicro Deep Security Agent versions 11.x antérieures à 11.0 Update 28 | ||
| Trend Micro | Deep Security Agent | TrendMicro Deep Security Agent versions 20.x antérieures à 20.0.0-3445 | ||
| Trend Micro | Deep Security Agent | TrendMicro Deep Security Agent versions 12.x antérieures à 12.0 Update 22 | ||
| Trend Micro | Deep Security Agent | TrendMicro Deep Security Agent versions 10.x antérieures à 10.0 Update 32 |
| Title | Publication Time | Tags | |||
|---|---|---|---|---|---|
|
|||||
{
"$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
"affected_systems": [
{
"description": "TrendMicro Deep Security Agent versions 11.x ant\u00e9rieures \u00e0 11.0 Update 28",
"product": {
"name": "Deep Security Agent",
"vendor": {
"name": "Trend Micro",
"scada": false
}
}
},
{
"description": "TrendMicro Deep Security Agent versions 20.x ant\u00e9rieures \u00e0 20.0.0-3445",
"product": {
"name": "Deep Security Agent",
"vendor": {
"name": "Trend Micro",
"scada": false
}
}
},
{
"description": "TrendMicro Deep Security Agent versions 12.x ant\u00e9rieures \u00e0 12.0 Update 22",
"product": {
"name": "Deep Security Agent",
"vendor": {
"name": "Trend Micro",
"scada": false
}
}
},
{
"description": "TrendMicro Deep Security Agent versions 10.x ant\u00e9rieures \u00e0 10.0 Update 32",
"product": {
"name": "Deep Security Agent",
"vendor": {
"name": "Trend Micro",
"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-2022-23120",
"url": "https://www.cve.org/CVERecord?id=CVE-2022-23120"
},
{
"name": "CVE-2022-23119",
"url": "https://www.cve.org/CVERecord?id=CVE-2022-23119"
}
],
"initial_release_date": "2022-01-20T00:00:00",
"last_revision_date": "2022-01-20T00:00:00",
"links": [],
"reference": "CERTFR-2022-AVI-061",
"revisions": [
{
"description": "Version initiale",
"revision_date": "2022-01-20T00:00:00.000000"
}
],
"risks": [
{
"description": "Ex\u00e9cution de code arbitraire"
},
{
"description": "Atteinte \u00e0 la confidentialit\u00e9 des donn\u00e9es"
},
{
"description": "\u00c9l\u00e9vation de privil\u00e8ges"
}
],
"summary": "De multiples vuln\u00e9rabilit\u00e9s ont \u00e9t\u00e9 d\u00e9couvertes dans TrendMicro Deep\nSecurity Agent. Elles permettent \u00e0 un attaquant de provoquer une\nex\u00e9cution de code arbitraire, une atteinte \u00e0 la confidentialit\u00e9 des\ndonn\u00e9es et une \u00e9l\u00e9vation de privil\u00e8ges.\n",
"title": "Multiples vuln\u00e9rabilit\u00e9s dans TrendMicro Deep Security Agent",
"vendor_advisories": [
{
"published_at": null,
"title": "Bulletin de s\u00e9curit\u00e9 TrendMicro 000290104 du 19 janvier 2022",
"url": "https://success.trendmicro.com/solution/000290104"
}
]
}
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.
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
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…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
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.