dbcve.org
Centreon WebApplication · Centreon

CVE-2024-33854

CRITICAL · 9.1 CVSS v3.1 Published 2024-08-23
Fix available
A fix is available. Upgrade to 22.10.23 / 23.04.19 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
A SQL Injection vulnerability exists in the Graph Template component in Centreon Web 24.04.x before 24.04.3, 23.10.x before 23.10.13, 23.04.x before 23.04.19, and 22.10.x before 22.10.23.

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 · high confidence

A SQL Injection vulnerability exists in the Graph Template component of Centreon Web. The vulnerability affects multiple version branches (24.04.x before 24.04.3, 23.10.x before 23.10.13, 23.04.x before 23.04.19, and 22.10.x before 22.10.23). The critical CVSS score of 9.1 indicates potential for severe impact including unauthorized data access or database compromise.

MitigationUpgrade Centreon Web to the patched versions (24.04.3, 23.10.13, 23.04.19, or 22.10.23) to remediate the SQL injection vulnerability in the Graph Template component.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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.10.0, < 22.10.23>= 23.04.0, < 23.04.19>= 23.10.0, < 23.10.13>= 24.04.0, < 24.04.3

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Centreon Web version
    Locate and read the Centreon version file or use the Centreon command-line interface to retrieve the installed version number (typically found in /etc/centreon/version or via 'centreon -V' or in the web interface footer)
    Affected if The installed version falls within any of these ranges: 22.10.0-22.10.22, 23.04.0-23.04.18, 23.10.0-23.10.12, or 24.04.0-24.04.2
  2. Confirm Graph Template module is accessible
    Verify that the Graph Template functionality is enabled and accessible in the Centreon web interface (typically under Monitoring > Graphics > Graph Templates, or similar navigation path)
    Affected if The Graph Template feature is enabled and exposed to the user interface, making it reachable for potential exploitation
  3. Check web server access logs for SQL injection patterns
    Review web server access logs (Apache or Nginx) for requests to Graph Template endpoints containing suspicious SQL patterns such as UNION SELECT, OR 1=1, or other SQL metacharacters in parameters
    Affected if Log analysis reveals any SQL injection attempt patterns directed at Graph Template URLs

You are affected if your installed Centreon Web version is lower than 22.10.23, 23.04.19, 23.10.13, or 24.04.3 AND the Graph Template feature is accessible in your environment.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.10.23 / 23.04.19 / 23.10.13 or later
Fixed in 22.10.2323.04.1923.10.13
Interim mitigation

Upgrade Centreon Web to the patched versions (24.04.3, 23.10.13, 23.04.19, or 22.10.23) to remediate the SQL injection vulnerability in the Graph Template component.

Recommended fix High confidence

Upgrade to Centreon Web 22.10.23, 23.04.19, 23.10.13, or 24.04.3 (or later) - recommended: 24.04.3 or latest stable release

  1. 1. Back up the Centreon database and configuration files before proceeding with any upgrade.
  2. 2. Review the official Centreon upgrade documentation for your current installation method (yum/dnf, apt, or source).
  3. 3. Foryum/dnf-based systems: Run 'dnf update centreon-web' or 'yum update centreon-web' to install the latest available package.
  4. 4. For apt-based systems: Run 'apt-get update && apt-get install centreon-web' to install the latest available package.
  5. 5. After package installation, run the Centreon upgrade wizard: php /usr/share/centreon/bin/centreon -u $USER -p $PASSWORD (or use the web interface).
  6. 6. Clear any caches and restart the Centreon services: systemctl restart centreon systemctl restart centengine.
  7. 7. Verify the upgrade was successful by checking the Centreon version in 'Administration > Extensions > Broker' or by running 'rpm -q centreon-web'.
  8. 8. Confirm the SQL injection vulnerability is resolved by verifying the Graph Template component functions correctly.
Caveat Review Centreon release notes for your target version; major version jumps may require testing in a staging environment due to potential API or configuration changes

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

Fix this in Centreon Web Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,392.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-33854 — 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-33854 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