CVE-2010-1330
Summary
| CVE | CVE-2010-1330 |
|---|---|
| State | PUBLISHED |
| Assigner | mitre |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2012-11-23 19:55:01 UTC |
| Updated | 2026-04-29 01:13:23 UTC |
| Description | The regular expression engine in JRuby before 1.4.1, when $KCODE is set to 'u', does not properly handle characters immediately after a UTF-8 character, which allows remote attackers to conduct cross-site scripting (XSS) attacks via a crafted string. |
Risk And Classification
CVSS v2.0 Breakdown
Access Vector
NetworkAccess Complexity
MediumAuthentication
NoneConfidentiality
NoneIntegrity
PartialAvailability
NoneAV:N/AC:M/Au:N/C:N/I:P/A:N
NVD Known Affected Configurations (CPE 2.3)
| Type | Vendor | Product | Version | Update | Edition | Language |
|---|---|---|---|---|---|---|
| Application | Jruby | Jruby | 0.9.0 | All | All | All |
| Application | Jruby | Jruby | 0.9.1 | All | All | All |
| Application | Jruby | Jruby | 0.9.2 | All | All | All |
| Application | Jruby | Jruby | 0.9.8 | All | All | All |
| Application | Jruby | Jruby | 0.9.9 | All | All | All |
| Application | Jruby | Jruby | 1.0.0 | All | All | All |
| Application | Jruby | Jruby | 1.0.0 | rc1 | All | All |
| Application | Jruby | Jruby | 1.0.0 | rc2 | All | All |
| Application | Jruby | Jruby | 1.0.0 | rc3 | All | All |
| Application | Jruby | Jruby | 1.0.1 | All | All | All |
| Application | Jruby | Jruby | 1.0.2 | All | All | All |
| Application | Jruby | Jruby | 1.0.3 | All | All | All |
| Application | Jruby | Jruby | 1.1 | All | All | All |
| Application | Jruby | Jruby | 1.1 | beta1 | All | All |
| Application | Jruby | Jruby | 1.1 | rc1 | All | All |
| Application | Jruby | Jruby | 1.1 | rc2 | All | All |
| Application | Jruby | Jruby | 1.1 | rc3 | All | All |
| Application | Jruby | Jruby | 1.1.1 | All | All | All |
| Application | Jruby | Jruby | 1.1.2 | All | All | All |
| Application | Jruby | Jruby | 1.1.3 | All | All | All |
| Application | Jruby | Jruby | 1.1.4 | All | All | All |
| Application | Jruby | Jruby | 1.1.5 | All | All | All |
| Application | Jruby | Jruby | 1.1.6 | All | All | All |
| Application | Jruby | Jruby | 1.1.6 | rc1 | All | All |
| Application | Jruby | Jruby | 1.2.0 | All | All | All |
| Application | Jruby | Jruby | 1.2.0 | rc1 | All | All |
| Application | Jruby | Jruby | 1.2.0 | rc2 | All | All |
| Application | Jruby | Jruby | 1.3.0 | All | All | All |
| Application | Jruby | Jruby | 1.3.0 | rc1 | All | All |
| Application | Jruby | Jruby | 1.3.0 | rc2 | All | All |
| Application | Jruby | Jruby | 1.3.1 | All | All | All |
| Application | Jruby | Jruby | 1.4.0 | rc1 | All | All |
| Application | Jruby | Jruby | 1.4.0 | rc2 | All | All |
| Application | Jruby | Jruby | 1.4.0 | rc3 | All | All |
| Application | Jruby | Jruby | All | All | All | All |
Vendor Declared Affected Products
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| IBM X-Force Exchange | af854a3a-2127-422b-91ae-364da2661108 | exchange.xforce.ibmcloud.com | |
| 317435 – (CVE-2010-1330) <dev-java/jruby-1.4.1 (<dev-java/jcodings-1.0.3) XSS vulnerability (CVE-2010-1330) | af854a3a-2127-422b-91ae-364da2661108 | bugs.gentoo.org | |
| Red Hat Customer Portal | af854a3a-2127-422b-91ae-364da2661108 | rhn.redhat.com | |
| 750306 – (CVE-2010-1330) CVE-2010-1330 jruby: XSS in the regular expression engine when processing invalid UTF-8 byte sequences | af854a3a-2127-422b-91ae-364da2661108 | bugzilla.redhat.com | |
| www.osvdb.org/77297 | af854a3a-2127-422b-91ae-364da2661108 | www.osvdb.org | |
| Security Advisory SA46891 - Red Hat update for JBoss Enterprise SOA Platform - Secunia | af854a3a-2127-422b-91ae-364da2661108 | secunia.com | Vendor Advisory |
| JRuby 1.4.1 Released - Fixes XSS Vulnerability in JRuby 1.4.0 - Recommended Upgrade — JRuby.org | af854a3a-2127-422b-91ae-364da2661108 | www.jruby.org | Exploit, Patch, Vendor Advisory |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.