{"answers":{"affected":"2 open source packages ship an affected version, including org.jruby:jruby-core. It affects 1 product.","exploited":"There is no known exploitation of CVE-2010-1330 in the wild and no public exploit code.","fix":"Upgrade org.jruby:jruby-core to 1.4.1 or later.","what":"CVE-2010-1330 is a medium-severity cross-site scripting vulnerability in n/a, published on 23 Nov 2012. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2010-1330 and fix it if it is affected.\n\nWhat it is: CVE-2010-1330 is a medium-severity cross-site scripting vulnerability in n/a, published on 23 Nov 2012. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2010-1330 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.jruby:jruby-core (Maven): affected all versions; fixed in 1.4.1\n- org.jruby:jruby-core (Maven): affected all versions; fixed in 1.4.1\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2010-1330/ (Markdown: https://insights.sbomify.com/CVE-2010-1330/index.md)","id":"CVE-2010-1330","markdown":"https://insights.sbomify.com/CVE-2010-1330/index.md","name":"CVE-2010-1330","record":{"aliases":["DEBIAN-CVE-2010-1330","GHSA-wmq2-jc9m-xp4m"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"JRuby runtime","requires_auth":"none","summary":"Remote attackers can execute cross-site scripting attacks in JRuby applications by exploiting a UTF-8 handling flaw in the regex engine when Unicode mode is enabled.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"jruby","vendor":"jruby"}],"cvss":{"score":4.3,"severity":"medium","source":"nvd","vector":"AV:N/AC:M/Au:N/C:N/I:P/A:N","version":"2.0"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"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.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Cross-site Scripting in in JRuby","id":"CVE-2010-1330","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"xss","year":"2010"},"n_packages":2,"n_references":7,"next":{"headline":"SQL injection in n/a","id":"CVE-2010-1331"},"packages":[{"ecosystem":"Maven","fixed":["1.4.1"],"introduced":["0"],"last_affected":[],"package":"org.jruby:jruby-core","purl":null,"source":"GHSA-wmq2-jc9m-xp4m"},{"ecosystem":"Maven","fixed":["1.4.1"],"introduced":["0"],"last_affected":[],"package":"org.jruby:jruby-core","purl":"pkg:maven/org.jruby/jruby-core","source":"GHSA-wmq2-jc9m-xp4m"}],"prev":{"headline":"Security feature bypass in n/a","id":"CVE-2010-1329"},"products":["n/a"],"published":"2012-11-23","related":[{"cvss_score":5.7,"headline":"JRuby-OpenSSL has hostname verification disabled by default","id":"CVE-2025-46551","kev_date_added":null,"published":"2025-05-07"},{"cvss_score":5,"headline":"JRuby denial of service via Hash Collision","id":"CVE-2012-5370","kev_date_added":null,"published":"2012-11-28"},{"cvss_score":5,"headline":"Denial of service in n/a","id":"CVE-2011-4838","kev_date_added":null,"published":"2011-12-30"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-07","vendors":["n/a"]},"summary":"Remote attackers can execute cross-site scripting attacks in JRuby applications by exploiting a UTF-8 handling flaw in the regex engine when Unicode mode is enabled.","url":"https://insights.sbomify.com/CVE-2010-1330/"}