CVE-2022-34355
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 · uneditedIBM Jazz Foundation (IBM Engineering Lifecycle Management 6.0.6, 6.0.6.1, 7.0, 7.0.1, and 7.0.2) could disclose sensitive version information to a user that could be used in further attacks against the system. IBM X-Force ID: 230498.
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 confidenceIBM Jazz Foundation is vulnerable to information disclosure through the exposure of sensitive version information. An authenticated user with low privileges could potentially access version details that could aid in identifying specific vulnerabilities for further exploitation. The CVSS 5.5 score reflects that this is an information disclosure issue with moderate confidentiality impact but no availability or integrity impact.
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= 6.0.6= 6.0.6.1= 7.0= 7.0.1= 7.0.2CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 IBM Jazz-based product installationLocate IBM Collaborative Lifecycle Management or IBM Engineering Lifecycle Management installations on your system. Common installation paths include /opt/IBM/ or C:\IBM\ on Windows servers.Affected if The product is installed in the environment
-
Determine installed CLM versionCheck the version of IBM Collaborative Lifecycle Management by examining installation manifests, About dialog in the web UI, or version files in the installation directory. Look for version files like version.ini or about.html in the installation root.Affected if Version is 6.0.6 or 6.0.6.1
-
Determine installed ELM versionCheck the version of IBM Engineering Lifecycle Management by examining installation manifests, About dialog in the web UI, or version files in the installation directory.Affected if Version is 7.0, 7.0.1, or 7.0.2
-
Verify web application accessibilityAccess the Jazz-based web application login page (typically at /jts/ or the root context of your CLM/ELM deployment) using a web browser or curl command to confirm the application is running.Affected if The web application is accessible and running an affected version
You are affected if IBM Collaborative Lifecycle Management version 6.0.6 or 6.0.6.1, or IBM Engineering Lifecycle Management version 7.0, 7.0.1, or 7.0.2 is installed and running 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.
From vendor dataApply the appropriate IBM fix pack or upgrade to a patched version of IBM Engineering Lifecycle Management as specified in the IBM security advisory. If immediate patching is not possible, implement network-level access controls to limit exposure of version information to authorized personnel only.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-34355 — 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-2022-34355 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