CVE-2025-6108
BaseFortify
Publication date: 2025-06-16
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-22 | The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-6108 is a critical path traversal vulnerability in the Spring-Boot-In-Action project, specifically in the file upload function 'watermarkTest' within ImageUploadService.java. The vulnerability occurs because the 'filename' argument is not properly validated, allowing an attacker to manipulate it to traverse directories and upload files to arbitrary locations on the system. This can be exploited remotely without user interaction. [1, 2]
How can this vulnerability impact me? :
This vulnerability can impact you by allowing an attacker to place unauthorized files anywhere on your system, potentially leading to unauthorized access, modification, or deletion of files. It affects the confidentiality, integrity, and availability of your system. Since the exploit is publicly available and can be launched remotely with ease, it poses a significant security risk. [2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring for unusual or unauthorized file uploads to the /watermarktest endpoint, especially those containing path traversal patterns in the filename parameter (e.g., '../'). Network intrusion detection systems (NIDS) can be configured to alert on HTTP requests to /watermarktest with suspicious path traversal sequences. Additionally, inspecting logs for attempts to upload files with directory traversal characters can help detect exploitation attempts. For example, using command-line tools like curl to test the endpoint with crafted payloads: curl -v -X POST 'http://<target>/watermarktest' -F 'filename=../../etc/passwd' -F 'file=@testfile'. Also, searching server logs for patterns like '../' in upload requests can be done with commands such as: grep -r "../" /var/log/httpd/ or /var/log/nginx/ or application logs. [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include disabling or restricting access to the vulnerable /watermarktest file upload endpoint to prevent exploitation. If possible, replace or patch the affected component to ensure proper validation of the filename parameter to prevent path traversal. Since no vendor patch or mitigation is available, consider using alternative secure file upload solutions. Additionally, implement network-level controls such as web application firewalls (WAF) to block requests containing path traversal patterns. Monitoring and alerting on suspicious upload attempts should also be established to detect exploitation early. [2]