dbcve.org
CentreonApplication

CVE-2022-34871

HIGH · 7.2 CVSS v3.1 Published 2022-08-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
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 configuration of poller resources. 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-16335.

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's poller resource configuration allows authenticated remote attackers to escalate privileges to administrator level by injecting malicious SQL through unvalidated user-supplied strings before SQL query construction.

MitigationApply vendor patches for CVE-2022-34871 and implement proper input validation with parameterized queries for all poller configuration parameters.

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.10.2

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

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

  1. Identify Centreon version
    Locate the Centreon installation and determine its version number. Common methods include checking the web interface 'About' page, package manager, or configuration files.
    Affected if The installed version is exactly 21.10.2 (Centreon Centreon)
  2. Confirm poller configuration module is accessible
    Verify that the Centreon poller resource configuration feature is enabled and accessible within the installation. Check user role permissions for accessing poller configuration menus.
    Affected if The poller configuration module is available to authenticated users without additional security restrictions
  3. Verify authenticated user access exists
    Confirm that user accounts exist with valid login credentials to Centreon. The SQL injection requires an authenticated session.
    Affected if There is at least one active authenticated user account that can access the poller configuration interface

A user is affected if they are running Centreon version 21.10.2 with the poller configuration feature 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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patches for CVE-2022-34871 and implement proper input validation with parameterized queries for all poller configuration parameters.

Recommended fix Moderate confidence

Centreon 21.10.3 or later LTS version

  1. 1. Verify current Centreon version by checking the About section in the web interface or running 'rpm -q centreon'
  2. 2. Backup the Centreon database and configuration files before proceeding with any upgrade
  3. 3. Download the latest Centreon 21.10.x LTS version from the official Centreon repository (packages.centreon.com)
  4. 4. Stop Centreon services: 'systemctl stop centreon' and 'systemctl stop centreon-engine'
  5. 5. Upgrade Centreon packages using your package manager (yum or apt depending on OS)
  6. 6. Run the Centreon upgrade wizard via web interface at http://<your-server>/centreon/
  7. 7. Restart Centreon services: 'systemctl start centreon' and verify all services are running
  8. 8. Log in and verify the poller configuration functionality works correctly
Caveat Minor version upgrades within 21.10.x typically preserve configuration; always backup before upgrading

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

Fix this in Centreon Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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