CVE-2022-42429
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 · uneditedThis 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-18557.
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 confidenceThis is a SQL injection vulnerability in Centreon's poller broker configuration module. An authenticated attacker can exploit improper input validation of user-supplied strings before they are used in SQL query construction, allowing privilege escalation to administrator level.
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< 21.04.19>= 21.10.0, < 21.10.11>= 22.04.0, < 22.04.6CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Centreon versionLog into the Centreon web interface and navigate to Administration > Parameters > About, or check the installed package version using the command: cat /usr/share/centreon/version.txt or rpm -q centreonAffected if The installed version falls within these vulnerable ranges: < 21.04.19, >= 21.10.0 and < 21.10.11, or >= 22.04.0 and < 22.04.6
-
Confirm poller broker configuration module accessNavigate to Configuration > Pollers > Broker Configuration in the Centreon web interface. Verify this module is visible and accessible to your user accountAffected if The poller broker configuration module is present and accessible without being explicitly disabled
-
Verify authentication is enabledCheck that Centreon user authentication is active by attempting to log in or reviewing the authentication configuration in Administration > Authentication > Authentication sourcesAffected if Centreon authentication is enabled, which is the default configuration and required for exploitation
-
Check for unauthorized administrator accountsReview user accounts in Administration > Users > Contacts/Users and check for any unexpected administrator-level accounts that may indicate prior exploitationAffected if New or unrecognized administrator accounts exist that were not created by your organization
You are affected if your Centreon version is 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.
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 · scoped21.04.1921.10.1122.04.6
Apply vendor-supplied patch for CVE-2022-42429. If no patch available, implement strict input validation and convert all database queries to parameterized statements to eliminate SQL injection vectors.
21.04.19 or later (21.04.x line), 21.10.11 or later (21.10.x line), or 22.04.6 or later (22.04.x line)
- 1. Identify the currently installed Centreon version by checking the 'Administration' > 'Parameters' > 'About' page in the Centreon web interface
- 2. Based on your current version branch, plan an upgrade to the minimum fixed version: If using 21.04.x, upgrade to 21.04.19 or later; If using 21.10.x, upgrade to 21.10.11 or later; If using 22.04.x, upgrade to 22.04.6 or later
- 3. Before upgrading, perform a complete backup of the Centreon database using command: `mysqldump -u centreon -p centreon > centreon_backup_$(date +%Y%m%d).sql`
- 4. Before upgrading, back up the Centreon configuration files in /etc/centreon/ and /etc/httpd/conf.d/
- 5. Follow the official Centreon upgrade documentation for your distribution to install the target version
- 6. After upgrade, verify the Centreon web interface is functional and check that the version displayed matches the expected fixed version
- 7. Test that authenticated users can no longer exploit the poller broker configuration to perform SQL injection attacks
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,720.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-42429 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-42429 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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