CVE-2019-3686
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 · uneditedopenQA before commit c172e8883d8f32fced5e02f9b6faaacc913df27b was vulnerable to XSS in the distri and version parameter. This was reported through the bug bounty program of Offensive Security
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 confidenceCross-site scripting (XSS) vulnerability in openQA allows injection of malicious JavaScript through the 'distri' and 'version' parameters in the web interface. This occurs when user-supplied input in these parameters is rendered without proper output encoding.
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< 2019-07-22CVSS 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 openQA installation versionLocate the openQA installation and determine its version by checking the package manager, RPM/DEB metadata, or the About page in the web interface if accessible. Compare the installed version date to 2019-07-22.Affected if The installed version date is before 2019-07-22 (any version prior to the fix commit c172e8883d8f32fced5e02f9b6faaacc913df27b).
-
Confirm openQA web interface is enabledVerify that the openQA web interface (usually on port 80/443 or 9526) is accessible and running. Check if the web service process is active.Affected if The web interface is exposed and running, making the XSS payload injectable through HTTP requests.
-
Inspect the 'distri' and 'version' parameter handlingExamine the openQA source code or configuration files to determine whether the 'distri' and 'version' parameters are processed without output encoding. Look for template rendering code that handles these parameters.Affected if The application renders the 'distri' or 'version' parameter values directly in HTML responses without proper sanitization or encoding.
-
Test for XSS vulnerability (optional manual check)If authorized, send a crafted request to the web interface with a test payload in the 'distri' or 'version' parameter (e.g., <script>alert('XSS')</script>) and observe if the payload is executed in the response.Affected if The malicious script payload is reflected back in the HTTP response without being escaped or sanitized, indicating the vulnerability is present.
You are affected if your openQA version predates 2019-07-22 and the web interface is accessible, as the 'distri' and 'version' parameters will reflect unsanitized input.
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 data2019-07-22
Upgrade openQA to a version after commit c172e8883d8f32fced5e02f9b6faaacc913df27b, which implements proper input validation and output encoding for the affected parameters.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-3686 — 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-3686 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