CVE-2019-10227
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 · uneditedopenITCOCKPIT before 3.7.1 has reflected XSS in the 404-not-found component.
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 confidenceThis is a reflected Cross-Site Scripting (XSS) vulnerability in the 404-not-found component of openITCOCKPIT versions prior to 3.7.1. User-supplied input in the 404 error page is not properly sanitized or encoded, allowing attackers to inject malicious JavaScript that executes in the victim's browser when they trigger a 404 error.
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< 3.7.1CVSS 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.
-
Identify installed openITCOCKPIT versionAccess the system administration panel or check the package/version information using the command line interface provided by openITCOCKPIT. Look for a version number displayed in the software or its installation metadata.Affected if The version displayed is any release prior to 3.7.1 (for example, 3.7.0, 3.6.x, or earlier)
-
Confirm 404 error page functionality is activeTrigger a 404 error by navigating to a non-existent page or resource within the openITCOCKPIT web interface, such as accessing a URL with a random path like /it-novum-nonexistent-page-12345.Affected if The application returns a custom 404 error page rather than a generic server error, indicating the vulnerable 404 component is enabled
-
Test for reflected input in 404 responseSubmit a request to a non-existent page with a specific test string in the URL (for example, /nonexistent?test=<script>alert(1)</script>) and examine whether the 404 page displays this string unescaped or without encoding.Affected if The test string appears in the response body exactly as submitted, without HTML encoding of special characters like < and >
A system is affected if it runs openITCOCKPIT version lower than 3.7.1 and the 404 error page reflects user-supplied input without proper sanitization or encoding.
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 data3.7.1
Upgrade to openITCOCKPIT version 3.7.1 or later, which contains the patch for this vulnerability. As a temporary workaround, avoid clicking on untrusted links that may trigger the vulnerable 404 component.
- 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-10227 — 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-10227 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