GHSA-w5rq-g9r6-vrcg
HIGHGHSA-w5rq-g9r6-vrcg is a high-severity (CVSS 8.1) Cross-site Scripting (XSS) vulnerability in @dapperduckling/keycloak-connector-server. O3 Security confirms whether GHSA-w5rq-g9r6-vrcg is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
@dapperduckling/keycloak-connector-server has Reflected XSS Vulnerability in Authentication Flow URL Handling
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.
@dapperduckling/keycloak-connector-servernpmDescription
Impact A Reflected Cross-Site Scripting (XSS) vulnerability was discovered in the authentication flow of the application. This issue arises due to improper sanitization of the URL parameters, allowing the URL bar's contents to be injected and reflected into the HTML page. An attacker could craft a malicious URL to execute arbitrary JavaScript in the browser of a victim who visits the link.
Who is impacted? Any application utilizing this authentication library is vulnerable. Users of the application are at risk if they can be lured into clicking on a crafted malicious link.
Patches The vulnerability has been patched in 2.5.5 by ensuring proper sanitization and escaping of user input in the affected URL parameters.
Users are strongly encouraged to upgrade to the following versions:
Workarounds If upgrading is not immediately possible, users can implement the following workarounds:
- Employ a Web Application Firewall (WAF) to block malicious requests containing suspicious URL parameters.
- Apply input validation and escaping directly within the application’s middleware or reverse proxy layer, specifically targeting the affected parameters.
References
- OWASP Cross-Site Scripting (XSS) Cheat Sheet: https://owasp.org/www-community/attacks/xss/
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @dapperduckling/keycloak-connector-server | all versions | 2.5.5 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @dapperduckling/keycloak-connector-server. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update @dapperduckling/keycloak-connector-server to 2.5.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w5rq-g9r6-vrcg is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-w5rq-g9r6-vrcg is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-w5rq-g9r6-vrcg. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-w5rq-g9r6-vrcg in your dependencies?
O3 detects GHSA-w5rq-g9r6-vrcg across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.