Skip to content
Fencer Intel
medium 4.3

CVE-2014-2538 json

rack-ssl Cross-site Scripting vulnerability

published 12y ago modified 4mo ago also GHSA-v3rr-cph9-2g2q , EUVD-2017-0309

cvss
4.3
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.2%
EPSS 2.2% chance of exploitation in 30 days, percentile 82%
public exploits
0
none known

Summary

Cross-site scripting (XSS) vulnerability in lib/rack/ssl.rb in the rack-ssl gem before 1.4.0 for Ruby allows remote attackers to inject arbitrary web script or HTML via a URI, which might not be properly handled by third-party adapters such as JRuby-Rack.

Patch / fix

  • rubygems rack-ssl 1.4.0
  • ruby-rack-ssl Debian 14, Debian 13, Debian 12 1.3.2-4

debian advisories DEBIAN-CVE-2014-2538

Is CVE-2014-2538 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2014-2538 updated cvss 4.3

rack-ssl: URL error display XSS

  • Red Hat CloudForms Management Engine 5 ruby193-rubygem-rack-ssl Red Hat OpenShift Enterprise 1 ruby193-rubygem-rack-ssl Red Hat OpenStack Platform 3 ruby193-rubygem-rack-ssl Red Hat OpenStack Platform 4 ruby193-rubygem-rack-ssl Red Hat Software Collections ruby193-rubygem-rack-ssl Red Hat Subscription Asset Manager ruby193-rubygem-rack-ssl
    affected: no fix planned “Will not fix”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

2.19% chance of exploitation in the next 30 days, higher than 82% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:N/I:P/A:N

Affected packages

ecosystem package affected fixed in
rubygems rack-ssl
<1.4.0
1.4.0

Classification

Weakness
  • CWE-79 Improper Neutralization of Input During Web Page Generation

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.