Vulnerability Issues

what are they? when compromised open source code packages are discovered by software developers and other members of the cybersecurity community, they are reported as vulnerabilities and given a vulnerability identifier (typically a common vulnerability enumeration or cve) cve records are added to a number of publicly accessible vulnerability databases, such as the national vulnerability database (nvd) and github advisory database during an sca, sbom, or container scan, soos compares the packages that are identified against numerous vulnerability databases, including nvd, github, and many more if there are matches, soos reports these to you as vulnerabilities vulnerability issue details include the name and version of the package which introduced the vulnerability, a link to research the vulnerability, the manifest or location where the vulnerability was introduced, as well as potentially newer version to upgrade to how does that affect my code? vulnerabilities can open your code and your users to various attacks, including remote code execution, data access, compromised systems, and more what can i do about it? vulnerabilities can often be fixed by updating to a newer version of the vulnerable package following the fix recommendations included in the vulnerability issue details displayed in the soos app creating tickets & pull requests docid\ nciuaesesmhdpuaddbfk4 contains more information about selecting and applying fixes