jvndb-2022-002761
Vulnerability from jvndb
Published
2022-11-21 18:25
Modified
2024-05-31 17:43
Severity ?
Summary
Multiple vulnerabilities in Trend Micro Apex One and Apex One as a Service
Details
Trend Micro Incorporated has released security updates for Apex One and Apex One as a Service. Trend Micro Incorporated reported these vulnerabilities to JPCERT/CC to notify users of the solutions through JVN.
Impacted products
Trend Micro, Inc.Apex One
Show details on JVN DB website


{
   "@rdf:about": "https://jvndb.jvn.jp/en/contents/2022/JVNDB-2022-002761.html",
   "dc:date": "2024-05-31T17:43+09:00",
   "dcterms:issued": "2022-11-21T18:25+09:00",
   "dcterms:modified": "2024-05-31T17:43+09:00",
   description: "Trend Micro Incorporated has released security updates for Apex One and Apex One as a Service.\r\n\r\nTrend Micro Incorporated reported these vulnerabilities to JPCERT/CC to notify users of the solutions through JVN.",
   link: "https://jvndb.jvn.jp/en/contents/2022/JVNDB-2022-002761.html",
   "sec:cpe": {
      "#text": "cpe:/a:trendmicro:apex_one",
      "@product": "Apex One",
      "@vendor": "Trend Micro, Inc.",
      "@version": "2.2",
   },
   "sec:cvss": {
      "@score": "7.8",
      "@severity": "High",
      "@type": "Base",
      "@vector": "CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
      "@version": "3.0",
   },
   "sec:identifier": "JVNDB-2022-002761",
   "sec:references": [
      {
         "#text": "https://jvn.jp/en/vu/JVNVU90082799",
         "@id": "JVNVU#90082799",
         "@source": "JVN",
      },
      {
         "#text": "http://jvn.jp/en/vu/JVNVU91848962/index.html",
         "@id": "JVNVU#91848962",
         "@source": "JVN",
      },
      {
         "#text": "https://www.cve.org/CVERecord?id=CVE-2022-44647",
         "@id": "CVE-2022-44647",
         "@source": "CVE",
      },
      {
         "#text": "https://www.cve.org/CVERecord?id=CVE-2022-44648",
         "@id": "CVE-2022-44648",
         "@source": "CVE",
      },
      {
         "#text": "https://www.cve.org/CVERecord?id=CVE-2022-44649",
         "@id": "CVE-2022-44649",
         "@source": "CVE",
      },
      {
         "#text": "https://www.cve.org/CVERecord?id=CVE-2022-44650",
         "@id": "CVE-2022-44650",
         "@source": "CVE",
      },
      {
         "#text": "https://www.cve.org/CVERecord?id=CVE-2022-44651",
         "@id": "CVE-2022-44651",
         "@source": "CVE",
      },
      {
         "#text": "https://www.cve.org/CVERecord?id=CVE-2022-44652",
         "@id": "CVE-2022-44652",
         "@source": "CVE",
      },
      {
         "#text": "https://www.cve.org/CVERecord?id=CVE-2022-44653",
         "@id": "CVE-2022-44653",
         "@source": "CVE",
      },
      {
         "#text": "https://www.cve.org/CVERecord?id=CVE-2022-44654",
         "@id": "CVE-2022-44654",
         "@source": "CVE",
      },
      {
         "#text": "https://nvd.nist.gov/vuln/detail/CVE-2022-44647",
         "@id": "CVE-2022-44647",
         "@source": "NVD",
      },
      {
         "#text": "https://nvd.nist.gov/vuln/detail/CVE-2022-44648",
         "@id": "CVE-2022-44648",
         "@source": "NVD",
      },
      {
         "#text": "https://nvd.nist.gov/vuln/detail/CVE-2022-44649",
         "@id": "CVE-2022-44649",
         "@source": "NVD",
      },
      {
         "#text": "https://nvd.nist.gov/vuln/detail/CVE-2022-44650",
         "@id": "CVE-2022-44650",
         "@source": "NVD",
      },
      {
         "#text": "https://nvd.nist.gov/vuln/detail/CVE-2022-44651",
         "@id": "CVE-2022-44651",
         "@source": "NVD",
      },
      {
         "#text": "https://nvd.nist.gov/vuln/detail/CVE-2022-44652",
         "@id": "CVE-2022-44652",
         "@source": "NVD",
      },
      {
         "#text": "https://nvd.nist.gov/vuln/detail/CVE-2022-44653",
         "@id": "CVE-2022-44653",
         "@source": "NVD",
      },
      {
         "#text": "https://nvd.nist.gov/vuln/detail/CVE-2022-44654",
         "@id": "CVE-2022-44654",
         "@source": "NVD",
      },
      {
         "#text": "https://cwe.mitre.org/data/definitions/125.html",
         "@id": "CWE-125",
         "@title": "Out-of-bounds Read(CWE-125)",
      },
      {
         "#text": "https://cwe.mitre.org/data/definitions/787.html",
         "@id": "CWE-787",
         "@title": "Out-of-bounds Write(CWE-787)",
      },
      {
         "#text": "https://cwe.mitre.org/data/definitions/367.html",
         "@id": "CWE-367",
         "@title": "Time-of-check Time-of-use (TOCTOU) Race Condition(CWE-367)",
      },
      {
         "#text": "https://cwe.mitre.org/data/definitions/755.html",
         "@id": "CWE-755",
         "@title": "Improper Handling of Exceptional Conditions(CWE-755)",
      },
      {
         "#text": "https://www.ipa.go.jp/en/security/vulnerabilities/cwe.html",
         "@id": "CWE-22",
         "@title": "Path Traversal(CWE-22)",
      },
      {
         "#text": "https://www.ipa.go.jp/en/security/vulnerabilities/cwe.html",
         "@id": "CWE-Other",
         "@title": "No Mapping(CWE-Other)",
      },
   ],
   title: "Multiple vulnerabilities in Trend Micro Apex One and Apex One as a Service",
}


Log in or create an account to share your comment.

Security Advisory comment format.

This schema specifies the format of a comment related to a security advisory.

UUIDv4 of the comment
UUIDv4 of the Vulnerability-Lookup instance
When the comment was created originally
When the comment was last updated
Title of the comment
Description of the comment
The identifier of the vulnerability (CVE ID, GHSA-ID, PYSEC ID, etc.).



Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

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.
  • 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.