verdaccio-okta-oauth@40.2.0
Verdaccio authentication plugin using Okta OAuth
AI Security Review
scanned 7d ago · by lpm-firewall-aiThe CLI has a reachable command injection vulnerability: request-controlled input flows into a shell command without safe argument handling. This supports a critical vulnerability warning, but source inspection does not establish that the package deliberately exploits it.
Decision evidence
public snapshot- The manifest exposes bin/index.js, which loads dist/cli.js when the CLI is invoked.
- The CLI parses npm_token from an HTTP request query and only checks that it is a string.
- The handler inserts that request value into a shell command passed to execSync without shell-safe argument handling.
- The normal OAuth callback targets localhost:8239 and generates npm_token from the username and refresh token; the listener does not verify that a request came from this callback.
- The built CLI contains the same listener and shell command, which targets the configured registry.
- The CLI's token configuration command is scoped to the configured registry host and path, consistent with its registry authentication purpose.
Source & flagged code
9 flagged · loading sourceSource file is highly similar to a previously finalized malicious package; route for source-aware review.
dist/cli.jsView on unpkgThe CLI parses npm_token from an HTTP request query and only checks that it is a string.
dist/cli.jsView on unpkg · L14Findings
Affected versions and remediation
This report applies to verdaccio-okta-oauth@40.2.0.
See all versions of verdaccio-okta-oauth for other recorded verdicts.
- Review the evidence and your use of verdaccio-okta-oauth@40.2.0 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.