dbcve.org
Websphere Application ServerApplication · Ibm

CVE-2022-34165

MEDIUM · 5.4 CVSS v3.1 Published 2022-09-09
Fix available
A fix is available. Upgrade to 22.0.0.9 or later.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable Zero-click Patch available

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
IBM WebSphere Application Server 7.0, 8.0, 8.5, and 9.0 and IBM WebSphere Application Server Liberty 17.0.0.3 through 22.0.0.9 are vulnerable to HTTP header injection, caused by improper validation. This could allow an attacker to conduct various attacks against the vulnerable system, including cache poisoning and cross-site scripting. IBM X-Force ID: 229429.

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
How this class of weakness works · CWE-74

Untrusted input crosses into a downstream interpreter — SQL, a shell, an HTML page, an LDAP query — without being kept separate from the commands around it, so the attacker's data is read as instructions. This is the parent class behind SQL injection, cross-site scripting, and command injection alike. The durable fix is the same everywhere: keep data and code apart at every boundary, using parameterisation or context-aware encoding rather than building interpreted strings by concatenation.

General guidance for the injection class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

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
Websphere Application ServerApplication
Affected:>= 7.0.0.0, <= 7.0.0.45>= 8.0.0.0, <= 8.0.0.15>= 8.5.0.0, <= 8.5.5.22>= 9.0.0.0, <= 9.0.5.13>= 17.0.0.3, < 22.0.0.9

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

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

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 22.0.0.9 or later
Fixed in 22.0.0.9
Vendor patch www.ibm.com →
Recommended fix High confidence

Upgrade to WebSphere Application Server 8.0.0.16+ (8.0 track), 8.5.5.23+ (8.5 track), or 9.0.5.14+ (9.0 track). Note: Version 7.0 reached End of Support and requires migration to a supported version.

  1. 1. Identify the current WebSphere Application Server version using the admin console or versionInfo command
  2. 2. Determine the appropriate target fix pack based on your current version: For 7.0.x, upgrade to a version beyond 7.0.0.45 (note: 7.0 is End of Support); For 8.0.x, upgrade to 8.0.0.16 or later; For 8.5.x, upgrade to 8.5.5.23 or later; For 9.0.x, upgrade to 9.0.5.14 or later
  3. 3. Obtain the fix from IBM Fix Central (https://www.ibm.com/support/fixcentral/) or the IBM Update Installer
  4. 4. Backup the current WebSphere installation and configuration before applying the update
  5. 5. Apply the fix using IBM Installation Manager or the Update Installer, following IBM's standard patching procedures
  6. 6. Restart the WebSphere Application Server after applying the fix
  7. 7. Verify the fix was applied successfully by checking the version and testing for the vulnerability
Caveat Review IBM's migration guides as upgrading between major fix pack levels may require regression testing of applications. WebSphere 7.0 is End of Life and requires full migration to a supported version (8.5 or 9.0).

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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