CVE-2024-39843
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 · uneditedA SQL injection vulnerability in Centreon 24.04.2 allows a remote high-privileged attacker to execute arbitrary SQL command via create user form inputs.
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 · moderate confidenceSQL injection vulnerability in Centreon 24.04.2 allows authenticated high-privilege users to execute arbitrary SQL commands through unsanitized inputs in the create user form. The vulnerability stems from improper input validation enabling malicious SQL statements to be passed to the database.
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= 24.04.2CVSS 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
- Low
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:L
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 installed Centreon versionAccess the Centreon administration interface and navigate to Administration > Parameters > About, or run 'rpm -q centreon' / 'dpkg -l centreon' from the command line to retrieve the exact version numberAffected if The installed version is exactly 24.04.2
-
Verify high-privilege user access existsLog into Centreon with an administrator-level account and confirm access to the Administration > Users > Add user functionality (or equivalent user creation menu)Affected if High-privilege administrative accounts with user creation permissions exist in the system
-
Inspect database user permissionsConnect to the Centreon database using the application database credentials and query for user privileges: SHOW GRANTS FOR 'centreon'@'localhost'; or inspect the contact table structure for unsanitized fieldsAffected if The database user has elevated permissions allowing arbitrary SQL execution, or the user creation form fields accept raw SQL syntax without sanitization
-
Review application logs for SQL injection indicatorsExamine Centreon logs in /var/log/centreon/ or the database audit logs for anomalous SQL patterns in user creation requests, looking for SQL keywords (UNION, SELECT, INSERT) in input fieldsAffected if Log entries show SQL syntax or unexpected queries originating from user creation form submissions
A user is affected if they are running Centreon version 24.04.2 AND have high-privilege administrative accounts that can access the create user form, as this is the specific attack vector for the SQL injection.
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.
From vendor dataApply Centreon security patches for version 24.04.2. As interim measures, implement strict input validation on all user creation form fields and ensure database accounts used by the application follow least-privilege principles.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-39843 — 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-2024-39843 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