diff options
| author | Stijn Tintel <stijn@linux-ipv6.be> | 2022-12-20 20:04:53 +0200 |
|---|---|---|
| committer | Hauke Mehrtens <hauke@hauke-m.de> | 2022-12-22 00:14:30 +0100 |
| commit | 377d8058879524d07231a11da0e5ccfeed0424e2 (patch) | |
| tree | 127923b1fe91294cebfceb8c94d480efda4837a6 /include | |
| parent | f30414c56db372acbd32d4cf77a2d0164c3e2b71 (diff) | |
| download | upstream-377d8058879524d07231a11da0e5ccfeed0424e2.tar.gz upstream-377d8058879524d07231a11da0e5ccfeed0424e2.tar.bz2 upstream-377d8058879524d07231a11da0e5ccfeed0424e2.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>
(cherry picked from commit c8c6508c22c59a09b7acce63bed28947788a46d4)
Diffstat (limited to 'include')
| -rw-r--r-- | include/trusted-firmware-a.mk | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/include/trusted-firmware-a.mk b/include/trusted-firmware-a.mk index d95250452b..14c03b99c8 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 |