# 7 VulnDB-API ## Requirements Linux Control Center = 2.10.X or higher ## Overview The Linux Control Center (LCC) has the 7vulndb-api, a constantly updated database with information about vulnerable packages from the main Linux distributions. The identification process uses the database to check for packages with vulnerabilities. Then, a scan is performed on all hosts managed by the LCC to compare and identify the presence of any package listed in the database. ## Objective The objective of this manual is to demonstrate the step-by-step process for using the LCC's 7Vulndb vulnerability API. ## Identifying Vulnerable Packages with the 7 Vulndb API {% hint style="warning" %} When performing this action on a Host, all packages with identified vulnerabilities will be marked. If the same package with vulnerability is installed on another Host, it will also be flagged in the Console. {% endhint %} 1. Access the LCC and click on **7 Vulndb API** ![](https://1620115297-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtZm19HsLxuDm2GumYKEz%2Fuploads%2Fgit-blob-7cf799a5ba07fae5b63fae9cf3bd52a0ecf6907f%2Fbotao-7vuln-dashboard.png?alt=media) 1. Click on **Check Vulnerability** ![](https://1620115297-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtZm19HsLxuDm2GumYKEz%2Fuploads%2Fgit-blob-ce3f11c8b18a4fcbb73707e9193e1bb67a06a853%2Fbotao-checkvulnerability-tela-api.png?alt=media) 1. The **Status** column will have the phrase ***Waiting API process:*** indicating that the API is performing the scan. ![](https://1620115297-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtZm19HsLxuDm2GumYKEz%2Fuploads%2Fgit-blob-57975a00223eeab5e590608a1c3a14578660f92c%2Fapi-processando.png?alt=media) 1. The **Status** column will have ***API awnser received:***, indicating that the scan has finished, along with the number of packages scanned. ![](https://1620115297-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtZm19HsLxuDm2GumYKEz%2Fuploads%2Fgit-blob-d4b19e4dde0f77eacec72b59c8b67417d7a4264c%2Fapi-finalizada.png?alt=media) 1. These are the descriptions of the information fields on the **7 Vulndb API** screen * **Packages request:** Total number of packages sent for analysis. * **Packages vulnerable:** Number of packages that have some vulnerability, whether exploitable or not. * **Request Uuid:** Request identifier. * **Created at:** Time the analysis request was sent. * **Updated at:** Time the analysis request was completed. ## Package Analysis Vulnerabilities After the scan is complete, you can get more details about the vulnerabilities found in the packages. 1. Click on **Hosts** in the left side menu. ![](https://1620115297-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtZm19HsLxuDm2GumYKEz%2Fuploads%2Fgit-blob-100bfe54e874fce161f05d8ae0a1eda065e8d997%2Fbotao-hosts.png?alt=media) 1. Click on a desired Host and click on **CVEs**. ![](https://1620115297-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtZm19HsLxuDm2GumYKEz%2Fuploads%2Fgit-blob-bc9be8f6b1571159fbb04bd20ab6ea7ed34ac3d4%2Fgeneral-host.png?alt=media) 1. All **CVEs** identified in all packages will be displayed. ![](https://1620115297-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtZm19HsLxuDm2GumYKEz%2Fuploads%2Fgit-blob-4a4ff8312e83ca85d7c6bbcf5524e41df5a6ec18%2Ftela-cves.png?alt=media) 1. To find the **CVE** of a specific package, change the selector from Host to Package ![](https://1620115297-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtZm19HsLxuDm2GumYKEz%2Fuploads%2Fgit-blob-b2d0db33e71e6d5187ee6ab0b62ac7dd102f60ce%2Fhost-para-packages.png?alt=media) 1. Click on **Filter Packages** ![](https://gitlab.com/7dev-doc/linux-control-center/-/blob/main/pt-br/images/7vulndb_api/arrow-bottom-filter-packages.png) 1. Note that it is possible to use the **Package Vulnerable By Tenable** filter in conjunction with the **Package Vulnerable By 7Vulndb** filter 2. Select the desired filters and click on **Confirm Filter**. ![](https://1620115297-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtZm19HsLxuDm2GumYKEz%2Fuploads%2Fgit-blob-059c12a693fc8c39cd52eeac0b0641cab802f205%2Fby-7vuln-by-tenable.png?alt=media) 1. This way, only the vulnerabilities related to the selected packages will be listed. ![](https://1620115297-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtZm19HsLxuDm2GumYKEz%2Fuploads%2Fgit-blob-f61915589a3eaf6170f943623fe38bda1683c798%2Ffilter-packages-somente-alguns-pacotes.png?alt=media) ## Updating Vulnerable Packages 1. In the left side menu of the LCC, click on **Hosts**. ![](https://1620115297-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtZm19HsLxuDm2GumYKEz%2Fuploads%2Fgit-blob-bf2553b10fbabb1e6772981c894be4d600207cff%2Fhosts_dashboard.png?alt=media) 1. Select 1 or more Hosts and click on the **Actions** button at the top of the page and execute the **Package Vulnerable Update** action. ![](https://1620115297-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtZm19HsLxuDm2GumYKEz%2Fuploads%2Fgit-blob-9c70c6d392430dd6d05cc029a734d541273a6578%2Fseta_package_vulnerable_update.png?alt=media) 1. Confirm the action by clicking **Yes** ![](https://1620115297-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtZm19HsLxuDm2GumYKEz%2Fuploads%2Fgit-blob-97e137a0cdb9f5b507b146255b65cc9af6f0ac85%2Fconfirma_vulnerable_update.png?alt=media) 1. Open the host that sent the action and click on **Actions History** ![](https://1620115297-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtZm19HsLxuDm2GumYKEz%2Fuploads%2Fgit-blob-b3f76fdbc5ff6a28a7b28109f9673a91572a9142%2Ftela_general_seta_actions.png?alt=media) 1. Wait for the actions *Package Vulnerable update,* *Package Check Update* and *Photography* to have the status **Processed** ![](https://1620115297-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtZm19HsLxuDm2GumYKEz%2Fuploads%2Fgit-blob-11c4c8549c996472c10c702e9fe93b743504c6a3%2Factions_history_vulnerable_update.png?alt=media) 1. With this action, some vulnerabilities that can be mitigated only by updating packages will no longer be a risk to your environment! Based on this information, it is possible to develop some security measures such as: * Update package * Proactive monitoring * Freeze package version until the version situation is investigated. * Vulnerability management * Backup and recovery Although not limited to these options, these measures aim to mitigate possible vulnerabilities and promote a safer environment.