CNVD-2020-34446

Vulnerability from cnvd - Published: 2020-06-23
VLAI
Title
SmartBear Software ReadyAPI注入漏洞
Description
SmartBear Software ReadyAPI是美国SmartBear Software公司的一款API测试平台。该平台提供安全测试(Secure Pro)、功能测试(SoapUI Pro)、性能测试(LoadUI Pro)、服务虚拟化(ServiceV Pro),以及生成测试报告等功能。jProductivity Protection!是美国jProductivity公司的一款许可工具包和许可管理器。 SmartBear Software ReadyAPI 3.2.5版本(使用了jProductivity Protection!)中存在安全漏洞。攻击者可利用该漏洞执行代码。
Severity
高
Formal description

目前厂商暂未发布修复措施解决此安全问题,建议使用此软件的用户随时关注厂商主页或参考网址以获取解决办法: https://smartbear.com/

Reference
https://nvd.nist.gov/vuln/detail/CVE-2020-12835
Impacted products
Name
SmartBear Software ReadyAPI 3.2.5
Show details on source website

{
  "cves": {
    "cve": {
      "cveNumber": "CVE-2020-12835"
    }
  },
  "description": "SmartBear Software ReadyAPI\u662f\u7f8e\u56fdSmartBear Software\u516c\u53f8\u7684\u4e00\u6b3eAPI\u6d4b\u8bd5\u5e73\u53f0\u3002\u8be5\u5e73\u53f0\u63d0\u4f9b\u5b89\u5168\u6d4b\u8bd5\uff08Secure Pro\uff09\u3001\u529f\u80fd\u6d4b\u8bd5\uff08SoapUI Pro\uff09\u3001\u6027\u80fd\u6d4b\u8bd5\uff08LoadUI Pro\uff09\u3001\u670d\u52a1\u865a\u62df\u5316\uff08ServiceV Pro\uff09\uff0c\u4ee5\u53ca\u751f\u6210\u6d4b\u8bd5\u62a5\u544a\u7b49\u529f\u80fd\u3002jProductivity Protection!\u662f\u7f8e\u56fdjProductivity\u516c\u53f8\u7684\u4e00\u6b3e\u8bb8\u53ef\u5de5\u5177\u5305\u548c\u8bb8\u53ef\u7ba1\u7406\u5668\u3002\n\nSmartBear Software ReadyAPI 3.2.5\u7248\u672c\uff08\u4f7f\u7528\u4e86jProductivity Protection!\uff09\u4e2d\u5b58\u5728\u5b89\u5168\u6f0f\u6d1e\u3002\u653b\u51fb\u8005\u53ef\u5229\u7528\u8be5\u6f0f\u6d1e\u6267\u884c\u4ee3\u7801\u3002",
  "formalWay": "\u76ee\u524d\u5382\u5546\u6682\u672a\u53d1\u5e03\u4fee\u590d\u63aa\u65bd\u89e3\u51b3\u6b64\u5b89\u5168\u95ee\u9898\uff0c\u5efa\u8bae\u4f7f\u7528\u6b64\u8f6f\u4ef6\u7684\u7528\u6237\u968f\u65f6\u5173\u6ce8\u5382\u5546\u4e3b\u9875\u6216\u53c2\u8003\u7f51\u5740\u4ee5\u83b7\u53d6\u89e3\u51b3\u529e\u6cd5\uff1a\r\nhttps://smartbear.com/",
  "isEvent": "\u901a\u7528\u8f6f\u786c\u4ef6\u6f0f\u6d1e",
  "number": "CNVD-2020-34446",
  "openTime": "2020-06-23",
  "products": {
    "product": "SmartBear Software ReadyAPI 3.2.5"
  },
  "referenceLink": "https://nvd.nist.gov/vuln/detail/CVE-2020-12835",
  "serverity": "\u9ad8",
  "submitTime": "2020-05-21",
  "title": "SmartBear Software ReadyAPI\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.