aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorStijn Tintel <stijn@linux-ipv6.be>2022-12-20 20:04:53 +0200
committerDaniel Golle <daniel@makrotopia.org>2022-12-20 18:36:26 +0000
commitc8c6508c22c59a09b7acce63bed28947788a46d4 (patch)
tree3fd565183e1f047ebc7d1a67d24213f0b82b542b
parent6675a9aaf4bc0afc3dccad8f9925b03b6e42993e (diff)
downloadupstream-c8c6508c22c59a09b7acce63bed28947788a46d4.tar.gz
upstream-c8c6508c22c59a09b7acce63bed28947788a46d4.tar.bz2
upstream-c8c6508c22c59a09b7acce63bed28947788a46d4.zip
trusted-firmware-a.mk: use correct CPE ID
There are 2 different CPE IDs on the NVD website: cpe:/a:arm:trusted_firmware-a cpe:/o:arm:arm_trusted_firmware The ID as currently used in trusted-firmware-a.mk does not exist. The CPE ID using the arm_trusted_firmware product name only lists a few records for versions 2.2 and 2.3 on the NVD site. The CPE ID using the trusted_firmware-a product name lists many more records, and actually has a CVE linked to it. Therefore, use the CPE ID using the trusted_firmware-a product name. Fixes: 104d60fe94ce ("trusted-firmware-a.mk: add PKG_CPE_ID") Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
-rw-r--r--include/trusted-firmware-a.mk2
1 files changed, 1 insertions, 1 deletions
diff --git a/include/trusted-firmware-a.mk b/include/trusted-firmware-a.mk
index 0b37c0f943..082ada269c 100644
--- a/include/trusted-firmware-a.mk
+++ b/include/trusted-firmware-a.mk
@@ -1,5 +1,5 @@
PKG_NAME ?= trusted-firmware-a
-PKG_CPE_ID ?= cpe:/a:arm:arm_trusted_firmware
+PKG_CPE_ID ?= cpe:/a:arm:trusted_firmware-a
ifndef PKG_SOURCE_PROTO
PKG_SOURCE = trusted-firmware-a-$(PKG_VERSION).tar.gz