CNVD-2022-56948

Vulnerability from cnvd - Published: 2022-08-15
VLAI
Title
SAP S/4HANA输入验证错误漏洞
Description
SAP S/4HANA是德国SAP公司的一个基于SAP HANA内存数据库系统的的企业资源管理软件。 SAP S/4HANA存在输入验证错误漏洞,该漏洞源于管理支票簿组件缺少输入验证,攻击者可利用该漏洞插入或编辑数据库中现有字段的值。
Severity
中
Patch Name
SAP S/4HANA输入验证错误漏洞的补丁
Patch Description
SAP S/4HANA是德国SAP公司的一个基于SAP HANA内存数据库系统的的企业资源管理软件。 SAP S/4HANA存在输入验证错误漏洞,该漏洞源于管理支票簿组件缺少输入验证,攻击者可利用该漏洞插入或编辑数据库中现有字段的值。目前,供应商发布了安全公告及相关补丁信息,修复了此漏洞。
Formal description

厂商已发布了漏洞修复程序,请及时关注更新: https://launchpad.support.sap.com/#/notes/3216161

Reference
https://www.sap.com/documents/2022/02/fa865ea4-167e-0010-bca6-c68f7e60039b.html
Impacted products
Name
['SAP S/4HANA 104', 'SAP S/4HANA 105', 'SAP S/4HANA 106', 'SAP S/4HANA 101', 'SAP S/4HANA 102', 'SAP S/4HANA 103']
Show details on source website

{
  "cves": {
    "cve": {
      "cveNumber": "CVE-2022-32248",
      "cveUrl": "https://nvd.nist.gov/vuln/detail/CVE-2022-32248"
    }
  },
  "description": "SAP S/4HANA\u662f\u5fb7\u56fdSAP\u516c\u53f8\u7684\u4e00\u4e2a\u57fa\u4e8eSAP HANA\u5185\u5b58\u6570\u636e\u5e93\u7cfb\u7edf\u7684\u7684\u4f01\u4e1a\u8d44\u6e90\u7ba1\u7406\u8f6f\u4ef6\u3002\n\nSAP S/4HANA\u5b58\u5728\u8f93\u5165\u9a8c\u8bc1\u9519\u8bef\u6f0f\u6d1e\uff0c\u8be5\u6f0f\u6d1e\u6e90\u4e8e\u7ba1\u7406\u652f\u7968\u7c3f\u7ec4\u4ef6\u7f3a\u5c11\u8f93\u5165\u9a8c\u8bc1\uff0c\u653b\u51fb\u8005\u53ef\u5229\u7528\u8be5\u6f0f\u6d1e\u63d2\u5165\u6216\u7f16\u8f91\u6570\u636e\u5e93\u4e2d\u73b0\u6709\u5b57\u6bb5\u7684\u503c\u3002",
  "formalWay": "\u5382\u5546\u5df2\u53d1\u5e03\u4e86\u6f0f\u6d1e\u4fee\u590d\u7a0b\u5e8f\uff0c\u8bf7\u53ca\u65f6\u5173\u6ce8\u66f4\u65b0\uff1a\r\nhttps://launchpad.support.sap.com/#/notes/3216161",
  "isEvent": "\u901a\u7528\u8f6f\u786c\u4ef6\u6f0f\u6d1e",
  "number": "CNVD-2022-56948",
  "openTime": "2022-08-15",
  "patchDescription": "SAP S/4HANA\u662f\u5fb7\u56fdSAP\u516c\u53f8\u7684\u4e00\u4e2a\u57fa\u4e8eSAP HANA\u5185\u5b58\u6570\u636e\u5e93\u7cfb\u7edf\u7684\u7684\u4f01\u4e1a\u8d44\u6e90\u7ba1\u7406\u8f6f\u4ef6\u3002\r\n\r\nSAP S/4HANA\u5b58\u5728\u8f93\u5165\u9a8c\u8bc1\u9519\u8bef\u6f0f\u6d1e\uff0c\u8be5\u6f0f\u6d1e\u6e90\u4e8e\u7ba1\u7406\u652f\u7968\u7c3f\u7ec4\u4ef6\u7f3a\u5c11\u8f93\u5165\u9a8c\u8bc1\uff0c\u653b\u51fb\u8005\u53ef\u5229\u7528\u8be5\u6f0f\u6d1e\u63d2\u5165\u6216\u7f16\u8f91\u6570\u636e\u5e93\u4e2d\u73b0\u6709\u5b57\u6bb5\u7684\u503c\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": "SAP S/4HANA\u8f93\u5165\u9a8c\u8bc1\u9519\u8bef\u6f0f\u6d1e\u7684\u8865\u4e01",
  "products": {
    "product": [
      "SAP S/4HANA 104",
      "SAP S/4HANA 105",
      "SAP S/4HANA 106",
      "SAP S/4HANA 101",
      "SAP S/4HANA 102",
      "SAP S/4HANA 103"
    ]
  },
  "referenceLink": "https://www.sap.com/documents/2022/02/fa865ea4-167e-0010-bca6-c68f7e60039b.html",
  "serverity": "\u4e2d",
  "submitTime": "2022-07-15",
  "title": "SAP S/4HANA\u8f93\u5165\u9a8c\u8bc1\u9519\u8bef\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.