CNVD-2025-02736

Vulnerability from cnvd - Published: 2025-02-12
VLAI
Title
Hitachi Energy RTU500 series CMU Firmware存在未明漏洞
Description
RTU500是日本日立制作所(Hitachi)公司的一系列工控组件,主要用于工业控制系统。 Hitachi Energy RTU500 series CMU Firmware存在安全漏洞,该漏洞源于stb语言文件处理中存在问题,攻击者可利用漏洞在授权用户上传特制的stb语言文件时,强制将诊断文本显示为空字符串。
Severity
中
Patch Name
Hitachi Energy RTU500 series CMU Firmware存在未明漏洞的补丁
Patch Description
RTU500是日本日立制作所(Hitachi)公司的一系列工控组件,主要用于工业控制系统。 Hitachi Energy RTU500 series CMU Firmware存在安全漏洞,该漏洞源于stb语言文件处理中存在问题,攻击者可利用漏洞在授权用户上传特制的stb语言文件时,强制将诊断文本显示为空字符串。目前,供应商发布了安全公告及相关补丁信息,修复了此漏洞。
Formal description

厂商已发布补丁修复漏洞,请广大用户及时下载更新: https://publisher.hitachienergy.com/preview?DocumentId=8DBD000190&languageCode=en&Preview=true

Reference
https://publisher.hitachienergy.com/preview?DocumentId=8DBD000190&languageCode=en&Preview=true
Impacted products
Name
['Hitachi Energy RTU500 series CMU Firmware >=13.4.1,<13.4.4', 'Hitachi Energy RTU500 series CMU Firmware >=12.2.1,<=12.2.11', 'Hitachi Energy RTU500 series CMU Firmware >=12.4.1,<=12.4.11', 'Hitachi Energy RTU500 series CMU Firmware >=12.6.1,<=12.6.9', 'Hitachi Energy RTU500 series CMU Firmware >=12.7.1,<=12.7.6', 'Hitachi Energy RTU500 series CMU Firmware >=13.2.1,<=13.2.6', 'Hitachi Energy RTU500 series CMU Firmware >=13.5.1,<=13.5.3']
Show details on source website

{
  "cves": {
    "cve": {
      "cveNumber": "CVE-2024-1532",
      "cveUrl": "https://nvd.nist.gov/vuln/detail/CVE-2024-1532"
    }
  },
  "description": "RTU500\u662f\u65e5\u672c\u65e5\u7acb\u5236\u4f5c\u6240\uff08Hitachi\uff09\u516c\u53f8\u7684\u4e00\u7cfb\u5217\u5de5\u63a7\u7ec4\u4ef6\uff0c\u4e3b\u8981\u7528\u4e8e\u5de5\u4e1a\u63a7\u5236\u7cfb\u7edf\u3002\n\nHitachi Energy RTU500 series CMU Firmware\u5b58\u5728\u5b89\u5168\u6f0f\u6d1e\uff0c\u8be5\u6f0f\u6d1e\u6e90\u4e8estb\u8bed\u8a00\u6587\u4ef6\u5904\u7406\u4e2d\u5b58\u5728\u95ee\u9898\uff0c\u653b\u51fb\u8005\u53ef\u5229\u7528\u6f0f\u6d1e\u5728\u6388\u6743\u7528\u6237\u4e0a\u4f20\u7279\u5236\u7684stb\u8bed\u8a00\u6587\u4ef6\u65f6\uff0c\u5f3a\u5236\u5c06\u8bca\u65ad\u6587\u672c\u663e\u793a\u4e3a\u7a7a\u5b57\u7b26\u4e32\u3002",
  "formalWay": "\u5382\u5546\u5df2\u53d1\u5e03\u8865\u4e01\u4fee\u590d\u6f0f\u6d1e\uff0c\u8bf7\u5e7f\u5927\u7528\u6237\u53ca\u65f6\u4e0b\u8f7d\u66f4\u65b0\uff1a\r\nhttps://publisher.hitachienergy.com/preview?DocumentId=8DBD000190\u0026languageCode=en\u0026Preview=true",
  "isEvent": "\u901a\u7528\u8f6f\u786c\u4ef6\u6f0f\u6d1e",
  "number": "CNVD-2025-02736",
  "openTime": "2025-02-12",
  "patchDescription": "RTU500\u662f\u65e5\u672c\u65e5\u7acb\u5236\u4f5c\u6240\uff08Hitachi\uff09\u516c\u53f8\u7684\u4e00\u7cfb\u5217\u5de5\u63a7\u7ec4\u4ef6\uff0c\u4e3b\u8981\u7528\u4e8e\u5de5\u4e1a\u63a7\u5236\u7cfb\u7edf\u3002\r\n\r\nHitachi Energy RTU500 series CMU Firmware\u5b58\u5728\u5b89\u5168\u6f0f\u6d1e\uff0c\u8be5\u6f0f\u6d1e\u6e90\u4e8estb\u8bed\u8a00\u6587\u4ef6\u5904\u7406\u4e2d\u5b58\u5728\u95ee\u9898\uff0c\u653b\u51fb\u8005\u53ef\u5229\u7528\u6f0f\u6d1e\u5728\u6388\u6743\u7528\u6237\u4e0a\u4f20\u7279\u5236\u7684stb\u8bed\u8a00\u6587\u4ef6\u65f6\uff0c\u5f3a\u5236\u5c06\u8bca\u65ad\u6587\u672c\u663e\u793a\u4e3a\u7a7a\u5b57\u7b26\u4e32\u3002\u76ee\u524d\uff0c\u4f9b\u5e94\u5546\u53d1\u5e03\u4e86\u5b89\u5168\u516c\u544a\u53ca\u76f8\u5173\u8865\u4e01\u4fe1\u606f\uff0c\u4fee\u590d\u4e86\u6b64\u6f0f\u6d1e\u3002",
  "patchName": "Hitachi Energy RTU500 series CMU Firmware\u5b58\u5728\u672a\u660e\u6f0f\u6d1e\u7684\u8865\u4e01",
  "products": {
    "product": [
      "Hitachi Energy RTU500 series CMU Firmware \u003e=13.4.1\uff0c\u003c13.4.4",
      "Hitachi Energy RTU500 series CMU Firmware \u003e=12.2.1\uff0c\u003c=12.2.11",
      "Hitachi Energy RTU500 series CMU Firmware \u003e=12.4.1\uff0c\u003c=12.4.11",
      "Hitachi Energy RTU500 series CMU Firmware \u003e=12.6.1\uff0c\u003c=12.6.9",
      "Hitachi Energy RTU500 series CMU Firmware \u003e=12.7.1\uff0c\u003c=12.7.6",
      "Hitachi Energy RTU500 series CMU Firmware \u003e=13.2.1\uff0c\u003c=13.2.6",
      "Hitachi Energy RTU500 series CMU Firmware \u003e=13.5.1\uff0c\u003c=13.5.3"
    ]
  },
  "referenceLink": "https://publisher.hitachienergy.com/preview?DocumentId=8DBD000190\u0026languageCode=en\u0026Preview=true",
  "serverity": "\u4e2d",
  "submitTime": "2024-03-29",
  "title": "Hitachi Energy RTU500 series CMU Firmware\u5b58\u5728\u672a\u660e\u6f0f\u6d1e"
}



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.