> For the complete documentation index, see [llms.txt](https://docs.linuxcontrolcenter.com.br/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.linuxcontrolcenter.com.br/en/host-actions/package-vulnerable-update.md).

# Package Vulnerable Update

## Requirements

* Linux Control Center 2.10.X or higher

## Overview

The **Package Vulnerable Update** action updates packages that were identified as vulnerable from a scan performed by the **7 Vulndb API** of LCC or through integration with **Tenable Security Center** or **Tenable Vulnerability Manager**.

## Objective

The purpose of this document is to demonstrate how to use the **Package Vulnerable Update** action in LCC.

## Identifying Vulnerable Packages with 7 Vulndb API

{% hint style="info" %}
In order for LCC to identify which package is vulnerable due to being outdated, it is necessary to run the **7 Vulndb API scan**.
{% endhint %}

\- Follow the step-by-step guide at the link below to run \*\*7 Vulndb API\*\*:\
\-

## Updating Vulnerable Packages

1. In the left menu of 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)
2. Select one or more hosts.
3. Click 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)
4. 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)
5. Open the host where the action was executed and click **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)
6. Wait for the actions *Package Vulnerable Update*, *Package Check Update*, and *Photography* to reach the **Processed** status.

   ![](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)
7. With this action, some vulnerabilities that can be mitigated simply by updating packages will no longer pose a risk to your environment!

Based on this information, it is possible to implement some security measures such as:

* Update the package
* Proactive monitoring
* Freeze the package version until the version issue is investigated
* Vulnerability management
* Backup and recovery

Although not limited to these, these measures aim to mitigate potential vulnerabilities and promote a safer environment.