dbcve.org
Centreon WebApplication · Centreon

CVE-2024-23119

HIGH · 8.8 CVSS v3.0 Published 2024-04-01
Fix available
A fix is available. Upgrade to 22.04.19 / 22.10.17 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Centreon insertGraphTemplate 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 insertGraphTemplate 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-22339.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis
How this class of weakness works · CWE-89

User input is woven into a database query, letting an attacker rewrite the query's logic. From there they can read, alter, or destroy data — frequently the entire database. The reliable fix is parameterised queries (prepared statements), so input is always treated as data and never as SQL.

General guidance for the sql injection class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Centreon WebApplication
Affected:< 22.04.19>= 22.10.2, < 22.10.17>= 23.04.0, < 23.04.13>= 23.10.0, < 23.10.5

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 22.04.19 / 22.10.17 / 23.04.13 or later
Fixed in 22.04.1922.10.1723.04.13
Vendor patch www.zerodayinitiative.com →
Recommended fix High confidence

Upgrade to Centreon 23.10.5 (or the latest available version in your respective branch: 22.04.19, 22.10.17, or 23.04.13)

  1. 1. Identify the currently installed Centreon Web version by checking the 'Administration' > 'Parameters' > 'About' section in the Centreon web interface.
  2. 2. Based on the installed version line, plan the upgrade to the corresponding fixed version:
  3. - If using Centreon 22.04.x, upgrade to version 22.04.19 or later
  4. - If using Centreon 22.10.x, upgrade to version 22.10.17 or later
  5. - If using Centreon 23.04.x, upgrade to version 23.04.13 or later
  6. - If using Centreon 23.10.x, upgrade to version 23.10.5 or later
  7. 3. Before upgrading, perform a full backup of the Centreon database and configuration files.
  8. 4. Follow the official Centreon upgrade documentation for your specific version path.
Caveat Standard Centreon upgrade risks apply - test in staging first, backup before upgrade, and verify custom configurations/plugins work post-upgrade

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-23119 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-23119 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data