dbcve.org
TomcatWeb server / proxy · Apache

CVE-2022-45143

HIGH · 7.5 CVSS v3.1 Published 2023-01-03
Fix available
A fix is available. Upgrade to 9.0.69 or later.
See remediation →
84/100
Remediation priority · High
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
The JsonErrorReportValve in Apache Tomcat 8.5.83, 9.0.40 to 9.0.68 and 10.1.0-M1 to 10.1.1 did not escape the type, message or description values. In some circumstances these are constructed from user provided data and it was therefore possible for users to supply values that invalidated or manipulated the JSON output.

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

The JsonErrorReportValve in affected Apache Tomcat versions does not escape user-supplied type, message, or description values when generating JSON error responses. This allows attackers to inject or manipulate JSON output by supplying crafted input values, potentially breaking JSON parsing or injecting malicious content.

MitigationUpgrade Apache Tomcat to version 8.5.84, 9.0.69, or 10.1.2 or later. If immediate upgrading is not feasible, implement input validation and sanitization on all user-supplied data that flows to the JsonErrorReportValve.

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
TomcatWeb server / proxy
Affected:>= 9.0.40, < 9.0.69= 8.5.83= 10.1.0= 10.1.1

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
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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 checks

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

  1. Identify Apache Tomcat installation directory
    Locate the Tomcat root directory, commonly at /opt/tomcat, /usr/share/tomcat, or C:\Program Files\Apache Software Foundation\Tomcat on Windows. Check for the presence of lib, conf, and logs subdirectories.
    Affected if Tomcat installation cannot be located or is not a standard Apache Tomcat directory structure.
  2. Determine installed Tomcat version
    Check for a VERSION file in the Tomcat home directory, or examine the startup logs in the logs folder for a line containing 'Server version name' or 'Server version number'. Alternatively, run: catalina.sh version (Unix) or catalina.bat version (Windows) from the bin directory.
    Affected if Unable to determine the version number from VERSION file, logs, or version command output.
  3. Compare version against affected ranges
    Verify if the installed version matches any of these patterns: 9.0.40 through 9.0.68 inclusive, exactly 8.5.83, exactly 10.1.0, or exactly 10.1.1. Version 9.0.69 and above, 8.5.84 and above, or 10.1.2 and above are NOT affected.
    Affected if The installed version is 9.0.40 through 9.0.68 inclusive, OR exactly 8.5.83, OR exactly 10.1.0, OR exactly 10.1.1.
  4. Locate JsonErrorReportValve configuration
    Search for 'JsonErrorReportValve' in the conf/server.xml file and any conf/context.xml files. Look for a Valve element with className containing 'JsonErrorReportValve', typically nested within a Host element.
    Affected if The JsonErrorReportValve is explicitly configured in server.xml or context.xml, making it actively used for error responses.
  5. Verify default error valve configuration
    Examine conf/server.xml for any ErrorReportValve configuration. If no specific ErrorReportValve is defined, Tomcat may use the default JsonErrorReportValve in affected versions. Check for comments or default Valve settings.
    Affected if No custom ErrorReportValve is configured and Tomcat is using its default error handling mechanism in an affected version.

A user is affected if they are running Apache Tomcat version 9.0.40 through 9.0.68, 8.5.83, 10.1.0, or 10.1.1 AND the JsonErrorReportValve is active (either explicitly configured or as the default), and untrusted user input can reach error response generation.

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 9.0.69 or later
Fixed in 9.0.69
Interim mitigation

Upgrade Apache Tomcat to version 8.5.84, 9.0.69, or 10.1.2 or later. If immediate upgrading is not feasible, implement input validation and sanitization on all user-supplied data that flows to the JsonErrorReportValve.

Recommended fix High confidence

Tomcat 8.5.84+, 9.0.69+, or 10.1.2+ depending on your branch

  1. 1. Identify the currently installed Apache Tomcat version by checking the $CATALINA_HOME/README RELEASE-NOTES file or running 'version.sh' (or 'version.bat' on Windows)
  2. 2. Download the appropriate fixed Tomcat version from the official Apache Tomcat downloads page (https://tomcat.apache.org/)
  3. 3. For Tomcat 8.5.x: upgrade to version 8.5.84 or later
  4. 4. For Tomcat 9.0.x: upgrade to version 9.0.69 or later
  5. 5. For Tomcat 10.1.x: upgrade to version 10.1.2 or later
  6. 6. Stop the running Tomcat instance
  7. 7. Back up the existing Tomcat installation including configuration files and web applications
  8. 8. Install the new Tomcat version to the same location or a new location
Caveat Minor: Standard Tomcat upgrade; review release notes for any deprecation notices in your version path

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

Fix this in Tomcat Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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