dbcve.org
Centreon WebApplication · Centreon

CVE-2024-33853

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 Timeperiod 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 Timeperiod component of Centreon Web, allowing unauthenticated attackers to inject malicious SQL queries. The vulnerability affects multiple supported version branches (24.04.x, 23.10.x, 23.04.x, 22.10.x) and is rated critical due to the potential for complete database compromise.

MitigationUpgrade Centreon Web to version 24.04.3, 23.10.13, 23.04.19, or 22.10.23 (or later) to patch the SQL Injection vulnerability in the Timeperiod 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 the Centreon Web installation directory or package manager and retrieve the installed version number (for example, check the about page in the Centreon web interface, examine Centreon package version with your package manager, or look for version files in the Centreon installation directory)
    Affected if The installed version falls within any of these ranges: 22.10.0 to 22.10.22, 23.04.0 to 23.04.18, 23.10.0 to 23.10.12, or 24.04.0 to 24.04.2
  2. Verify Timeperiod component is accessible
    Confirm that the Centreon web interface is reachable and the Timeperiod feature is enabled (the Timeperiod component is part of the Configuration > Users > Timeperiods menu in the Centreon web interface)
    Affected if The Centreon web interface is exposed and the Timeperiod component is accessible to unauthenticated users (the vulnerability is exploitable without authentication)
  3. Check web server access logs for Timeperiod requests
    Examine web server access logs (such as Apache or Nginx logs) for unusual or malformed requests to Timeperiod-related endpoints, looking for SQL injection patterns (for example, requests containing SQL operators like UNION, SELECT, or single quotes in parameters)
    Affected if Unusual SQL injection patterns are present in logs targeting Timeperiod endpoints, indicating potential exploitation attempts

The environment is affected if Centreon Web is running a version lower than 22.10.23, 23.04.19, 23.10.13, or 24.04.3 and the web interface with the Timeperiod component is accessible.

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) to patch the SQL Injection vulnerability in the Timeperiod component.

Recommended fix High confidence

Upgrade to Centreon Web 24.04.3 (or the latest 24.04.x release if newer) as the recommended stable version

  1. 1. Back up the Centreon database and configuration files before upgrading
  2. 2. Identify the current Centreon Web version (e.g., from Administration > Extensions > Manager or via command line)
  3. 3. For Centreon 24.04.x: Upgrade to version 24.04.3 or later
  4. 4. For Centreon 23.10.x: Upgrade to version 23.10.13 or later
  5. 5. For Centreon 23.04.x: Upgrade to version 23.04.19 or later
  6. 6. For Centreon 22.10.x: Upgrade to version 22.10.23 or later
  7. 7. Verify the upgrade was successful by checking the version in Administration > Extensions > Manager
  8. 8. Test the Timeperiod component functionality to ensure it works correctly post-upgrade
Caveat Standard Centreon upgrade risks apply - test in non-production first, ensure compatibility with existing plugins and extensions

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
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
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,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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