dbcve.org
CentreonApplication

CVE-2022-42425

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
High EPSS 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-18555.

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

This is a SQL injection vulnerability in Centreon IT monitoring platform. An authenticated attacker can modify poller broker configuration parameters containing unsanitized user input to inject malicious SQL queries, potentially gaining administrator privileges.

MitigationApply vendor patches for CVE-2022-42425 and implement parameterized queries/ input validation for all database operations in the poller broker configuration module.

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
    Check the Centreon web interface at Administration > Parameters > About, or run 'rpm -qa | grep centreon' or 'cat /usr/share/centreon/VERSION' on the server
    Affected if The installed version is < 21.04.19, OR >= 21.10.0 and < 21.10.11, OR >= 22.04.0 and < 22.04.6
  2. Verify poller broker configuration module access
    Log into Centreon web interface and navigate to Configuration > Pollers > Broker configuration, or check if the /centreon/api endpoint responds for broker configuration API calls
    Affected if The user has access to the poller broker configuration module without additional network restrictions
  3. ConfirmCentreon authentication is enabled
    Check Administration > Authentication > Authentication sources in the web interface, or inspect the $conf_centreon array in /etc/centreon/conf.php for authentication provider settings
    Affected if External authentication (LDAP/AD) is configured or local user authentication is active - since the attacker requires valid credentials

You are affected if your Centreon version falls within the vulnerable ranges AND the poller broker configuration module is accessible to authenticated users.

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 vendor patches for CVE-2022-42425 and implement parameterized queries/ input validation for all database operations in the poller broker configuration module.

Recommended fix Moderate confidence

Minimum: 21.04.19, 21.10.11, or 22.04.6 (choose the appropriate branch for your environment)

  1. Backup your Centreon database before proceeding with the upgrade
  2. Review the Centreon upgrade documentation for your current version path
  3. Ensure you have valid backups of configuration files and the database
  4. Upgrade Centreon to version 21.04.19 or later if on the 21.04.x line
  5. Upgrade Centreon to version 21.10.11 or later if on the 21.10.x line
  6. Upgrade Centreon to version 22.04.6 or later if on the 22.04.x line
  7. After upgrade, verify the poller broker configuration functionality works correctly
  8. Test that authentication and privilege escalation protections are functioning
Caveat Always backup database and configuration before upgrading; test in staging first

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

Fix this in Centreon Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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