CNVD-2015-02848

Vulnerability from cnvd - Published: 2015-05-04
VLAI
Title
Magento Community Edition和Enterprise Edition存在漏洞
Description
Magento是美国Magento公司的一套专业开源的PHP电子商务系统,它提供权限管理、搜索引擎和支付网关等功能。Magento Community Edition(CE)是一个社区版。Magento Enterprise Edition(EE)是一个企业版。 Magento CE 1.9.1.0版本和EE 1.14.1.0版本的Mage_Core_Block_Template_Zend类中的‘fetchView’函数存在安全漏洞。由于程序未能正确限制在模版路径中使用流封装。远程攻击者可通过phar://流封装利用该漏洞包含并执行任意PHP文件。
Severity
中
Patch Name
Magento Community Edition和Enterprise Edition存在漏洞的补丁
Patch Description
Magento是美国Magento公司的一套专业开源的PHP电子商务系统,它提供权限管理、搜索引擎和支付网关等功能。Magento Community Edition(CE)是一个社区版。Magento Enterprise Edition(EE)是一个企业版。 Magento CE 1.9.1.0版本和EE 1.14.1.0版本的Mage_Core_Block_Template_Zend类中的‘fetchView’函数存在安全漏洞。由于程序未能正确限制在模版路径中使用流封装。远程攻击者可通过phar://流封装利用该漏洞包含并执行任意PHP文件。目前,供应商发布了安全公告及相关补丁信息,修复了此漏洞。
Formal description

用户可参考如下供应商提供的安全公告获得补丁信息: http://magento.com/blog/technical/critical-security-advisory-remote-code-execution-rce-vulnerability

Reference
http://blog.checkpoint.com/2015/04/20/analyzing-magento-vulnerability/ http://magento.com/blog/technical/critical-security-advisory-remote-code-execution-rce-vulnerability
Impacted products
Name
['Magento Magento Community Edition (CE) 1.9.1.0', 'Magento Magento Enterprise Edition (EE) 1.14.1.0']
Show details on source website

{
  "cves": {
    "cve": {
      "cveNumber": "CVE-2015-3458"
    }
  },
  "description": "Magento\u662f\u7f8e\u56fdMagento\u516c\u53f8\u7684\u4e00\u5957\u4e13\u4e1a\u5f00\u6e90\u7684PHP\u7535\u5b50\u5546\u52a1\u7cfb\u7edf\uff0c\u5b83\u63d0\u4f9b\u6743\u9650\u7ba1\u7406\u3001\u641c\u7d22\u5f15\u64ce\u548c\u652f\u4ed8\u7f51\u5173\u7b49\u529f\u80fd\u3002Magento Community Edition\uff08CE\uff09\u662f\u4e00\u4e2a\u793e\u533a\u7248\u3002Magento Enterprise Edition\uff08EE\uff09\u662f\u4e00\u4e2a\u4f01\u4e1a\u7248\u3002\r\n\r\nMagento CE 1.9.1.0\u7248\u672c\u548cEE 1.14.1.0\u7248\u672c\u7684Mage_Core_Block_Template_Zend\u7c7b\u4e2d\u7684\u2018fetchView\u2019\u51fd\u6570\u5b58\u5728\u5b89\u5168\u6f0f\u6d1e\u3002\u7531\u4e8e\u7a0b\u5e8f\u672a\u80fd\u6b63\u786e\u9650\u5236\u5728\u6a21\u7248\u8def\u5f84\u4e2d\u4f7f\u7528\u6d41\u5c01\u88c5\u3002\u8fdc\u7a0b\u653b\u51fb\u8005\u53ef\u901a\u8fc7phar://\u6d41\u5c01\u88c5\u5229\u7528\u8be5\u6f0f\u6d1e\u5305\u542b\u5e76\u6267\u884c\u4efb\u610fPHP\u6587\u4ef6\u3002",
  "discovererName": "Magento",
  "formalWay": "\u7528\u6237\u53ef\u53c2\u8003\u5982\u4e0b\u4f9b\u5e94\u5546\u63d0\u4f9b\u7684\u5b89\u5168\u516c\u544a\u83b7\u5f97\u8865\u4e01\u4fe1\u606f\uff1a\r\nhttp://magento.com/blog/technical/critical-security-advisory-remote-code-execution-rce-vulnerability",
  "isEvent": "\u901a\u7528\u8f6f\u786c\u4ef6\u6f0f\u6d1e",
  "number": "CNVD-2015-02848",
  "openTime": "2015-05-04",
  "patchDescription": "Magento\u662f\u7f8e\u56fdMagento\u516c\u53f8\u7684\u4e00\u5957\u4e13\u4e1a\u5f00\u6e90\u7684PHP\u7535\u5b50\u5546\u52a1\u7cfb\u7edf\uff0c\u5b83\u63d0\u4f9b\u6743\u9650\u7ba1\u7406\u3001\u641c\u7d22\u5f15\u64ce\u548c\u652f\u4ed8\u7f51\u5173\u7b49\u529f\u80fd\u3002Magento Community Edition\uff08CE\uff09\u662f\u4e00\u4e2a\u793e\u533a\u7248\u3002Magento Enterprise Edition\uff08EE\uff09\u662f\u4e00\u4e2a\u4f01\u4e1a\u7248\u3002 \r\n\r\nMagento CE 1.9.1.0\u7248\u672c\u548cEE 1.14.1.0\u7248\u672c\u7684Mage_Core_Block_Template_Zend\u7c7b\u4e2d\u7684\u2018fetchView\u2019\u51fd\u6570\u5b58\u5728\u5b89\u5168\u6f0f\u6d1e\u3002\u7531\u4e8e\u7a0b\u5e8f\u672a\u80fd\u6b63\u786e\u9650\u5236\u5728\u6a21\u7248\u8def\u5f84\u4e2d\u4f7f\u7528\u6d41\u5c01\u88c5\u3002\u8fdc\u7a0b\u653b\u51fb\u8005\u53ef\u901a\u8fc7phar://\u6d41\u5c01\u88c5\u5229\u7528\u8be5\u6f0f\u6d1e\u5305\u542b\u5e76\u6267\u884c\u4efb\u610fPHP\u6587\u4ef6\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": "Magento Community Edition\u548cEnterprise Edition\u5b58\u5728\u6f0f\u6d1e\u7684\u8865\u4e01",
  "products": {
    "product": [
      "Magento Magento Community Edition (CE) 1.9.1.0",
      "Magento Magento Enterprise Edition (EE) 1.14.1.0"
    ]
  },
  "referenceLink": "http://blog.checkpoint.com/2015/04/20/analyzing-magento-vulnerability/ \r\nhttp://magento.com/blog/technical/critical-security-advisory-remote-code-execution-rce-vulnerability",
  "serverity": "\u4e2d",
  "submitTime": "2015-04-30",
  "title": "Magento Community Edition\u548cEnterprise Edition\u5b58\u5728\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.