# CVE-2025-3355: IBM Tivoli Monitoring is vulnerable to unauthenticated file read and write operations

> Remote attackers can traverse directories to read and write arbitrary files on IBM Tivoli Monitoring servers without authentication.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Oct 2025
- **Updated:** 30 Oct 2025
- **Also known as:** GHSA-vvmv-j82j-96cm

## What is CVE-2025-3355?

CVE-2025-3355 is a high-severity path traversal vulnerability in IBM Tivoli Monitoring, published on 30 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

IBM 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.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2025-3355?

It affects 1 product.


Products: Ibm Tivoli Monitoring.

## How do I fix CVE-2025-3355?

No fix has been published for CVE-2025-3355 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-3355 being exploited?

There is no known exploitation of CVE-2025-3355 in the wild and no public exploit code.

## Other vulnerabilities in IBM Tivoli Monitoring

- [CVE-2015-7411](https://insights.sbomify.com/CVE-2015-7411/): Privilege escalation in n/a (critical 9.9)
- [CVE-2025-3357](https://insights.sbomify.com/CVE-2025-3357/): IBM Tivoli Monitoring code execution (critical 9.8)
- [CVE-2017-1789](https://insights.sbomify.com/CVE-2017-1789/): Code injection in Tivoli Monitoring V6 (critical 9.8)
- [CVE-2025-3356](https://insights.sbomify.com/CVE-2025-3356/): IBM Tivoli Monitoring is vulnerable to unauthenticated file read and write operations (high 8.6)
- [CVE-2015-5003](https://insights.sbomify.com/CVE-2015-5003/): Command injection in n/a (high 8.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-3355 and fix it if it is affected.

What it is: CVE-2025-3355 is a high-severity path traversal vulnerability in IBM Tivoli Monitoring, published on 30 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-3355 in the wild and no public exploit code.

Affected product: IBM Tivoli Monitoring. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-3355/ (Markdown: https://insights.sbomify.com/CVE-2025-3355/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-3355
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-3355
- OSV: https://osv.dev/vulnerability/CVE-2025-3355

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-3355/
Summaries are generated and may contain mistakes; the official description above is the record.