CVE-2019-17643
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 · uneditedAn issue was discovered in Centreon before 2.8-30,18.10-8, 19.04-5, and 19.10-2. It provides sensitive information via an unauthenticated direct request for include/monitoring/recurrentDowntime/GetXMLHost4Services.php.
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 confidenceCentreon before versions 2.8-30, 18.10-8, 19.04-5, and 19.10-2 contains an unauthenticated information disclosure vulnerability. The file include/monitoring/recurrentDowntime/GetXMLHost4Services.php can be accessed directly without authentication, allowing remote attackers to obtain sensitive monitoring data.
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< 2.8.30>= 2.8.4, < 18.10.8>= 19.0.0, < 19.04.5>= 19.04.6, < 19.10.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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 Centreon versionCheck the version file or administration interface. Look for a version.php or similar file in the Centreon installation directory, or log into the Centreon web interface and navigate to the About or Administration section.Affected if The installed version is less than 2.8.30, or between 2.8.4 and 18.10.7, or between 19.0.0 and 19.04.4, or between 19.04.6 and 19.10.1.
-
Locate the vulnerable PHP fileSearch for the file GetXMLHost4Services.php in the Centreon web directory, typically under include/monitoring/recurrentDowntime/.Affected if The file exists in the expected location within the Centreon web root.
-
Test unauthenticated access to the endpointUsing a web browser or curl command, attempt to access the URL directly without providing any authentication credentials: http(s)://<centreon-host>/include/monitoring/recurrentDowntime/GetXMLHost4Services.phpAffected if The page loads and returns monitoring data or XML content without requiring login credentials.
-
Check access control configurationReview the web server configuration and Centreon access control settings to verify whether the include/monitoring/recurrentDowntime/ directory is protected by authentication.Affected if No authentication is required to access files in this directory, or the directory is not covered by the existing authentication rules.
A user is affected if their Centreon version falls within the vulnerable ranges AND the GetXMLHost4Services.php file is accessible without authentication.
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 data2.8.3018.10.819.04.5
Update Centreon to version 2.8-30, 18.10-8, 19.04-5, 19.10-2 or later to patch this vulnerability. Alternatively, implement authentication and access controls on the affected PHP endpoint.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-17643 — 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-2019-17643 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