dbcve.org
CentreonApplication

CVE-2022-42426

HIGH · 8.8 CVSS v3.1 Published 2023-03-29
Fix available
A fix is available. Upgrade to 21.04.19 / 21.10.11 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
This vulnerability allows remote attackers to escalate privileges on affected installations of Centreon. Authentication is required to exploit this vulnerability. The specific flaw exists within the handling of requests to modify poller broker configuration. 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 escalate privileges to the level of an administrator. Was ZDI-CAN-18554.

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

An authenticated SQL injection vulnerability in Centreon's poller broker configuration module allows attackers to manipulate SQL queries through unsanitized user-supplied strings, enabling privilege escalation to administrator level.

MitigationApply Centreon security patches immediately. Until patched, restrict access to the poller broker configuration interface to trusted administrators only and monitor for suspicious SQL-like patterns in requests.

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
CentreonApplication
Affected:< 21.04.19>= 21.10.0, < 21.10.11>= 22.04.0, < 22.04.6

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 installed Centreon version
    Locate the Centreon version number through the web interface (typically in Help > About or Administration > Parameters > About) or via the system package manager (e.g., rpm -qa centreon-web, dpkg -l centreon-web)
    Affected if Version falls outside the safe ranges: 21.04.19 or higher, 21.10.11 or higher, or 22.04.6 or higher
  2. Confirm poller broker configuration module access
    Log into Centreon and navigate to the poller broker configuration interface (typically found under Configuration > Pollers > Broker Configuration)
    Affected if The module is accessible to your user account without additional restrictions
  3. Verify user authentication context
    Determine whether your account has any level of access to the Centreon web interface, as this vulnerability requires authenticated access
    Affected if You can authenticate to Centreon with any valid user account

You are affected if your Centreon version is below 21.04.19, between 21.10.0-21.10.10, or between 22.04.0-22.04.5 AND you have authenticated access to the poller broker configuration module.

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 21.04.19 / 21.10.11 / 22.04.6 or later
Fixed in 21.04.1921.10.1122.04.6
Interim mitigation

Apply Centreon security patches immediately. Until patched, restrict access to the poller broker configuration interface to trusted administrators only and monitor for suspicious SQL-like patterns in requests.

Recommended fix Moderate confidence

Centreon 21.04.19, 21.10.11, or 22.04.6 (or later stable release)

  1. 1. Back up your Centreon installation and database before proceeding with any upgrade.
  2. 2. Determine your current Centreon version by checking the About page in the Centreon web interface.
  3. 3. If running Centreon < 21.04.19, upgrade to version 21.04.19 or later.
  4. 4. If running Centreon >= 21.10.0 and < 21.10.11, upgrade to version 21.10.11 or later.
  5. 5. If running Centreon >= 22.04.0 and < 22.04.6, upgrade to version 22.04.6 or later.
  6. 6. After upgrade, verify the Centreon web interface is functional and test that the poller broker configuration save functionality works correctly.
  7. 7. Review user accounts and privilege assignments to confirm no unauthorized privilege escalation occurred.

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

Fix this in Centreon Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,360
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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