Update NIST CPE Dictionary

Nessuno ha ancora preso questa issue.

CPE (Common Platform Enumeration) is a standard syntax for describing software (e.g. vendor, software type, software name, version).

The [NIST CPE Dictionary](https://nvd.nist.gov/products/cpe) is a central database of registered CPEs. Vendors can register their CPEs with NIST to be added to the database.

Currently, LoopBack only has 1 CPE entry, [`cpe:2.3:a:ibm:loopback:8.0.0:*:*:*:*:*:*:*`](https://nvd.nist.gov/products/cpe/detail/849715?namingFormat=2.3&orderBy=CPEURI&keyword=loopback&status=FINAL).

Here is a 3-part proposal:

1. IBM is no longer the vendor for LoopBack
To solve this, we can revoke the current CPE and replace it with the following:
`cpe:2.3:a:loopback:\@loopback\/rest:8.0.0:*:*:*:*:*:*:*`
Note that the CPE above is not registered and may change once we contact NIST. The backslash is used to "quote" printable, non-alphanmuric characters in accordance with the CPE 2.3 specification.
2. Other vulnerable LoopBack packages with a published CVE do not have an associated CPE.
~~LB2/3 is quite different from LB4. Hence one proposal is to utilise the DefinitelyTyped syntax by:
a. Replacing the above CPE with double underscore
b. Use hyphen as per-normal for LB2/3 packages (e.g. `loopback-boot`)
This allows us to exploit the existing distinctive property separating LB2/3 and LB4, that LB2/3 packages are unscoped while LB4 packages are scoped.~~
3. For "non-LoopBack" packages such as `strong-soap`, keep the `loopback` vendor and use the package name as per-normal, similar to 2.a.

Inizia dai link del NIST CPE Dictionary presenti nell'issue e dagli identificatori CPE proposti per LoopBack e i pacchetti correlati. Determina quali voci debbano essere revocate, sostituite o aggiunte, quindi conferma la denominazione finale con NIST; il lavoro è completato quando i record CPE concordati sono registrati e le indicazioni di sicurezza del repository li riflettono.

Scritto dal modello di indicizzazione a partire dal testo della issue.