All netmask versions

[email protected] rejected Risk: 53 MIT

netmask @1.0.6

rejected
This version was rejected. It did not pass GreenFlagged's security review and is not served by the registry. The findings and risk dispositions below explain why.
npm Repository Homepage Tarball
53
Risk Score
MIT
License
No
Install Scripts
0
Dependencies
2
Dev Dependencies
5.9 KB
Package Size
Published

Parse and lookup IP network blocks

Maintainers

rs

Keywords

netmaskipnetworkcidrnetmasksubnetipcalc

Dev Dependencies (2)

PackageConstraintRegistry Status
vows * auto_approved
coffee-script >=1.2.0 auto_approved

Changes from v0.0.1

Dependency Changes

ChangePackageVersion
removed coffee-script 1.2.0

File Changes

1 added 0 removed 6 modified size delta: +3.3 KB

SAST Findings (3)

CRITICAL GHSA-4c7m-wxvm-r7gc: Improper parsing of octal bytes in netmask osv

CVSS 9.1 (CRITICAL) — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N Improper input validation of octal strings in netmask npm package v1.0.6 and below allows unauthenticated remote attackers to perform indeterminate SSRF, RFI, and LFI attacks on many of the dependent packages. A remote unauthenticated attacker can bypass packages relying on netmask to filter IPs and reach critical VPN or LAN hosts. :exclamation: NOTE: The fix for this issue was incomplete. A subsequent fix was made in version `2.0.1` which was assigned [CVE-2021-29418 / GHSA-pch5-whg9-qr2r](https://github.com/advisories/GHSA-pch5-whg9-qr2r). For complete protection from this vulnerability an upgrade to version 2.0.1 or later is recommended.

MEDIUM GHSA-pch5-whg9-qr2r: netmask npm package mishandles octal input data osv

CVSS 5.3 (MEDIUM) — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N The netmask package before 2.0.1 for Node.js mishandles certain unexpected characters in an IP address string, such as an octal digit of 9. This (in some situations) allows attackers to bypass access control that is based on IP addresses. NOTE: this issue exists because of an incomplete fix for CVE-2021-28918.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

Review Summary

Risk score: 53. Findings: 1 critical (+40), 1 medium (+10), 1 low (+3).

Commit: 610161f7a8ca Browse source

Published to npm: