How severe is GHSA-9px9-f7jw-fwhj?

No CVSS score has been assigned to GHSA-9px9-f7jw-fwhj yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-9px9-f7jw-fwhj?

GHSA-9px9-f7jw-fwhj affects the following packages: priest-runner (npm). Ecosystems affected: npm.

How do I fix GHSA-9px9-f7jw-fwhj?

No patched version of priest-runner has shipped for GHSA-9px9-f7jw-fwhj yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect GHSA-9px9-f7jw-fwhj in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for priest-runner, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-9px9-f7jw-fwhj if there is no patch (or I can't update yet)?

Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Is GHSA-9px9-f7jw-fwhj actively exploited in the wild?

No public exploit code has been indexed for GHSA-9px9-f7jw-fwhj yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-9px9-f7jw-fwhj published, and has it been updated?

GHSA-9px9-f7jw-fwhj was published on September 3, 2020 and was last updated on August 31, 2020. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

Command Injection in priest-runnerGHSA-9px9-f7jw-fwhj

GHSA-9px9-f7jw-fwhj is a remote code execution vulnerability in priest-runner. No vendor fix is recorded yet; mitigation options are listed below.

Published

Sep 3, 2020

Updated

Aug 31, 2020

Affected

1 pkg

Patched

None yet

Exploits

None indexed

Exploitation data as of Aug 31, 2020 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

0other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

priest-runnernpm

55downloads / week

Description

All versions of priest-runner are vulnerable to Command Injection. The package fails to sanitize input and passes it directly to a spawn call, which may allow attackers to execute arbitrary code in the system. The PriestController.prototype.createChild function is vulnerable since the spawn parameters come from a POST request body.

Recommendation

No fix is currently available. Consider using an alternative package until a fix is made available.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
📦npm	`priest-runner`	≥ 0.0.0	No fix

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for priest-runner, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of priest-runner has shipped for GHSA-9px9-f7jw-fwhj yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Frequently Asked Questions

All versions of `priest-runner` are vulnerable to Command Injection. The package fails to sanitize input and passes it directly to a `spawn` call, which may allow attackers to execute arbitrary code in the system. The `PriestController.prototype.createChild ` function is vulnerable since the `spawn` parameters come from a POST request body. ## Recommendation No fix is currently available. Consider using an alternative package until a fix is made available.

O3 Security · Impact-Aware SCA

Is GHSA-9px9-f7jw-fwhj in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works