CVE-2019-17104
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 · uneditedIn Centreon VM through 19.04.3, the cookie configuration within the Apache HTTP Server does not protect against theft because the HTTPOnly flag is not set.
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 VM through version 19.04.3 fails to set the HTTPOnly flag on session cookies configured within the Apache HTTP Server. Without this flag, client-side scripts can access cookies via document.cookie, enabling attackers to steal session identifiers through cross-site scripting (XSS) vulnerabilities and potentially hijack user sessions.
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<= 19.04.3CVSS 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 VM versionLocate the Centreon installation and retrieve the version number, typically found in the web interface (About page) or via command line tools such as 'rpm -qa centreon-web' or 'cat /usr/share/centreon/VERSION', depending on the installation method.Affected if The installed version is 19.04.3 or any earlier version within the Centreon VM 19.04 branch.
-
Verify Apache module configurationInspect the Apache HTTP Server configuration files for Centreon (commonly in /etc/httpd/conf.d/ or /etc/apache2/sites-enabled/) and check whether mod_headers is loaded and configured to add the HttpOnly flag to Set-Cookie headers. Look for directives like 'Header edit Set-Cookie' or 'Header set Set-Cookie' that include the HttpOnly attribute.Affected if mod_headers is not loaded, or no Header directive is present that adds the HttpOnly attribute to session cookies.
-
Inspect active session cookiesLog into the Centreon web interface, open a browser's developer tools (F12), navigate to the Application or Storage tab, locate the session cookies (typically named PHPSESSID, cid, or similar), and examine the cookie attributes. Alternatively, use a command-line tool like curl to make a request and inspect the Set-Cookie headers in the response.Affected if Session cookies are present without the HttpOnly attribute in their definition, meaning the cookie value can be accessed via document.cookie in client-side scripts.
A user is affected if their Centreon VM installation is version 19.04.3 or earlier AND the session cookies created by the application do not include the HttpOnly flag, leaving them vulnerable to session theft via XSS attacks.
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 dataConfigure Apache HTTP Server to set the HttpOnly and Secure flags on all session cookies using mod_headers (Header edit Set-Cookie ^(.*)$ $1;HttpOnly;Secure), or modify the application code to set these flags when cookies are created.
- 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-17104 — 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-17104 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