CNVD-2020-03175

Vulnerability from cnvd - Published: 2020-01-21
VLAI
Title
Red Hat Directory Server和389 Directory Server代码问题漏洞
Description
Red Hat 389 Directory Server(前称Fedora Directory Server)和Red Hat Directory Server都是美国红帽(Red Hat)公司的产品。389 Directory Server是一款企业级的Linux目录服务器。该服务器完全支持LDAPv3规范,具有可扩展、多主复制等特点。Red Hat Directory Server是一款商业版Linux目录服务器。 Red Hat Directory Server 8版本和389 Directory Server中的‘_ger_parse_control’函数存在代码问题漏洞。该漏洞源于网络系统或产品的代码开发过程中存在设计或实现不当的问题。攻击者可利于该漏洞造成拒绝服务。
Severity
中
Patch Name
Red Hat Directory Server和389 Directory Server代码问题漏洞的补丁
Patch Description
Red Hat 389 Directory Server(前称Fedora Directory Server)和Red Hat Directory Server都是美国红帽(Red Hat)公司的产品。389 Directory Server是一款企业级的Linux目录服务器。该服务器完全支持LDAPv3规范,具有可扩展、多主复制等特点。Red Hat Directory Server是一款商业版Linux目录服务器。 Red Hat Directory Server 8版本和389 Directory Server中的‘_ger_parse_control’函数存在代码问题漏洞。该漏洞源于网络系统或产品的代码开发过程中存在设计或实现不当的问题。攻击者可利于该漏洞造成拒绝服务。目前,供应商发布了安全公告及相关补丁信息,修复了此漏洞。
Formal description

目前厂商已发布升级补丁以修复漏洞,补丁获取链接: https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2010-2222

Reference
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2010-2222
Impacted products
Name
['Red Hat Red Hat Directory Server 8', 'Red Hat Red Hat 389 Directory Server']
Show details on source website

{
  "cves": {
    "cve": {
      "cveNumber": "CVE-2010-2222",
      "cveUrl": "https://nvd.nist.gov/vuln/detail/CVE-2010-2222"
    }
  },
  "description": "Red Hat 389 Directory Server\uff08\u524d\u79f0Fedora Directory Server\uff09\u548cRed Hat Directory Server\u90fd\u662f\u7f8e\u56fd\u7ea2\u5e3d\uff08Red Hat\uff09\u516c\u53f8\u7684\u4ea7\u54c1\u3002389 Directory Server\u662f\u4e00\u6b3e\u4f01\u4e1a\u7ea7\u7684Linux\u76ee\u5f55\u670d\u52a1\u5668\u3002\u8be5\u670d\u52a1\u5668\u5b8c\u5168\u652f\u6301LDAPv3\u89c4\u8303\uff0c\u5177\u6709\u53ef\u6269\u5c55\u3001\u591a\u4e3b\u590d\u5236\u7b49\u7279\u70b9\u3002Red Hat Directory Server\u662f\u4e00\u6b3e\u5546\u4e1a\u7248Linux\u76ee\u5f55\u670d\u52a1\u5668\u3002\n\nRed Hat Directory Server 8\u7248\u672c\u548c389 Directory Server\u4e2d\u7684\u2018_ger_parse_control\u2019\u51fd\u6570\u5b58\u5728\u4ee3\u7801\u95ee\u9898\u6f0f\u6d1e\u3002\u8be5\u6f0f\u6d1e\u6e90\u4e8e\u7f51\u7edc\u7cfb\u7edf\u6216\u4ea7\u54c1\u7684\u4ee3\u7801\u5f00\u53d1\u8fc7\u7a0b\u4e2d\u5b58\u5728\u8bbe\u8ba1\u6216\u5b9e\u73b0\u4e0d\u5f53\u7684\u95ee\u9898\u3002\u653b\u51fb\u8005\u53ef\u5229\u4e8e\u8be5\u6f0f\u6d1e\u9020\u6210\u62d2\u7edd\u670d\u52a1\u3002",
  "formalWay": "\u76ee\u524d\u5382\u5546\u5df2\u53d1\u5e03\u5347\u7ea7\u8865\u4e01\u4ee5\u4fee\u590d\u6f0f\u6d1e\uff0c\u8865\u4e01\u83b7\u53d6\u94fe\u63a5\uff1a\r\nhttps://bugzilla.redhat.com/show_bug.cgi?id=CVE-2010-2222",
  "isEvent": "\u901a\u7528\u8f6f\u786c\u4ef6\u6f0f\u6d1e",
  "number": "CNVD-2020-03175",
  "openTime": "2020-01-21",
  "patchDescription": "Red Hat 389 Directory Server\uff08\u524d\u79f0Fedora Directory Server\uff09\u548cRed Hat Directory Server\u90fd\u662f\u7f8e\u56fd\u7ea2\u5e3d\uff08Red Hat\uff09\u516c\u53f8\u7684\u4ea7\u54c1\u3002389 Directory Server\u662f\u4e00\u6b3e\u4f01\u4e1a\u7ea7\u7684Linux\u76ee\u5f55\u670d\u52a1\u5668\u3002\u8be5\u670d\u52a1\u5668\u5b8c\u5168\u652f\u6301LDAPv3\u89c4\u8303\uff0c\u5177\u6709\u53ef\u6269\u5c55\u3001\u591a\u4e3b\u590d\u5236\u7b49\u7279\u70b9\u3002Red Hat Directory Server\u662f\u4e00\u6b3e\u5546\u4e1a\u7248Linux\u76ee\u5f55\u670d\u52a1\u5668\u3002\r\n\r\nRed Hat Directory Server 8\u7248\u672c\u548c389 Directory Server\u4e2d\u7684\u2018_ger_parse_control\u2019\u51fd\u6570\u5b58\u5728\u4ee3\u7801\u95ee\u9898\u6f0f\u6d1e\u3002\u8be5\u6f0f\u6d1e\u6e90\u4e8e\u7f51\u7edc\u7cfb\u7edf\u6216\u4ea7\u54c1\u7684\u4ee3\u7801\u5f00\u53d1\u8fc7\u7a0b\u4e2d\u5b58\u5728\u8bbe\u8ba1\u6216\u5b9e\u73b0\u4e0d\u5f53\u7684\u95ee\u9898\u3002\u653b\u51fb\u8005\u53ef\u5229\u4e8e\u8be5\u6f0f\u6d1e\u9020\u6210\u62d2\u7edd\u670d\u52a1\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": "Red Hat Directory Server\u548c389 Directory Server\u4ee3\u7801\u95ee\u9898\u6f0f\u6d1e\u7684\u8865\u4e01",
  "products": {
    "product": [
      "Red Hat Red Hat Directory Server 8",
      "Red Hat Red Hat 389 Directory Server"
    ]
  },
  "referenceLink": "https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2010-2222",
  "serverity": "\u4e2d",
  "submitTime": "2019-11-12",
  "title": "Red Hat Directory Server\u548c389 Directory Server\u4ee3\u7801\u95ee\u9898\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.