CNVD-2021-22156

Vulnerability from cnvd - Published: 2021-03-25
VLAI
Title
Kentico SQL注入漏洞(CNVD-2021-22156)
Description
Kentico是一个一体化ASP.NET CMS,将Web内容管理、电子商务、在线营销及内联网完全集成在了一个平台上。 Kentico 5.5 R2 build 5.5.3996中的Blog模块存在SQL注入漏洞。攻击者可通过tagname参数利用该漏洞与后端数据库交互并访问/修改/删除存储的数据,干扰应用程序逻辑,提升其在数据库中的权限和/或可能控制数据库服务器。
Severity
高
Formal description

厂商尚未提供漏洞修复方案,请关注厂商主页更新: https://kontent.ai/

Reference
https://nvd.nist.gov/vuln/detail/CVE-2021-27581
Impacted products
Name
Kentico Kentico CMS 5.5 R2 build 5.5.3996
Show details on source website

{
  "cves": {
    "cve": {
      "cveNumber": "CVE-2021-27581",
      "cveUrl": "https://nvd.nist.gov/vuln/detail/CVE-2021-27581"
    }
  },
  "description": "Kentico\u662f\u4e00\u4e2a\u4e00\u4f53\u5316ASP.NET CMS\uff0c\u5c06Web\u5185\u5bb9\u7ba1\u7406\u3001\u7535\u5b50\u5546\u52a1\u3001\u5728\u7ebf\u8425\u9500\u53ca\u5185\u8054\u7f51\u5b8c\u5168\u96c6\u6210\u5728\u4e86\u4e00\u4e2a\u5e73\u53f0\u4e0a\u3002\n\nKentico 5.5 R2 build 5.5.3996\u4e2d\u7684Blog\u6a21\u5757\u5b58\u5728SQL\u6ce8\u5165\u6f0f\u6d1e\u3002\u653b\u51fb\u8005\u53ef\u901a\u8fc7tagname\u53c2\u6570\u5229\u7528\u8be5\u6f0f\u6d1e\u4e0e\u540e\u7aef\u6570\u636e\u5e93\u4ea4\u4e92\u5e76\u8bbf\u95ee/\u4fee\u6539/\u5220\u9664\u5b58\u50a8\u7684\u6570\u636e\uff0c\u5e72\u6270\u5e94\u7528\u7a0b\u5e8f\u903b\u8f91\uff0c\u63d0\u5347\u5176\u5728\u6570\u636e\u5e93\u4e2d\u7684\u6743\u9650\u548c/\u6216\u53ef\u80fd\u63a7\u5236\u6570\u636e\u5e93\u670d\u52a1\u5668\u3002",
  "formalWay": "\u5382\u5546\u5c1a\u672a\u63d0\u4f9b\u6f0f\u6d1e\u4fee\u590d\u65b9\u6848\uff0c\u8bf7\u5173\u6ce8\u5382\u5546\u4e3b\u9875\u66f4\u65b0\uff1a\r\nhttps://kontent.ai/",
  "isEvent": "\u901a\u7528\u8f6f\u786c\u4ef6\u6f0f\u6d1e",
  "number": "CNVD-2021-22156",
  "openTime": "2021-03-25",
  "products": {
    "product": "Kentico Kentico CMS 5.5 R2 build 5.5.3996"
  },
  "referenceLink": "https://nvd.nist.gov/vuln/detail/CVE-2021-27581",
  "serverity": "\u9ad8",
  "submitTime": "2021-03-08",
  "title": "Kentico SQL\u6ce8\u5165\u6f0f\u6d1e\uff08CNVD-2021-22156\uff09"
}



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.