CVE-2022-41142
SQLi in Centreon 22.04.2
Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2022-41142 is a high-severity SQL Injection (CWE-89) vulnerability in Centreon Centreon. Its CVSS base score is 8.8 (High).
Operationally, ranked in the top 0.3% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to AC-6 (Least Privilege) and SI-10 (Information Input Validation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
This vulnerability is a SQL injection issue tracked as CWE-89 that affects Centreon. It stems from insufficient validation of user-supplied input when handling requests to configure poller resources, allowing the input to be used directly in constructing SQL queries. The flaw was originally reported as ZDI-CAN-18304 and carries a CVSS 3.1 score of 8.8.
Authentication is required to exploit the issue. A remote attacker with valid low-privileged credentials can send crafted requests to the poller configuration component and escalate to full administrator privileges on the affected Centreon installation.
Public references point to the Zero Day Initiative advisory ZDI-22-1326 and Centreon’s security policy page, which typically direct users to apply vendor-supplied updates that address the input-handling flaw.
EPSS scores for the CVE rose from a low baseline to a peak of 0.4989, indicating that exploitation interest increased after disclosure.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2022-44383
Vulnerability Data
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 configure poller resources. The issue results from the lack of…
more
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-18304.
- CWE(s)
Related Threats
Likely ATT&CK TechniquesAI
Techniques this vulnerability likely enables, inferred from its description, weakness type, and attributed-actor tradecraft. Confidence is per-technique.
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
Mitigating Controls (NIST 800-53 r5) AI
Directly requires validation of user-supplied input before it is used to construct SQL queries, blocking the exact flaw exploited in the poller resource configuration path.
Enforces least privilege so that even an authenticated low-privileged account cannot reach or abuse the administrative SQL paths that enable escalation.
Requires the system to enforce authorized access decisions on every request, preventing the crafted SQL statements from bypassing intended privilege boundaries.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly target injection flaws during coding and review so largely prevent CWE-89 introduction, yet the single broad outcome leaves residual risk from incomplete neutralization techniques or missed edge cases.
Training raises developer awareness of SQLi risks and can reduce introduction likelihood (partial) but removes none of the actual coding flaw's risk by itself since technical neutralization is still required.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
The same secure-coding and static-analysis activities surface missing neutralization of SQL metacharacters before the system is accepted.
Early warnings and shared best-practice information help organizations apply the latest remediation techniques against SQL-injection vulnerabilities.
Threat-intelligence feeds that surface new SQL-injection campaigns enable rapid updates to query-construction defenses and detection signatures before exploitation occurs.
Secure-coding rules and security testing phases mandate the use of parameterized queries or equivalent escaping, preventing the construction of dynamic SQL statements from untrusted input.
Language-specific secure coding rules, peer review and SAST together prevent the construction of SQL statements from untrusted data without proper parameterization or escaping.