Addressing False Positive Vulnerability Findings for Common Package Names.

Addressing False Positive Vulnerability Findings for Common Package Names.

199
Created On 11/14/25 18:02 PM - Last Modified 11/14/25 23:28 PM


Symptom


  • Several false positive detections observed for common packages like Alpine, the affected CVEs include CVE-2023-27482, and CVE-2022-28841
  • CVE-2022-28841 is detected incorrectly for Alpine since the package bridge is common for both Alpine and Adobe Systems Incorporated
  • Similarly for CVE-2023-27482, NVD and Alpine both share a package named supervisor but NVD detection points to home-assistant:supervisor, which is unrelated to Alpine


Environment


  1. Alpine Linux
  2. Prisma Cloud Compute


Cause


The vulnerability false positives (e.g., for packages like supervisor and bridge) are caused by a known, industry-wide challenge: package name ambiguity. This occurs when unrelated software from different ecosystems (e.g., Alpine Linux vs. Home Assistant, or Alpine Linux vs. Adobe) share an identical package name.

The core issue is that vulnerability data, such as that from the National Vulnerability Database (NVD), often lacks a specific "running-on-with" configuration. This missing data makes it difficult to programmatically differentiate which package the vulnerability applies to. As a result, a CVE intended for one vendor's product (like home-assistant:supervisor) can be incorrectly associated with another vendor's package that shares the same name.



Resolution


To address this class of false positives, a future enhancement is planned to improve our matching logic. This update will allow our system to use additional contextual data to better distinguish between packages with identical names but from different publishers, significantly improving the accuracy of vulnerability reporting.



Additional Information


In the context of the National Vulnerability Database (NVD), CPE stands for Common Platform Enumeration, which is a standardized naming scheme for information technology systems, software, and hardware. It provides a structured way to describe the specific IT products associated with vulnerabilities (CVEs), making it easier to determine which systems are affected by a particular security issue.  
 
  • Function
    CPE normalizes the way products are named by including the component type (like application, operating system, or hardware), vendor, product, and version. 
     
  • Usage in NVD
    The NVD uses CPE to link vulnerabilities (CVEs) to the specific software and hardware that are impacted. For example, a CVE record will often contain one or more CPE entries to indicate the affected products. 
     
  • Purpose
    By providing a consistent and standardized format, CPE allows for automated searching, vulnerability scanning, and the creation of software bill of materials (SBOMs) that track vulnerable components. 


Actions
  • Print
  • Copy Link

    https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA1Ki000000fyc3KAA&lang=en_US&refURL=http%3A%2F%2Fknowledgebase.paloaltonetworks.com%2FKCSArticleDetail