CVE-2019-16405 is a high-severity (CVSS 7.2) remote code execution vulnerability in centreon/centreon. 5 public exploit references exist, so weaponization risk is real. O3 Security confirms whether CVE-2019-16405 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Improper Input Validation in Centreon Web
Real-World Exposure
centreon/centreon🐘centreon/centreonReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
Centreon Web 19.04.4 allows Remote Code Execution by an administrator who can modify Macro Expression location settings.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | centreon/centreon | all versions | 18.10.8 |
| 🐘Packagist | centreon/centreon | ≥ 19.0.0&&< 19.04.5 | 19.04.5 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Centreon 19.04 - Authenticated Remote Code Execution (Metasploit)
by TheCyberGeek · Jan 20, 2020
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for centreon/centreon. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update centreon/centreon to 18.10.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-16405 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2019-16405 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2019-16405. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2019-16405 in your dependencies?
O3 detects CVE-2019-16405 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.