dbcve.org
CentreonApplication · Merethis

CVE-2014-3829

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
displayServiceStatus.php in Centreon 2.5.1 and Centreon Enterprise Server 2.2 (fixed in Centreon web 2.5.3) allows remote attackers to execute arbitrary commands via shell metacharacters in the (1) session_id or (2) template_id parameter, related to the command_line variable.

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

Centreon displayServiceStatus.php fails to sanitize user input in the session_id and template_id parameters before passing to the command_line variable, allowing attackers to inject shell metacharacters and execute arbitrary OS commands. This is a classic command injection vulnerability in a web application that directly invokes system commands with unsanitized user-supplied data.

MitigationUpgrade to Centreon Web 2.5.3 or later. If immediate patching is not possible, implement input validation to reject shell metacharacters and consider web application firewall rules to block malicious parameter patterns.

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
    Locate Centreon web files on the system - typically installed in /usr/share/centreon or /var/www/html/centreon. Look for the main Centreon web application directory.
    Affected if Centreon is not present on the system
  2. Identify Centreon version
    Check the installed Centreon version - look for version.php in the Centreon web directory, or access the Centreon web interface login page which often displays version information.
    Affected if The installed version is 2.5.1 (Merethis Centreon) or 2.2 (Merethis Centreon Enterprise Server)
  3. Locate vulnerable script
    Find the displayServiceStatus.php file within the Centreon web directory structure.
    Affected if The file displayServiceStatus.php exists in the Centreon installation
  4. Verify web interface exposure
    Confirm the Centreon web interface is accessible over HTTP/HTTPS - the vulnerability is exploitable through web requests.
    Affected if The Centreon web interface is externally accessible and the vulnerable script can be reached
  5. Check for command injection entry points
    Examine the displayServiceStatus.php script - specifically look for usage of session_id and template_id parameters being passed to command_line without sanitization.
    Affected if The script uses session_id or template_id parameters in system commands without input validation

A user is affected if Centreon version 2.5.1 or 2.2 is installed, the displayServiceStatus.php file exists, and the web interface is accessible allowing unauthenticated injection through session_id or template_id parameters.

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. If immediate patching is not possible, implement input validation to reject shell metacharacters and consider web application firewall rules to block malicious parameter patterns.

Recommended fix High confidence

Centreon web 2.5.3 or later

  1. 1. Identify the current Centreon installation version by checking the web interface or using 'rpm -qa | grep centreon'
  2. 2. Create a complete backup of the Centreon database and configuration files
  3. 3. Stop the Centreon services (centcore, centstorage, apache) before upgrading
  4. 4. Upgrade Centreon to version 2.5.3 or later by following the official Centreon upgrade documentation for your distribution
  5. 5. Restart the Centreon services after the upgrade completes
  6. 6. Verify the new version is installed: 'rpm -qa | grep centreon'
  7. 7. Verify the vulnerability is patched by checking that the displayServiceStatus.php file no longer allows shell metacharacters in session_id or template_id parameters
Caveat Review Centreon 2.5.3 release notes for any breaking changes or required migration steps before upgrading

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

Fix this in Centreon Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the patch applied

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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