dbcve.org
Centreon WebApplication · Centreon

CVE-2024-32501

CRITICAL · 9.8 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 updateServiceHost functionality 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

SQL injection vulnerability in Centreon Web's updateServiceHost function allows attackers to inject malicious SQL queries via unsanitized input, potentially enabling unauthorized database access, data exfiltration, or complete system compromise.

MitigationUpgrade Centreon Web to version 24.04.3, 23.10.13, 23.04.19, or 22.10.23 or later. If immediate patching is not feasible, restrict network access to the Centreon management interface and deploy WAF rules to block SQL injection attempts.

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
High

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

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. Determine installed Centreon Web version
    Check the Centreon about page in the web interface (Help > About) or run: grep -r 'CENTREON_VERSION' /usr/share/centreon/src/ 2>/dev/null | head -5
    Affected if version falls within 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. Verify updateServiceHost function exists
    Search for the function in the Centreon source code: grep -r 'updateServiceHost' /usr/share/centreon/www/ 2>/dev/null | grep -i function
    Affected if function exists in the codebase, indicating the vulnerable component is present
  3. Confirm web management interface accessibility
    Determine if the Centreon web interface is reachable over network: curl -s -o /dev/null -w '%{http_code}' http://localhost/centreon/ or check firewall rules for port 80/443
    Affected if the Centreon web interface is network-accessible to untrusted users, allowing the SQL injection attack surface to be reachable

The environment is affected if the installed Centreon Web version is within any of the vulnerable ranges and the web management interface is accessible to potential attackers.

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 version 24.04.3, 23.10.13, 23.04.19, or 22.10.23 or later. If immediate patching is not feasible, restrict network access to the Centreon management interface and deploy WAF rules to block SQL injection attempts.

Recommended fix High confidence

Centreon Web 22.10.23, 23.04.19, 23.10.13, or 24.04.3 (depending on your current major version)

  1. 1. Identify the currently installed Centreon Web version by checking the /usr/share/centreon/version.inc or Centreon web interface (Administration > Parameters > About)
  2. 2. For Centreon Web 22.10.x versions: Upgrade to version 22.10.23 or later
  3. 3. For Centreon Web 23.04.x versions: Upgrade to version 23.04.19 or later
  4. 4. For Centreon Web 23.10.x versions: Upgrade to version 23.10.13 or later
  5. 5. For Centreon Web 24.04.x versions: Upgrade to version 24.04.3 or later
  6. 6. Use the official Centreon upgrade procedure: Stop Centreon services (centreon, httpd), backup the database and /etc/centreon directory, then install the new RPM/DEB packages
  7. 7. After upgrade, clear browser cache and verify the Centreon web interface is functional
  8. 8. Validate that the updateServiceHost functionality works correctly and the SQL injection vulnerability is resolved
Caveat Review Centreon release notes for any configuration or compatibility changes between your current and target version before upgrading

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
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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