CNVD-2017-30661

Vulnerability from cnvd - Published: 2017-10-19
VLAI
Title
AVM FRITZ!Box 6810 LTE和FRITZ!Box 6840 LTE代码注入漏洞
Description
AVM FRITZ!Box 6810 LTE和FRITZ!Box 6840 LTE都是德国AVM公司的路由器产品。 AVM FRITZ!Box 6810 LTE和FRITZ!Box 6840 LTE中存在代码注入漏洞,该漏洞源于程序未能正确的验证加密签名。远程攻击者可利用该漏洞注入并执行恶意的代码。
Severity
高
Patch Name
AVM FRITZ!Box 6810 LTE和FRITZ!Box 6840 LTE代码注入漏洞 的补丁
Patch Description
AVM FRITZ!Box 6810 LTE和FRITZ!Box 6840 LTE都是德国AVM公司的路由器产品。 AVM FRITZ!Box 6810 LTE和FRITZ!Box 6840 LTE中存在代码注入漏洞,该漏洞源于程序未能正确的验证加密签名。远程攻击者可利用该漏洞注入并执行恶意的代码。目前,供应商发布了安全公告及相关补丁信息,修复了此漏洞。
Formal description

目前厂商已发布升级补丁以修复漏洞,详情请关注厂商主页: https://avm.de/

Reference
https://nvd.nist.gov/vuln/detail/CVE-2014-8872
Impacted products
Name
['AVM AVM FRITZ!Box 7490', 'AVM AVM FRITZ!Box 7390', 'AVM AVM FRITZ!Box 7270v3']
Show details on source website

{
  "cves": {
    "cve": {
      "cveNumber": "CVE-2014-8872"
    }
  },
  "description": "AVM FRITZ!Box 6810 LTE\u548cFRITZ!Box 6840 LTE\u90fd\u662f\u5fb7\u56fdAVM\u516c\u53f8\u7684\u8def\u7531\u5668\u4ea7\u54c1\u3002\r\n\r\nAVM FRITZ!Box 6810 LTE\u548cFRITZ!Box 6840 LTE\u4e2d\u5b58\u5728\u4ee3\u7801\u6ce8\u5165\u6f0f\u6d1e\uff0c\u8be5\u6f0f\u6d1e\u6e90\u4e8e\u7a0b\u5e8f\u672a\u80fd\u6b63\u786e\u7684\u9a8c\u8bc1\u52a0\u5bc6\u7b7e\u540d\u3002\u8fdc\u7a0b\u653b\u51fb\u8005\u53ef\u5229\u7528\u8be5\u6f0f\u6d1e\u6ce8\u5165\u5e76\u6267\u884c\u6076\u610f\u7684\u4ee3\u7801\u3002",
  "discovererName": "unknwon",
  "formalWay": "\u76ee\u524d\u5382\u5546\u5df2\u53d1\u5e03\u5347\u7ea7\u8865\u4e01\u4ee5\u4fee\u590d\u6f0f\u6d1e\uff0c\u8be6\u60c5\u8bf7\u5173\u6ce8\u5382\u5546\u4e3b\u9875\uff1a\r\nhttps://avm.de/",
  "isEvent": "\u901a\u7528\u8f6f\u786c\u4ef6\u6f0f\u6d1e",
  "number": "CNVD-2017-30661",
  "openTime": "2017-10-19",
  "patchDescription": "AVM FRITZ!Box 6810 LTE\u548cFRITZ!Box 6840 LTE\u90fd\u662f\u5fb7\u56fdAVM\u516c\u53f8\u7684\u8def\u7531\u5668\u4ea7\u54c1\u3002\r\n\r\nAVM FRITZ!Box 6810 LTE\u548cFRITZ!Box 6840 LTE\u4e2d\u5b58\u5728\u4ee3\u7801\u6ce8\u5165\u6f0f\u6d1e\uff0c\u8be5\u6f0f\u6d1e\u6e90\u4e8e\u7a0b\u5e8f\u672a\u80fd\u6b63\u786e\u7684\u9a8c\u8bc1\u52a0\u5bc6\u7b7e\u540d\u3002\u8fdc\u7a0b\u653b\u51fb\u8005\u53ef\u5229\u7528\u8be5\u6f0f\u6d1e\u6ce8\u5165\u5e76\u6267\u884c\u6076\u610f\u7684\u4ee3\u7801\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": "AVM FRITZ!Box 6810 LTE\u548cFRITZ!Box 6840 LTE\u4ee3\u7801\u6ce8\u5165\u6f0f\u6d1e \u7684\u8865\u4e01",
  "products": {
    "product": [
      "AVM AVM FRITZ!Box 7490",
      "AVM AVM FRITZ!Box 7390",
      "AVM  AVM FRITZ!Box 7270v3"
    ]
  },
  "referenceLink": "https://nvd.nist.gov/vuln/detail/CVE-2014-8872",
  "serverity": "\u9ad8",
  "submitTime": "2017-08-29",
  "title": "AVM FRITZ!Box 6810 LTE\u548cFRITZ!Box 6840 LTE\u4ee3\u7801\u6ce8\u5165\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.