dbcve.org
Centreon WebApplication · Centreon

CVE-2024-39841

HIGH · 8.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 →
94/100
Remediation priority · Urgent
Remotely reachable 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 service configuration 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 service configuration functionality allows authenticated attackers to inject malicious SQL queries, potentially leading to unauthorized data access or manipulation. The vulnerability affects multiple version branches (24.04.x, 23.10.x, 23.04.x, 22.10.x) prior to their respective patched releases.

MitigationApply vendor-supplied patches by upgrading Centreon Web to version 24.04.3, 23.10.13, 23.04.19, or 22.10.23 or later. Alternatively, restrict administrative access to the service configuration interface until patching can be completed.

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
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 checks

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

  1. Identify Centreon Web installation and version
    Locate the Centreon Web application and determine its installed version number. This is typically found in the software's about page, version information file, or command-line interface using 'centreon -V' or similar. Compare the version to the affected ranges: 22.10.0 to 22.10.22, 23.04.0 to 23.04.18, 23.10.0 to 23.10.12, and 24.04.0 to 24.04.2.
    Affected if The installed version falls within any of the affected version ranges (22.10.x before 22.10.23, 23.04.x before 23.04.19, 23.10.x before 23.10.13, or 24.04.x before 24.04.3).
  2. Verify access to service configuration functionality
    Confirm whether the Centreon Web service configuration interface is accessible within the current deployment. This involves checking user role permissions and the presence of the service configuration module in the web interface navigation.
    Affected if The service configuration module is available and accessible to users with authenticated access to Centreon Web.
  3. Check authentication mechanisms and user access controls
    Review the authentication configuration and user privilege settings for Centreon Web. Identify accounts that have access to the service configuration area and evaluate whether untrusted or low-privilege users can reach this functionality.
    Affected if Untrusted or low-privilege authenticated users have access to the service configuration interface.

You are affected if Centreon Web is installed at a version lower than 22.10.23, 23.04.19, 23.10.13, or 24.04.3 AND the service configuration feature is accessible to authenticated users 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

Apply vendor-supplied patches by upgrading Centreon Web to version 24.04.3, 23.10.13, 23.04.19, or 22.10.23 or later. Alternatively, restrict administrative access to the service configuration interface until patching can be completed.

Recommended fix High confidence

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

  1. 1. Identify your current Centreon Web version by checking the 'Administration > Parameters > About' page in the Centreon web interface
  2. 2. Create a complete backup of your Centreon database and configuration files before proceeding with the upgrade
  3. 3. Download the appropriate fixed version from the official Centreon repository or download centreon.com: 22.10.23 for 22.10.x users, 23.04.19 for 23.04.x users, 23.10.13 for 23.10.x users, or 24.04.3 for 24.04.x users
  4. 4. Follow the official Centreon upgrade documentation for your specific version to apply the security update
  5. 5. After upgrade, verify the version number matches the expected fixed release in 'Administration > Parameters > About'
  6. 6. Test the service configuration functionality to confirm the SQL injection vulnerability is resolved
  7. 7. Review Centreon logs to ensure no errors occurred during the upgrade process
Caveat Standard Centreon upgrade risks apply - ensure database and configuration backups before upgrading; test in staging if possible

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

Fix this in Centreon Web Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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