Bump vulners from 2.1.5 to 2.1.7

[dependabot]

Bumps vulners from 2.1.5 to 2.1.7.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dryrunsecurity]

Hi there 👋, @DryRunSecurity here, below is a summary of our analysis and findings.

DryRun Security	Status	Findings
AppSec Analyzer	✅	0 findings
Configured Codepaths Analyzer	✅	0 findings
Sensitive Files Analyzer	❕	1 finding
Authn/Authz Analyzer	✅	0 findings
Secrets Analyzer	✅	0 findings

Note

🟢 Risk threshold not exceeded.

Change Summary (click to expand)

The following is a summary of changes in this pull request made by me, your security buddy 🤖. Note that this summary is auto-generated and not meant to be a definitive list of security issues but rather a helpful summary from a security perspective.

Summary:

The code change in the provided requirements.txt file is updating the vulners package from version 2.1.5 to 2.1.7. This package is a Python library that provides an interface to the Vulners API, which is a vulnerability database. From an application security perspective, this update is generally a positive change, as it likely includes bug fixes, security improvements, or new features that enhance the library's functionality. Keeping dependencies up-to-date is an important aspect of maintaining the security of an application. The requirements.txt file is a common way to manage the dependencies of a Python-based application, such as DefectDojo, which is a popular open-source web application for managing software vulnerabilities. By maintaining a centralized list of required packages and their versions, it becomes easier to ensure that the application is deployed with the correct dependencies, reducing the risk of compatibility issues or security vulnerabilities introduced by outdated dependencies. Overall, this code change appears to be a routine update to a dependency, which is a standard practice in software development to keep the application secure and up-to-date.

Files Changed:

• requirements.txt: The code change in this file updates the vulners package from version 2.1.5 to 2.1.7. This package is a Python library that provides an interface to the Vulners API, which is a vulnerability database. Updating dependencies to their latest versions is a common practice to maintain the security and functionality of the application.

Powered by DryRun Security

[mtesauro]

Approved