CVE-2017-11289
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 · uneditedAn issue was discovered in Adobe Connect 9.6.2 and earlier versions. A reflected cross-site scripting vulnerability exists that can result in information disclosure.
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 confidenceA reflected cross-site scripting (XSS) vulnerability in Adobe Connect versions 9.6.2 and earlier allows attackers to inject malicious scripts through user-supplied input that gets reflected back without proper sanitization, potentially leading to session hijacking or information disclosure.
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<= 9.6.2CVSS 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.0/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 Adobe Connect versionAccess the Adobe Connect login page, admin dashboard, or help/about section to view the software version. Alternatively, check installation directories or configuration files for version information.Affected if The installed version is 9.6.2 or any version lower (e.g., 9.6.1, 9.5.x, earlier).
-
Identify user input parameters in HTTP requestsUse a browser proxy or manual inspection to capture HTTP requests sent to the Adobe Connect server. Look for parameters in URLs or form submissions that accept user input.Affected if User-supplied parameters exist in requests that get reflected back in the server response without encoding.
-
Test for reflected XSS in user-supplied parametersInject a test payload such as <script>alert(1)</script> into suspected parameters (e.g., query strings, form fields, POST data) and observe whether the payload is returned unmodified in the HTML response.Affected if The injected script payload appears verbatim or with minimal HTML breaking changes in the response, indicating lack of proper output encoding.
-
Verify session cookie attributesInspect the Set-Cookie headers for the Adobe Connect session cookies to confirm if HttpOnly and Secure flags are set.Affected if Session cookies lack HttpOnly or Secure flags, making them more vulnerable to XSS-driven session hijacking.
A user is affected if their Adobe Connect installation is version 9.6.2 or earlier and user-supplied input is reflected in responses without sanitization, allowing script injection.
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 proper input validation and output encoding on all user-supplied parameters, and apply available vendor patches for Adobe Connect.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-11289 — 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-2017-11289 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