# CVE-2019-17104: Centreon Does Not Set HTTPOnly Flag

> Attackers can steal session cookies due to missing HTTPOnly flag, potentially leading to account takeover.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Oct 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-j224-7qr4-8646

## What is CVE-2019-17104?

CVE-2019-17104 is a high-severity vulnerability in n/a, published on 8 Oct 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In 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.

Weakness: CWE-565 (Reliance on Cookies without Validation and Integrity Checking)

## Which versions are affected by CVE-2019-17104?

2 open source packages ship an affected version, including centreon/centreon. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `centreon/centreon` | Packagist | All versions to 19.04.3 | None |
| `centreon/centreon` | Packagist | All versions to 19.04.3 | None |

Products: Centreon Centreon Vm.

## How do I fix CVE-2019-17104?

No fix has been published for CVE-2019-17104 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-17104 being exploited?

There is no known exploitation of CVE-2019-17104 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2018-21025](https://insights.sbomify.com/CVE-2018-21025/): Centreon Privilege Escalation (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-17104 and fix it if it is affected.

What it is: CVE-2019-17104 is a high-severity vulnerability in n/a, published on 8 Oct 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-17104 in the wild and no public exploit code.

Affected packages and fixed versions:
- centreon/centreon (Packagist): affected all versions up to 19.04.3; no fix listed
- centreon/centreon (Packagist): affected all versions up to 19.04.3; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-17104/ (Markdown: https://insights.sbomify.com/CVE-2019-17104/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-17104
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-17104
- OSV: https://osv.dev/vulnerability/CVE-2019-17104

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-17104/
Summaries are generated and may contain mistakes; the official description above is the record.