Next Generation Application Programming Interface
Approved changes feed: RSS · Atom
cpe:2.3:a:netapp:next_generation_application_programming_interface:-:*:*:*:*:*:*:*
part: a version: - update: *
| Vendor | Netapp (f19678f6-cb27-5a55-8852-34b249f80ef9) |
|---|---|
| Product | Next Generation Application Programming Interface (897607ff-6e8e-508f-963f-b2985d21660c) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2021-43616 |
vulnerable | 2026-06-08 05:36:43.625877 |
Details available
CRITICAL (9)
The npm ci command in npm 7.x and 8.x through 8.1.3 proceeds with an installation even if dependency information in package-lock.json differs from package.json. This behavior is inconsistent with the documentation, and makes it easier for attackers to install malware that was supposed to have been blocked by an exact version match requirement in package-lock.json. NOTE: The npm team believes this is not a vulnerability. It would require someone to socially engineer package.json which has different dependencies than package-lock.json. That user would have to have file system or write access to change dependencies. The npm team states preventing malicious actors from socially engineering or gaining file system access is outside the scope of the npm CLI.
Published: 2021-11-13T00:00:00.000Z
Updated: 2024-08-04T04:03:08.795Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.