JenaApplication · Apache
CVE-2023-22665
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThere is insufficient checking of user queries in Apache Jena versions 4.7.0 and earlier, when invoking custom scripts. It allows a remote user to execute arbitrary javascript via a SPARQL query.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceApache Jena versions 4.7.0 and earlier lack sufficient input validation on SPARQL queries when custom scripts are invoked, allowing remote attackers to inject and execute arbitrary JavaScript code through specially crafted SPARQL queries.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
JenaApplication
>= 3.7.0, <= 4.8.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Apache Jena installation and versionCheck your project's dependency management file (Maven pom.xml, Gradle build.gradle, or similar) for the Apache Jena dependency, or list the Jena JAR files present in your classpath/lib directory. Run: grep -r 'jena' pom.xml or ls *.jar in lib folders to locate jena-core or jena-fuseki packages.Affected if The detected version is 3.7.0, 4.0.0, 4.1.0, 4.2.0, 4.3.0, 4.4.0, 4.5.0, 4.6.0, 4.7.0, or 4.8.0 (any version from 3.7.0 through 4.8.0 inclusive)
-
Determine if custom script execution is configuredSearch your application configuration files and codebase for script execution enabling parameters. Look for settings related to Java scripting engines, custom SPARQL function registration, or script-based extensions. Check for: ScriptEngineManager usage, javax.script references, or custom function definitions in configuration.Affected if Custom script execution or custom SPARQL functions are enabled in your Jena configuration or application code
You are affected if you have Apache Jena version 3.7.0 through 4.8.0 AND have custom script execution or custom SPARQL functions enabled in your environment.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade Apache Jena to version 4.8.0 or later, which contains proper input validation for user queries in custom script execution contexts.
Apache Jena 4.9.0 or later
- 1. Identify all Apache Jena deployments in your environment that use versions 3.7.0 through 4.8.0
- 2. Review any custom scripts or extensions that process SPARQL queries, as these are the attack vector
- 3. Plan upgrade to Apache Jena version 4.9.0 or later (the first version after 4.8.0)
- 4. Test the upgrade in a non-production environment first
- 5. Deploy the upgraded version to production
- 6. Verify that custom script execution still functions correctly after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Jena
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-22665 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-22665 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data