How severe is GHSA-23f2-vgr6-fwv7?

No CVSS score has been assigned to GHSA-23f2-vgr6-fwv7 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-23f2-vgr6-fwv7?

GHSA-23f2-vgr6-fwv7 affects the following packages: librenms/librenms (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-23f2-vgr6-fwv7?

Update librenms/librenms to 22.4.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-23f2-vgr6-fwv7 is resolved across your whole dependency graph.

How do I detect GHSA-23f2-vgr6-fwv7 in my Packagist dependencies?

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

How do I mitigate GHSA-23f2-vgr6-fwv7 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-23f2-vgr6-fwv7 actively exploited in the wild?

No public exploit code has been indexed for GHSA-23f2-vgr6-fwv7 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.

What is the EPSS score for GHSA-23f2-vgr6-fwv7?

GHSA-23f2-vgr6-fwv7 has an EPSS (Exploit Prediction Scoring System) score of 1.7%, placing it in the 78th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-23f2-vgr6-fwv7?

GHSA-23f2-vgr6-fwv7 is classified as CWE-77 (CWE-77). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-23f2-vgr6-fwv7 published, and has it been updated?

GHSA-23f2-vgr6-fwv7 was published on June 3, 2022 and was last updated on November 28, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

Not in CISA KEV

Command injection in librenmsGHSA-23f2-vgr6-fwv7

Fix: librenms/librenms#13932

GHSA-23f2-vgr6-fwv7 is a CWE-77 vulnerability in librenms/librenms. A fix is available for librenms/librenms — see the affected versions and patch details below.

Also known asCVE-2022-29712

Published

Jun 3, 2022

Updated

Nov 28, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 11, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs78th percentile — riskier than 78% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐘librenms/librenms

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

LibreNMS v22.3.0 was discovered to contain multiple command injection vulnerabilities via the service_ip, hostname, and service_param parameters.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`librenms/librenms`	all versions	22.4.0`composer require librenms/librenms:^22.4.0`

Affected Products

1 product · 1 configurations

Application

librenmslibrenms

1 version

22.3.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for librenms/librenms, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update librenms/librenms to 22.4.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-23f2-vgr6-fwv7 is resolved across your whole dependency graph.
Workarounds
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

LibreNMS v22.3.0 was discovered to contain multiple command injection vulnerabilities via the service_ip, hostname, and service_param parameters.

O3 Security · Impact-Aware SCA

Is GHSA-23f2-vgr6-fwv7 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works