CVE-2024-5723
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 · uneditedCentreon updateServiceHost 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 updateServiceHost 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 apache user. Was ZDI-CAN-23294.
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 · moderate confidenceThis is a SQL Injection vulnerability in Centreon's `updateServiceHost` function where user-supplied input is not properly validated before being used in SQL query construction. An authenticated attacker can inject malicious SQL statements to achieve remote code execution in the context of the apache user.
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< 22.04.24>= 22.10.0, < 22.10.22>= 23.04.0, < 23.04.18>= 23.10.0, < 23.10.12CVSS 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.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Locate Centreon installation and versionCheck the Centreon version file typically located at /usr/share/centreon/src/version.php or /opt/centreon/www/version.txt, or query the database: SELECT value FROM options WHERE key_value = 'version' LIMIT 1;Affected if The installed version matches any of these ranges: < 22.04.24, >= 22.10.0 and < 22.10.22, >= 23.04.0 and < 23.04.18, or >= 23.10.0 and < 23.10.12
-
Identify the vulnerable function fileLocate the file containing the updateServiceHost function. This is typically in the Centreon GPL API or service configuration module. Search for: grep -r 'function updateServiceHost' /usr/share/centreon/ 2>/dev/nullAffected if The updateServiceHost function exists and the code directly uses user input in SQL queries without parameterized binding (look for variables like $host_id or $service_id concatenated into SQL strings)
-
Verify authentication is required for exploitationConfirm whether the updateServiceHost function is protected by Centreon's authentication mechanism. Check the API endpoint or controller that calls this function for session/token validation.Affected if The function is accessible to authenticated users (any user with valid Centreon credentials can reach the vulnerable code)
-
Check for indicators of exploitationReview web server access logs for unusual SQL patterns in requests to Centreon's API endpoints. Look for: grep -E "(UNION|SELECT|INSERT|UPDATE|DELETE).*FROM" /var/log/apache2/centreon*.log or similar log paths.Affected if Log entries show SQL injection patterns in API calls that correspond to the updateServiceHost function parameters
You are affected if Centreon Web is installed with a version that falls within the vulnerable ranges AND the updateServiceHost function is accessible to authenticated users without additional security controls.
Generated from the published advisory. Verify against your own configuration.
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 · scoped22.04.2422.10.2223.04.18
Apply the Centreon vendor patch when available. Until then, restrict administrative access to trusted users only and implement input validation with parameterized queries in the vulnerable function.
Upgrade to the latest version in your respective branch: 22.04.24+, 22.10.22+, 23.04.18+, or 23.10.12+
- 1. Back up the Centreon database and configuration files before proceeding with any upgrade.
- 2. Review the Centreon upgrade documentation for your current version branch.
- 3. For Centreon 22.04.x users: Upgrade to version 22.04.24 or later.
- 4. For Centreon 22.10.x users: Upgrade to version 22.10.22 or later.
- 5. For Centreon 23.04.x users: Upgrade to version 23.04.18 or later.
- 6. For Centreon 23.10.x users: Upgrade to version 23.10.12 or later.
- 7. After upgrade, verify the updateServiceHost functionality works correctly and test that SQL injection is no longer possible.
- 8. Review Centreon access logs and audit logs for any signs of exploitation attempts prior to the upgrade.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-5723 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-5723 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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