How severe is GHSA-8c8c-4vfj-rrpc?

No CVSS score has been assigned to GHSA-8c8c-4vfj-rrpc yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-8c8c-4vfj-rrpc?

GHSA-8c8c-4vfj-rrpc affects the following packages: redis-commander (npm). Ecosystems affected: npm.

How do I fix GHSA-8c8c-4vfj-rrpc?

Update redis-commander to 0.5.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8c8c-4vfj-rrpc is resolved across your whole dependency graph.

How do I detect GHSA-8c8c-4vfj-rrpc in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for redis-commander. 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.

How do I mitigate GHSA-8c8c-4vfj-rrpc if there is no patch (or I can't update yet)?

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 does O3 Security protect against GHSA-8c8c-4vfj-rrpc?

O3 pinpoints whether GHSA-8c8c-4vfj-rrpc is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-8c8c-4vfj-rrpc actively exploited in the wild?

No public exploit code has been indexed for GHSA-8c8c-4vfj-rrpc yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-8c8c-4vfj-rrpc published, and has it been updated?

GHSA-8c8c-4vfj-rrpc was published on September 1, 2020 and was last updated on March 4, 2022. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

GHSA-8c8c-4vfj-rrpc

Fix: joeferner/redis-commander@1a483eb

GHSA-8c8c-4vfj-rrpc is a security vulnerability in redis-commander. O3 Security confirms whether GHSA-8c8c-4vfj-rrpc is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Reflected Cross-Site Scripting in redis-commander

Published

Sep 1, 2020

Updated

Mar 4, 2022

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Mar 4, 2022 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

📦redis-commander

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.

Description

Affected versions of redis-commander contain a cross-site scripting vulnerability in the highlighterId paramter of the clipboard.swf component on hosts serving Redis Commander.

Mitigating factors: Flash must be installed / enabled for this to work. The below proof of concept was verified to work using Firefox 57.0 on Windows 10 by manually installing the Flash NPAPI Windows plugin

Proof of concept

http://instance/jstree/_docs/syntax/clipboard.swf?highlighterId=\%22))}%20catch(e)%20{alert(document.domain);}//

Recommendation

No direct patch for this vulnerability is currently available.

At this time, the best mitigation is to use an alternative, functionally equivalent package, or to use extreme caution when using redis-commander, ensuring that redis-commmander is the only web page you have open, and avoiding clicking on any links.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`redis-commander`	≥ 0.0.0&&< 0.5.0	0.5.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for redis-commander. 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 redis-commander to 0.5.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8c8c-4vfj-rrpc 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-8c8c-4vfj-rrpc 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-8c8c-4vfj-rrpc. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Affected versions of `redis-commander` contain a cross-site scripting vulnerability in the `highlighterId` paramter of the clipboard.swf component on hosts serving Redis Commander. Mitigating factors: Flash must be installed / enabled for this to work. The below proof of concept was verified to work using Firefox 57.0 on Windows 10 by manually installing the [Flash NPAPI Windows plugin](https://get.adobe.com/flashplayer/otherversions/) ## Proof of concept ``` http://instance/jstree/_docs/syntax/clipboard.swf?highlighterId=\%22))}%20catch(e)%20{alert(document.domain);}// ``` ## Recommendat

O3 Security · Impact-Aware SCA

Is GHSA-8c8c-4vfj-rrpc in your dependencies?

O3 detects GHSA-8c8c-4vfj-rrpc across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works