CVE-2019-19484
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 · uneditedOpen redirect via parameter ‘p’ in login.php in Centreon (19.04.4 and below) allows an attacker to craft a payload and execute unintended behavior.
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 · moderate confidenceOpen redirect vulnerability in Centreon login.php where the 'p' parameter is not properly validated, allowing attackers to craft malicious URLs that redirect users to arbitrary external sites. This can be leveraged in phishing attacks to trick users into believing they are visiting legitimate Centreon pages.
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.4CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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.
-
Verify Centreon installation existsCheck for Centreon web application files in the web server document root (commonly /usr/share/centreon or /var/www/html/centreon). Look for the presence of login.php file in theCentreon web interface directory.Affected if Centreon web application is present on the server
-
Determine installed Centreon versionCheck the Centreon version by examining the version file or the Centreon web interface footer. Common locations include version.php file in theCentreon root directory or the 'About' page in the administration section.Affected if Installed version is 19.04.4 or any earlier version (19.04.x versions <= 19.04.4)
-
Confirm login.php is accessibleVerify that the login.php file is accessible via the web server by accessing the Centreon login page URL (typically /centreon/login.php or /login.php).Affected if The Centreon login page is accessible over the network
-
Inspect 'p' parameter handling in login.phpExamine the login.php source code for the 'p' parameter usage. Look for any redirect or header manipulation logic that uses the 'p' parameter without proper validation against external URLs.Affected if The login.php code contains logic that uses the 'p' parameter for redirection without validating it is a relative/internal path only
A system is affected if it is running Centreon version 19.04.4 or earlier with the login.php file accessible and the 'p' parameter being used for redirection without validation against external domains.
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 dataImplement strict input validation on the 'p' parameter, restricting it to an allowlist of internal paths or relative URLs only; reject any attempts to specify external domains or absolute URLs.
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-19484 — 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-19484 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