CNVD-2016-10484

Vulnerability from cnvd - Published: 2016-11-02
VLAI
Title
Samsung Galaxy S4至S7设备中的libomacp.so整数溢出漏洞
Description
Samsung Galaxy S4等都是韩国三星(Samsung)公司发布的智能移动设备。 Samsung Galaxy S4至S7设备中的libomacp.so存在整数溢出漏洞。当程序解析OMACP(包含WAP Push SMS信息) 信息时,攻击者可利用该漏洞造成拒绝服务(堆损坏),也可能执行远程代码。
Severity
高
Patch Name
Samsung Galaxy S4至S7设备中的libomacp.so整数溢出漏洞的补丁
Patch Description
Samsung Galaxy S4等都是韩国三星(Samsung)公司发布的智能移动设备。 Samsung Galaxy S4至S7设备中的libomacp.so存在整数溢出漏洞。当程序解析OMACP(包含WAP Push SMS信息) 信息时,攻击者可利用该漏洞造成拒绝服务(堆损坏),也可能执行远程代码。目前,供应商发布了安全公告及相关补丁信息,修复了此漏洞。
Formal description

目前厂商已经发布了升级补丁以修复此安全问题,补丁获取链接: http://security.samsungmobile.com/smrupdate.html#SMR-AUG-2016

Reference
http://security.samsungmobile.com/smrupdate.html#SMR-AUG-2016
Impacted products
Name
Samsung Galaxy >=s4,<=s7
Show details on source website

{
  "cves": {
    "cve": {
      "cveNumber": "CVE-2016-7990"
    }
  },
  "description": "Samsung Galaxy S4\u7b49\u90fd\u662f\u97e9\u56fd\u4e09\u661f\uff08Samsung\uff09\u516c\u53f8\u53d1\u5e03\u7684\u667a\u80fd\u79fb\u52a8\u8bbe\u5907\u3002\r\n\r\nSamsung Galaxy S4\u81f3S7\u8bbe\u5907\u4e2d\u7684libomacp.so\u5b58\u5728\u6574\u6570\u6ea2\u51fa\u6f0f\u6d1e\u3002\u5f53\u7a0b\u5e8f\u89e3\u6790OMACP(\u5305\u542bWAP Push SMS\u4fe1\u606f) \u4fe1\u606f\u65f6\uff0c\u653b\u51fb\u8005\u53ef\u5229\u7528\u8be5\u6f0f\u6d1e\u9020\u6210\u62d2\u7edd\u670d\u52a1\uff08\u5806\u635f\u574f\uff09\uff0c\u4e5f\u53ef\u80fd\u6267\u884c\u8fdc\u7a0b\u4ee3\u7801\u3002",
  "discovererName": "unknown",
  "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\nhttp://security.samsungmobile.com/smrupdate.html#SMR-AUG-2016",
  "isEvent": "\u901a\u7528\u8f6f\u786c\u4ef6\u6f0f\u6d1e",
  "number": "CNVD-2016-10484",
  "openTime": "2016-11-02",
  "patchDescription": "Samsung Galaxy S4\u7b49\u90fd\u662f\u97e9\u56fd\u4e09\u661f\uff08Samsung\uff09\u516c\u53f8\u53d1\u5e03\u7684\u667a\u80fd\u79fb\u52a8\u8bbe\u5907\u3002\r\n\r\nSamsung Galaxy S4\u81f3S7\u8bbe\u5907\u4e2d\u7684libomacp.so\u5b58\u5728\u6574\u6570\u6ea2\u51fa\u6f0f\u6d1e\u3002\u5f53\u7a0b\u5e8f\u89e3\u6790OMACP(\u5305\u542bWAP Push SMS\u4fe1\u606f) \u4fe1\u606f\u65f6\uff0c\u653b\u51fb\u8005\u53ef\u5229\u7528\u8be5\u6f0f\u6d1e\u9020\u6210\u62d2\u7edd\u670d\u52a1\uff08\u5806\u635f\u574f\uff09\uff0c\u4e5f\u53ef\u80fd\u6267\u884c\u8fdc\u7a0b\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": "Samsung Galaxy S4\u81f3S7\u8bbe\u5907\u4e2d\u7684libomacp.so\u6574\u6570\u6ea2\u51fa\u6f0f\u6d1e\u7684\u8865\u4e01",
  "products": {
    "product": "Samsung Galaxy \u003e=s4\uff0c\u003c=s7"
  },
  "referenceLink": "http://security.samsungmobile.com/smrupdate.html#SMR-AUG-2016",
  "serverity": "\u9ad8",
  "submitTime": "2016-11-01",
  "title": "Samsung Galaxy S4\u81f3S7\u8bbe\u5907\u4e2d\u7684libomacp.so\u6574\u6570\u6ea2\u51fa\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.