CVE-2025-3355
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 Tivoli Monitoring 6.3.0.7 through 6.3.0.7 Service Pack 21 could allow a remote attacker to traverse directories on the system. An attacker could send a specially crafted URL request containing "dot dot" sequences (/../) to view arbitrary files on the system.
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 Tivoli Monitoring versions 6.3.0.7 through 6.3.0.7 SP21 contains a path traversal vulnerability where specially crafted URLs containing 'dot dot' sequences (/../) allow remote attackers to escape the web root and view arbitrary files on the underlying system.
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.3.0.7CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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 Tivoli Monitoring installation versionLocate the itmcmd and version files, or run 'itmcmd version' or check the installation directory for version information files typically found in $ITM_HOME or the installation rootAffected if The installed version is 6.3.0.7 or falls within the 6.3.0.7 through 6.3.0.7 SP21 range
-
Confirm the Tivoli Monitoring web server component is enabledCheck if the IBM Tivoli Monitoring web server (TEPS or Portal) is running and accessible. Look for processes like 'kfw-services' or check the configured HTTP port (typically 1920, 8080, or 443)Affected if The web server component is running and exposed on a network interface without additional access controls
-
Verify no URL validation is implemented for the web interfaceInspect the IBM Tivoli Monitoring configuration files (such as kuip.conf, httpd.conf, or custom filters) for rules that filter or block path traversal sequences like /../Affected if No URL filtering or input validation is configured to reject requests containing 'dot dot' sequences
-
Check web server logs for path traversal attemptsReview the IBM Tivoli Monitoring web server access and error logs for any requests containing /../ patterns that may indicate exploitation attemptsAffected if Recent requests with /../ sequences are present in the logs, indicating active targeting of the vulnerability
The environment is affected if IBM Tivoli Monitoring version 6.3.0.7 or any version through 6.3.0.7 SP21 is installed with the web interface exposed and no URL validation is in place to block traversal sequences.
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 IBM Tivoli Monitoring patches as they become available; meanwhile, implement URL validation and restrict web server access to prevent traversal sequences in requests.
- Consultation4.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,728.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-3355 — 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-2025-3355 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