dbcve.org
CocoonApplication · Apache

CVE-2022-45135

CRITICAL · 9.8 CVSS v3.1 Published 2023-11-30
Fix available
A fix is available. Upgrade to 2.3.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Apache Cocoon.This issue affects Apache Cocoon: from 2.2.0 before 2.3.0. Users are recommended to upgrade to version 2.3.0, which fixes the issue.

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 · moderate confidence

SQL injection vulnerability in Apache Cocoon web application framework affecting versions 2.2.0 through 2.3.0. The vulnerability allows attackers to inject malicious SQL commands through unsanitized input in database queries.

MitigationUpgrade Apache Cocoon to version 2.3.0 or later which contains the fix for the SQL injection vulnerability.

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
CocoonApplication
Affected:>= 2.2.0, < 2.3.0

CVSS 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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Apache Cocoon version
    Locate the cocoon-core JAR file in the application's WEB-INF/lib directory. Inspect the MANIFEST.MF file inside the JAR to find the Implementation-Version attribute. Alternatively, check the pom.xml or ivy.xml dependency file if source code or build configuration is available.
    Affected if The version is 2.2.0 or higher but lower than 2.3.0 (e.g., 2.2.0, 2.2.1, 2.2.2, etc.)
  2. Confirm database connectivity is in use
    Search for database-related configuration files such as cocoon.xconf, applicationContext.xml, or Spring bean configuration files that define dataSource or SQL connector beans. Also check web.xml for database-related servlet initialization parameters.
    Affected if The application is configured to connect to a database using Cocoon's SQL transformer, SQL executor, or connection pooling mechanisms.
  3. Identify SQL query execution points
    Review the application's XML pipeline configurations (typically in sitemap.xmap files) for use of the SQL transformer (<map:transformer name="sql" .../>) or SQL action components. Also search source code for dynamic SQL query construction using parameters that may not be properly parameterized.
    Affected if SQL queries are executed through Cocoon's SQL components and user-supplied input is passed to these queries without sanitization.
  4. Inspect input handling in database operations
    Examine the code paths that feed user request parameters (from query strings, form inputs, or HTTP headers) into SQL statements. Look for patterns where request.getParameter() or similar methods directly concatenate into SQL without using prepared statements or binding variables.
    Affected if User-controllable input flows directly into SQL query strings without proper escaping or parameterized queries.

You are affected if Apache Cocoon version 2.2.0 through 2.3.0 is installed AND the application uses database connectivity features where unsanitized user input can be injected into SQL queries.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2.3.0 or later
Fixed in 2.3.0
Interim mitigation

Upgrade Apache Cocoon to version 2.3.0 or later which contains the fix for the SQL injection vulnerability.

Recommended fix High confidence

2.3.0

  1. Obtain Apache Cocoon version 2.3.0 from the official Apache distribution repository
  2. Back up all existing configuration files, custom pipelines, and any local modifications to your current Cocoon installation
  3. Replace the existing Cocoon installation with version 2.3.0 files
  4. Restore your backed-up configuration files to the new installation
  5. Verify that all custom pipelines and applications function correctly with the new version
  6. Test that the SQL injection vulnerability is no longer present in affected endpoints

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Cocoon Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-45135 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-45135 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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