cnvd-2017-04911
Vulnerability from cnvd

Title: PCRE '_pcre32_xclass'函数拒绝服务漏洞

Description:

PCRE(Perl Compatible Regular Expressions)是软件开发者Philip Hazel所研发的一个使用C语言编写的开源正则表达式函数库。

PCRE 8.40版本中libpcre1的pcre_xclass.c文件中的_pcre32_xclass函数存在安全漏洞。远程攻击者可利用该漏洞造成拒绝服务(无效的内存读取)。

Severity:

Formal description:

目前没有详细的解决方案提供: http://www.pcre.org/

Reference: https://blogs.gentoo.org/ago/2017/03/20/libpcre-invalid-memory-read-in-_pcre32_xclass-pcre_xclass-c/ http://www.securityfocus.com/bid/97067 https://nvd.nist.gov/vuln/detail/CVE-2017-7244

Impacted products
Name
PCRE PCRE 8.40
Show details on source website


{
  "bids": {
    "bid": {
      "bidNumber": "97067"
    }
  },
  "cves": {
    "cve": {
      "cveNumber": "CVE-2017-7244"
    }
  },
  "description": "PCRE\uff08Perl Compatible Regular Expressions\uff09\u662f\u8f6f\u4ef6\u5f00\u53d1\u8005Philip Hazel\u6240\u7814\u53d1\u7684\u4e00\u4e2a\u4f7f\u7528C\u8bed\u8a00\u7f16\u5199\u7684\u5f00\u6e90\u6b63\u5219\u8868\u8fbe\u5f0f\u51fd\u6570\u5e93\u3002\r\n\r\nPCRE 8.40\u7248\u672c\u4e2dlibpcre1\u7684pcre_xclass.c\u6587\u4ef6\u4e2d\u7684_pcre32_xclass\u51fd\u6570\u5b58\u5728\u5b89\u5168\u6f0f\u6d1e\u3002\u8fdc\u7a0b\u653b\u51fb\u8005\u53ef\u5229\u7528\u8be5\u6f0f\u6d1e\u9020\u6210\u62d2\u7edd\u670d\u52a1\uff08\u65e0\u6548\u7684\u5185\u5b58\u8bfb\u53d6\uff09\u3002",
  "discovererName": "Agostino Sarubbo of Gentoo",
  "formalWay": "\u76ee\u524d\u6ca1\u6709\u8be6\u7ec6\u7684\u89e3\u51b3\u65b9\u6848\u63d0\u4f9b\uff1a\r\nhttp://www.pcre.org/",
  "isEvent": "\u901a\u7528\u8f6f\u786c\u4ef6\u6f0f\u6d1e",
  "number": "CNVD-2017-04911",
  "openTime": "2017-04-21",
  "products": {
    "product": "PCRE PCRE 8.40"
  },
  "referenceLink": "https://blogs.gentoo.org/ago/2017/03/20/libpcre-invalid-memory-read-in-_pcre32_xclass-pcre_xclass-c/\r\nhttp://www.securityfocus.com/bid/97067\r\nhttps://nvd.nist.gov/vuln/detail/CVE-2017-7244",
  "serverity": "\u4e2d",
  "submitTime": "2017-03-28",
  "title": "PCRE \u0027_pcre32_xclass\u0027\u51fd\u6570\u62d2\u7edd\u670d\u52a1\u6f0f\u6d1e"
}


Log in or create an account to share your comment.




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.


Loading…