dbcve.org
CentreonApplication · Merethis

CVE-2014-3828

HIGH · 10.0 CVSS v2.0 Published 2014-10-23
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
High EPSS Public exploit Remotely reachable No privileges Zero-click Patch available

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
Multiple SQL injection vulnerabilities in Centreon 2.5.1 and Centreon Enterprise Server 2.2 (fixed in Centreon web 2.5.3) allow remote attackers to execute arbitrary SQL commands via (1) the index_id parameter to views/graphs/common/makeXML_ListMetrics.php, (2) the sid parameter to views/graphs/GetXmlTree.php, (3) the session_id parameter to views/graphs/graphStatus/displayServiceStatus.php, (4) the mnftr_id parameter to configuration/configObject/traps/GetXMLTrapsForVendor.php, or (5) the index parameter to common/javascript/commandGetArgs/cmdGetExample.php in include/.

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

Multiple SQL injection vulnerabilities in Centreon 2.5.1 and Centreon Enterprise Server 2.2 allow remote unauthenticated attackers to execute arbitrary SQL commands via five different parameters across various PHP files including makeXML_ListMetrics.php, GetXmlTree.php, displayServiceStatus.php, GetXMLTrapsForVendor.php, and cmdGetExample.php.

MitigationUpgrade to Centreon web 2.5.3 or later, which contains the fix for these SQL injection vulnerabilities. Alternatively, implement parameterized queries or input validation on the affected parameters as a compensating control.

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:= 2.5.1
Centreon Enterprise ServerApplication
Affected:= 2.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
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

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. Confirm Centreon installation
    Identify whether Centreon (formerly Merethis Centreon) is installed in your environment. Check for Centreon web application directories (commonly /usr/local/centreon, /var/www/html/centreon, or similar paths) or access the web interface on typical ports (80, 443).
    Affected if Centreon web application is present in the environment.
  2. Identify installed Centreon version
    Locate and read the Centreon version information. This is typically found in the web interface under 'About' or 'System Information' pages, or in version/configuration files within the Centreon installation directory.
    Affected if The installed version is Centreon 2.5.1 or Centreon Enterprise Server 2.2.
  3. Locate vulnerable PHP files
    Check for the presence of the affected PHP files in the Centreon web directory: makeXML_ListMetrics.php, GetXmlTree.php, displayServiceStatus.php, GetXMLTrapsForVendor.php, and cmdGetExample.php. These are typically found under the Centreon 'www' or 'include' directory.
    Affected if Any of these PHP files exist in the Centreon installation directory and are web-accessible.
  4. Verify unauthenticated access to vulnerable endpoints
    Attempt to access the vulnerable PHP files directly via HTTP/HTTPS without authentication. The SQL injection vulnerabilities are exploitable by remote unauthenticated attackers via specific parameters in these files.
    Affected if The vulnerable PHP files are accessible without authentication and accept user input via the affected parameters.

You are affected if Centreon 2.5.1 or Centreon Enterprise Server 2.2 is installed and the vulnerable PHP files (makeXML_ListMetrics.php, GetXmlTree.php, displayServiceStatus.php, GetXMLTrapsForVendor.php, cmdGetExample.php) are accessible without authentication.

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
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Upgrade to Centreon web 2.5.3 or later, which contains the fix for these SQL injection vulnerabilities. Alternatively, implement parameterized queries or input validation on the affected parameters as a compensating control.

Recommended fix High confidence

Centreon web 2.5.3 or later

  1. 1. Back up the current Centreon installation and database before starting the upgrade
  2. 2. Download Centreon web 2.5.3 or later from the official Centreon repository (https://download.centreon.com)
  3. 3. Follow the official Centreon upgrade documentation for your specific installation (Centreon 2.5.1 or Centreon Enterprise Server 2.2)
  4. 4. Apply the upgrade following the standard procedure: stop the Centreon services, replace the web files, run the upgrade script, and restart services
  5. 5. Verify the SQL injection vulnerabilities are resolved by checking that the vulnerable parameters (index_id, sid, session_id, mnftr_id, index) are properly sanitized
  6. 6. Test Centreon functionality to ensure all monitoring features work correctly after the upgrade

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 / QA2.0 h
20.0 hours of engineering $3,500
Get the patch applied

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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