CNVD-2017-07084

Vulnerability from cnvd - Published: 2017-05-19
VLAI
Title
lxterminal存在未明漏洞
Description
lxterminal是一个开源的终端模拟器程序,该程序支持复制、粘贴以及标签等功能。 lxterminal 0.3.0及之前的版本中的unixsocket.c文件存在安全漏洞。本地攻击者可利用该漏洞造成拒绝服务(阻止终端启动)。
Severity
中
Patch Name
lxterminal存在未明漏洞的补丁
Patch Description
lxterminal是一个开源的终端模拟器程序,该程序支持复制、粘贴以及标签等功能。 lxterminal 0.3.0及之前的版本中的unixsocket.c文件存在安全漏洞。本地攻击者可利用该漏洞造成拒绝服务(阻止终端启动)。目前,供应商发布了安全公告及相关补丁信息,修复了此漏洞。
Formal description

目前厂商已经发布了升级补丁以修复此安全问题,补丁获取链接: https://git.lxde.org/gitweb/?p=lxde/lxterminal.git;a=commit;h=f99163c6ff8b2f57c5f37b1ce5d62cf7450d4648

Reference
https://unix.stackexchange.com/questions/333539/lxterminal-in-the-netstat-output/333578
Impacted products
Name
lxterminal lxterminal <=0.3.0
Show details on source website

{
  "cves": {
    "cve": {
      "cveNumber": "CVE-2016-10369"
    }
  },
  "description": "lxterminal\u662f\u4e00\u4e2a\u5f00\u6e90\u7684\u7ec8\u7aef\u6a21\u62df\u5668\u7a0b\u5e8f\uff0c\u8be5\u7a0b\u5e8f\u652f\u6301\u590d\u5236\u3001\u7c98\u8d34\u4ee5\u53ca\u6807\u7b7e\u7b49\u529f\u80fd\u3002\r\n\r\nlxterminal 0.3.0\u53ca\u4e4b\u524d\u7684\u7248\u672c\u4e2d\u7684unixsocket.c\u6587\u4ef6\u5b58\u5728\u5b89\u5168\u6f0f\u6d1e\u3002\u672c\u5730\u653b\u51fb\u8005\u53ef\u5229\u7528\u8be5\u6f0f\u6d1e\u9020\u6210\u62d2\u7edd\u670d\u52a1\uff08\u963b\u6b62\u7ec8\u7aef\u542f\u52a8\uff09\u3002",
  "discovererName": "Yao Wei",
  "formalWay": "\u76ee\u524d\u5382\u5546\u5df2\u7ecf\u53d1\u5e03\u4e86\u5347\u7ea7\u8865\u4e01\u4ee5\u4fee\u590d\u6b64\u5b89\u5168\u95ee\u9898\uff0c\u8865\u4e01\u83b7\u53d6\u94fe\u63a5\uff1a\r\nhttps://git.lxde.org/gitweb/?p=lxde/lxterminal.git;a=commit;h=f99163c6ff8b2f57c5f37b1ce5d62cf7450d4648",
  "isEvent": "\u901a\u7528\u8f6f\u786c\u4ef6\u6f0f\u6d1e",
  "number": "CNVD-2017-07084",
  "openTime": "2017-05-19",
  "patchDescription": "lxterminal\u662f\u4e00\u4e2a\u5f00\u6e90\u7684\u7ec8\u7aef\u6a21\u62df\u5668\u7a0b\u5e8f\uff0c\u8be5\u7a0b\u5e8f\u652f\u6301\u590d\u5236\u3001\u7c98\u8d34\u4ee5\u53ca\u6807\u7b7e\u7b49\u529f\u80fd\u3002\r\n\r\nlxterminal 0.3.0\u53ca\u4e4b\u524d\u7684\u7248\u672c\u4e2d\u7684unixsocket.c\u6587\u4ef6\u5b58\u5728\u5b89\u5168\u6f0f\u6d1e\u3002\u672c\u5730\u653b\u51fb\u8005\u53ef\u5229\u7528\u8be5\u6f0f\u6d1e\u9020\u6210\u62d2\u7edd\u670d\u52a1\uff08\u963b\u6b62\u7ec8\u7aef\u542f\u52a8\uff09\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": "lxterminal\u5b58\u5728\u672a\u660e\u6f0f\u6d1e\u7684\u8865\u4e01",
  "products": {
    "product": "lxterminal lxterminal \u003c=0.3.0"
  },
  "referenceLink": "https://unix.stackexchange.com/questions/333539/lxterminal-in-the-netstat-output/333578",
  "serverity": "\u4e2d",
  "submitTime": "2017-05-10",
  "title": "lxterminal\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.