\n/queues/>\n```\n\n### Patches\n\nv2.2.1\n\n### Workarounds\n\nNo known workarounds at this time. It is recommended to not click on 3rd party or untrusted links to the resque-web interface until you have patched your application.\n\n### References\n\nhttps://github.com/resque/resque/pull/1790\n","datePublished":"2023-12-18T19:34:06Z","dateModified":"2024-02-16T08:16:11.344395Z","url":"https://o3.security/vulnerability/GHSA-gc3j-vvwf-4rp8","inLanguage":"en","author":{"@id":"https://o3.security/#organization"},"publisher":{"@id":"https://o3.security/#organization"},"mainEntityOfPage":{"@type":"WebPage","@id":"https://o3.security/vulnerability/GHSA-gc3j-vvwf-4rp8"},"speakable":{"@type":"SpeakableSpecification","cssSelector":["h1",".vuln-summary",".vuln-severity",".vuln-mitigation"]},"about":[{"@type":"SoftwareApplication","name":"resque","applicationCategory":"RubyGems","softwareVersion":"2.2.1"}],"citation":[{"@type":"WebPage","url":"https://github.com/resque/resque/security/advisories/GHSA-gc3j-vvwf-4rp8"},{"@type":"WebPage","url":"https://nvd.nist.gov/vuln/detail/CVE-2023-50725"},{"@type":"WebPage","url":"https://github.com/resque/resque/pull/1790"},{"@type":"WebPage","url":"https://github.com/resque/resque/commit/ee99d2ed6cc75d9d384483b70c2d96d312115f07"},{"@type":"WebPage","url":"https://github.com/rubysec/ruby-advisory-db/blob/master/gems/resque/CVE-2023-50725.yml"}]}\n/queues/>\n```\n\n### Patches\n\nv2.2.1\n\n### Workarounds\n\nNo known workarounds at this time. It is recommended to not click on 3rd party or untrusted links to the resque-web interface until you have patched your application.\n\n### References\n\nhttps://github.com/resque/resque/pull/1790\n","url":"https://o3.security/vulnerability/GHSA-gc3j-vvwf-4rp8","identifier":"GHSA-gc3j-vvwf-4rp8","datePublished":"2023-12-18T19:34:06Z","dateModified":"2024-02-16T08:16:11.344395Z","inLanguage":"en","keywords":["GHSA-gc3j-vvwf-4rp8","MEDIUM severity","CWE-79","CVE","vulnerability","security advisory"],"creator":{"@id":"https://o3.security/#organization"},"isAccessibleForFree":true,"variableMeasured":[{"@type":"PropertyValue","name":"CVSS Base Score","value":6.3,"description":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:H/A:N"},{"@type":"PropertyValue","name":"Severity","value":"MEDIUM"},{"@type":"PropertyValue","name":"EPSS Percentile","value":40}]}\n/queues/>\n```\n\n### Patches\n\nv2.2.1\n\n### Workarounds\n\nNo known workarounds at this time. It is recommended to not click on 3rd party or untrusted links to the resque-web interface until you have patched your application.\n\n### References\n\nhttps://github.com/resque/resque/pull/1790\n"}},{"@type":"Question","name":"How severe is GHSA-gc3j-vvwf-4rp8?","acceptedAnswer":{"@type":"Answer","text":"GHSA-gc3j-vvwf-4rp8 has a CVSS score of 6.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance."}},{"@type":"Question","name":"Which packages are affected by GHSA-gc3j-vvwf-4rp8?","acceptedAnswer":{"@type":"Answer","text":"GHSA-gc3j-vvwf-4rp8 affects the following packages: resque (RubyGems). Ecosystems affected: RubyGems."}},{"@type":"Question","name":"How do I fix GHSA-gc3j-vvwf-4rp8?","acceptedAnswer":{"@type":"Answer","text":"Update resque to 2.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-gc3j-vvwf-4rp8 is resolved across your whole dependency graph."}},{"@type":"Question","name":"How do I detect GHSA-gc3j-vvwf-4rp8 in my RubyGems dependencies?","acceptedAnswer":{"@type":"Answer","text":"Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for resque. 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."}},{"@type":"Question","name":"How do I mitigate GHSA-gc3j-vvwf-4rp8 if there is no patch (or I can't update yet)?","acceptedAnswer":{"@type":"Answer","text":"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."}},{"@type":"Question","name":"How does O3 Security protect against GHSA-gc3j-vvwf-4rp8?","acceptedAnswer":{"@type":"Answer","text":"O3 pinpoints whether GHSA-gc3j-vvwf-4rp8 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed."}},{"@type":"Question","name":"Is GHSA-gc3j-vvwf-4rp8 actively exploited in the wild?","acceptedAnswer":{"@type":"Answer","text":"No public exploit code has been indexed for GHSA-gc3j-vvwf-4rp8 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."}},{"@type":"Question","name":"What is the EPSS score for GHSA-gc3j-vvwf-4rp8?","acceptedAnswer":{"@type":"Answer","text":"GHSA-gc3j-vvwf-4rp8 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 40th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority."}},{"@type":"Question","name":"What type of vulnerability is GHSA-gc3j-vvwf-4rp8?","acceptedAnswer":{"@type":"Answer","text":"GHSA-gc3j-vvwf-4rp8 is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure."}},{"@type":"Question","name":"When was GHSA-gc3j-vvwf-4rp8 published, and has it been updated?","acceptedAnswer":{"@type":"Answer","text":"GHSA-gc3j-vvwf-4rp8 was published on December 18, 2023 and was last updated on February 16, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting."}}]}
Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
💎 RubyGems

GHSA-gc3j-vvwf-4rp8

MEDIUM

Resque vulnerable to reflected XSS in resque-web failed and queues lists

Also known asCVE-2023-50725
Published
Dec 18, 2023
Updated
Feb 16, 2024
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed

EPSS Exploitation Probability

via FIRST.org ↗
0.5%probability of exploitation in next 30 days
Lower Risk40th percentile-0.13%
0.03%0.40%0.78%1.16%0.7%0.5%Dec 25Apr 26Jun 26

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected
💎resque

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

Description

Impact

The following paths in resque-web have been found to be vulnerable to reflected XSS:

/failed/?class=<script>alert(document.cookie)</script>
/queues/><img src=a onerror=alert(document.cookie)>

Patches

v2.2.1

Workarounds

No known workarounds at this time. It is recommended to not click on 3rd party or untrusted links to the resque-web interface until you have patched your application.

References

https://github.com/resque/resque/pull/1790

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
💎RubyGemsresqueall versions2.2.1

Detection & mitigation playbook

Open-source dependency
  1. Detect

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

  2. Fix

    Update resque to 2.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-gc3j-vvwf-4rp8 is resolved across your whole dependency graph.

  3. 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.

  4. How O3 protects you

    O3 pinpoints whether GHSA-gc3j-vvwf-4rp8 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-gc3j-vvwf-4rp8. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact The following paths in resque-web have been found to be vulnerable to reflected XSS: ``` /failed/?class=<script>alert(document.cookie)</script> /queues/><img src=a onerror=alert(document.cookie)> ``` ### Patches v2.2.1 ### Workarounds No known workarounds at this time. It is recommended to not click on 3rd party or untrusted links to the resque-web interface until you have patched your application. ### References https://github.com/resque/resque/pull/1790
O3 Security · Impact-Aware SCA

Is GHSA-gc3j-vvwf-4rp8 in your dependencies?

O3 detects GHSA-gc3j-vvwf-4rp8 across RubyGems dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

GHSA-gc3j-vvwf-4rp8: resque Cross-Site Scripting (Medium 6.3) | O3 Security