CVE-2024-55573
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 · uneditedAn issue was discovered in Centreon centreon-web 24.10.x before 24.10.3, 24.04.x before 24.04.9, 23.10.x before 23.10.19, 23.04.x before 23.04.24. A user with high privileges is able to inject SQL into the form used to create virtual metrics.
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 confidenceSQL injection vulnerability in Centreon centreon-web allows high-privilege users to inject malicious SQL through the virtual metrics creation form. The lack of proper input sanitization or parameterized queries in this specific form enables an attacker with elevated privileges to manipulate database queries.
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>= 23.04.0, < 23.04.24>= 23.10.0, < 23.10.19>= 24.04.0, < 24.04.9>= 24.10.0, < 24.10.3CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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.
-
Determine installed Centreon Web versionLog into Centreon web interface and navigate to Administration > About, or run command: rpm -q centreon-web-centreon or dpkg -l | grep centreon-webAffected if Version falls within any of these ranges: >= 23.04.0 and < 23.04.24, >= 23.10.0 and < 23.10.19, >= 24.04.0 and < 24.04.9, >= 24.10.0 and < 24.10.3
-
Verify virtual metrics feature accessCheck if the logged-in user has permission to access Monitoring > Virtual Metrics or the virtual metrics creation form in the web interface under Configuration > MetricsAffected if User with elevated privileges has access to virtual metrics creation form
-
Inspect user privilege levelIn Centreon, navigate to Administration > Users > [select user] and check the ACL (Access Control List) applied to the user accountAffected if User is assigned to an ACL group granting write access to virtual metrics configuration
-
Review database query loggingEnable and review PostgreSQL or MySQL query logs for the Centreon database. Look for unusual SQL patterns in INSERT/UPDATE statements related to virtual metrics tables (virtual_metrics)Affected if Suspicious SQL injection patterns appear in database query logs involving virtual metrics tables
You are affected if your Centreon Web version is within any of the vulnerable ranges AND high-privilege users have access to the virtual metrics creation form.
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 · scoped23.04.2423.10.1924.04.9
Apply vendor patches by upgrading centreon-web to version 24.10.3, 24.04.9, 23.10.19, or 23.04.24 or later. Until patched, limit virtual metrics creation to absolutely trusted administrative users only and monitor database query logs for suspicious activity.
Upgrade to Centreon Web 23.04.24 (or later), 23.10.19 (or later), 24.04.9 (or later), or 24.10.3 (or later) depending on your current branch
- 1. Identify the currently installed Centreon Web version by checking the Centreon about page or using: cat /usr/share/centreon/.env | grep version
- 2. Determine which version branch you are running (23.04.x, 23.10.x, 24.04.x, or 24.10.x)
- 3. For version 23.04.x: Upgrade to Centreon Web 23.04.24 or later
- 4. For version 23.10.x: Upgrade to Centreon Web 23.10.19 or later
- 5. For version 24.04.x: Upgrade to Centreon Web 24.04.9 or later
- 6. For version 24.10.x: Upgrade to Centreon Web 24.10.3 or later
- 7. Download the appropriate upgrade from the official Centreon repository or support portal
- 8. Follow the standard Centreon upgrade procedure documented in the official Centreon upgrade guide
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-55573 — 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-55573 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