All dom-iterator versions

dom-iterator @0.3.0

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.
88
Risk Score
MIT
License
Yes
Install Scripts
2
Dependencies
3
Dev Dependencies
6.2 KB
Package Size
Published

iterator for mini-html-parser

Maintainers

mattmuellertootallnate

Keywords

iteratordommini-html-parser

Dependencies (2)

PackageConstraintRegistry Status
component-xor 0.0.3 auto_approved
component-props 1.1.1 auto_approved

Dev Dependencies (3)

PackageConstraintRegistry Status
mocha ~1.17.1 auto_approved
component-test ~0.1.3 Not imported
mini-html-parser 0.0.3 Not imported

Transitive Dependency Tree

2 transitive deps max depth 1
  ├─ component-props 1.1.1 → 1.1.1
  ├─ component-xor 0.0.3 → 0.0.3

Risk Dispositions (1 applicable to this version, 0 other)

Accepted rules are downgraded to INFO on future analyses; rejected rules escalate to CRITICAL.

Rule Source Disposition Author Reason
osv:GHSA-jrvm-mcxc-mf6m osv reject AI AI (osv): CVE-2024-21541: arbitrary code execution via Function constructor; fixed in 1.0.1. Affects all versions < 1.0.1.

SAST Findings (3)

CRITICAL GHSA-jrvm-mcxc-mf6m: dom-iterator code execution vulnerability osv

[Always reject] CVSS 7.3 (HIGH) — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L Versions of the package dom-iterator before 1.0.1 are vulnerable to Arbitrary Code Execution due to use of the Function constructor without complete input sanitization. Function generates a new function body and thus care must be given to ensure that the inputs to Function are not attacker-controlled. The risks involved are similar to that of allowing attacker-controlled input to reach eval.

HIGH Publisher changed: mattmueller → tootallnate (on 2014-07-20) provenance

This version was published by a different npm account than previous versions on 2014-07-20. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

Review Summary

Risk score: 88. Findings: 1 critical (+40), 1 high (+25), 2 medium (+20), 1 low (+3).

Commit: 9f183af5532f Browse source

Published to npm: