How severe is GHSA-22v7-v3mj-pm8r?

GHSA-22v7-v3mj-pm8r has a CVSS score of 8.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-22v7-v3mj-pm8r?

GHSA-22v7-v3mj-pm8r affects the following packages: centreon/centreon (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-22v7-v3mj-pm8r?

Update centreon/centreon to 22.10.15 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-22v7-v3mj-pm8r is resolved across your whole dependency graph.

How do I detect GHSA-22v7-v3mj-pm8r in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for centreon/centreon. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-22v7-v3mj-pm8r if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-22v7-v3mj-pm8r?

O3 pinpoints whether GHSA-22v7-v3mj-pm8r is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-22v7-v3mj-pm8r actively exploited in the wild?

No public exploit code has been indexed for GHSA-22v7-v3mj-pm8r 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 type of vulnerability is GHSA-22v7-v3mj-pm8r?

GHSA-22v7-v3mj-pm8r is classified as SQL Injection (CWE-89). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-22v7-v3mj-pm8r published, and has it been updated?

GHSA-22v7-v3mj-pm8r was published on April 2, 2024 and was last updated on April 2, 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

GHSA-22v7-v3mj-pm8r

HIGH

GHSA-22v7-v3mj-pm8r is a high-severity (CVSS 8.8) SQL Injection vulnerability in centreon/centreon. O3 Security confirms whether GHSA-22v7-v3mj-pm8r is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Centreon updateDirectory SQL Injection Remote Code Execution Vulnerability

Also known asCVE-2024-0637

Published

Apr 2, 2024

Updated

Apr 2, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

🐘centreon/centreon

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

The specific flaw exists within the updateDirectory function. The issue results from the lack of proper validation of a user-supplied string before using it to construct SQL queries. An attacker can leverage this vulnerability to execute code in the context of the service account. Was ZDI-CAN-22294.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`centreon/centreon`	all versions	22.10.15

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for centreon/centreon. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update centreon/centreon to 22.10.15 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-22v7-v3mj-pm8r is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-22v7-v3mj-pm8r is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-22v7-v3mj-pm8r. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Centreon updateDirectory SQL Injection Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of Centreon. Authentication is required to exploit this vulnerability. The specific flaw exists within the updateDirectory function. The issue results from the lack of proper validation of a user-supplied string before using it to construct SQL queries. An attacker can leverage this vulnerability to execute code in the context of the service account. Was ZDI-CAN-22294.

O3 Security · Impact-Aware SCA

Is GHSA-22v7-v3mj-pm8r in your dependencies?

O3 detects GHSA-22v7-v3mj-pm8r across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works