dbcve.org
JetspeedApplication · Apache

CVE-2022-32533

CRITICAL · 9.8 CVSS v3.1 Published 2022-07-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
Apache Jetspeed-2 does not sufficiently filter untrusted user input by default leading to a number of issues including XSS, CSRF, XXE, and SSRF. Setting the configuration option "xss.filter.post = true" may mitigate these issues. NOTE: Apache Jetspeed is a dormant project of Apache Portals and no updates will be provided for this 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 · high confidence

Apache Jetspeed-2 portal framework fails to properly filter untrusted user input by default, resulting in multiple critical vulnerabilities including Cross-Site Scripting (XSS), Cross-Site Request Forgery (CSRF), XML External Entity (XXE), and Server-Side Request Forgery (SSRF).

MitigationEnable the 'xss.filter.post = true' configuration option as a partial mitigation; however, this is a dormant project with no official patches expected.

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
JetspeedApplication
Affected:>= 2.2.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. Confirm Apache Jetspeed installation
    Locate the Jetspeed web application directory or WAR file. Check for jetspeed*.war or a deployed jetspeed directory in your application server (e.g., Tomcat webapps/). Also look for jetspeed.properties or jetspeed-config.xml configuration files.
    Affected if Apache Jetspeed is not present in the environment
  2. Identify installed Jetspeed version
    Check the version by examining the WAR file name, the jetspeed.jar MANIFEST.MF file, or any version information in the WEB-INF/lib directory. Alternatively, check the pom.xml if source code is available.
    Affected if The installed version is 2.2.0 or higher
  3. Locate the XSS filter configuration
    Find the main Jetspeed configuration file (typically jetspeed.properties or jetspeed-portlet.xml in the WEB-INF/classes or WEB-INF directory). Search for the 'xss.filter.post' property.
    Affected if The configuration file exists and contains the xss.filter.post setting
  4. Check XSS filter status
    Examine the xss.filter.post value in the configuration file. If the property is absent, missing, or set to false, the filter is not enabled.
    Affected if xss.filter.post is not set to 'true' (either missing, absent, or explicitly set to false)
  5. Verify default filter behavior
    Confirm that by default, without explicit configuration, Jetspeed does not filter XSS, CSRF, XXE, or SSRF inputs. This is the vulnerable state - the absence of filtering protection.
    Affected if No explicit filtering configuration is in place and the application processes untrusted input without sanitization

You are affected if Apache Jetspeed version 2.2.0 or higher is installed and the xss.filter.post configuration is not explicitly set to true (meaning the default vulnerable state with no input filtering is active).

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Enable the 'xss.filter.post = true' configuration option as a partial mitigation; however, this is a dormant project with no official patches expected.

Recommended fix High confidence
  1. Locate the Jetspeed configuration file (typically jetspeed.properties or WEB-INF/conf/jetspeed.properties in the deployed webapp)
  2. Add or modify the setting: xss.filter.post=true
  3. Save the configuration file
  4. Restart the Jetspeed service or redeploy the web application
Caveat The Apache Jetspeed project is dormant with no updates planned; no fixed release exists

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

Fix this in Jetspeed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-32533 — 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-32533 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