How severe is GHSA-qcff-ffx3-m25c?

No CVSS score has been assigned to GHSA-qcff-ffx3-m25c yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-qcff-ffx3-m25c?

GHSA-qcff-ffx3-m25c affects the following packages: meta-git (npm). Ecosystems affected: npm.

How do I fix GHSA-qcff-ffx3-m25c?

No patched version of meta-git has shipped for GHSA-qcff-ffx3-m25c 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-qcff-ffx3-m25c in my npm dependencies?

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

How do I mitigate GHSA-qcff-ffx3-m25c 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-qcff-ffx3-m25c actively exploited in the wild?

No public exploit code has been indexed for GHSA-qcff-ffx3-m25c 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-qcff-ffx3-m25c published, and has it been updated?

GHSA-qcff-ffx3-m25c was published on September 4, 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 meta-gitGHSA-qcff-ffx3-m25c

GHSA-qcff-ffx3-m25c is a remote code execution vulnerability in meta-git. No vendor fix is recorded yet; mitigation options are listed below.

Published

Sep 4, 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.

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

meta-gitnpm

999downloads / week

Description

All versions of meta-git are vulnerable to Command Injection. The package fails to sanitize input and passes it directly to an exec call, which may allow attackers to execute arbitrary code in the system. The clone command is vulnerable through the branch name.

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	`meta-git`	≥ 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 meta-git, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of meta-git has shipped for GHSA-qcff-ffx3-m25c 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 `meta-git` are vulnerable to Command Injection. The package fails to sanitize input and passes it directly to an `exec` call, which may allow attackers to execute arbitrary code in the system. The `clone` command is vulnerable through the branch name. ## Recommendation No fix is currently available. Consider using an alternative package until a fix is made available.

O3 Security · Impact-Aware SCA

Is GHSA-qcff-ffx3-m25c in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works