Directory Traversal Vulnerability in Pivotal Spring Framework - libspring-java

libspring-java Updated 02 Oct 2025

Summary

20/11/2014
N/A
Yes i
Unrated
Not published

CVE-2014-3625: Directory traversal vulnerability in Pivotal Spring Framework 3.0.4 through 3.2.x before 3.2.12, 4.0.x before 4.0.8, and 4.1.x before 4.1.2 allows remote attackers to read arbitrary files via unspecified vectors, related... Affects libspring-java versions < 3.2.13-1. Fixed in 3.2.13-1. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The Pivotal Spring Framework is a powerful framework for building Java applications, providing comprehensive infrastructure support for developing Java applications. It offers features such as dependency injection, aspect-oriented programming, and transaction management. However, certain versions of the libspring-java package are vulnerable to a directory traversal issue that allows unauthorized access to arbitrary files on the server.

Vulnerability Detail

The vulnerability, identified as CVE-2014-3625, is a directory traversal flaw present in Pivotal Spring Framework versions 3.0.4 through 3.2.x before 3.2.12, 4.0.x before 4.0.8, and 4.1.x before 4.1.2. This vulnerability enables remote attackers to read sensitive files on the server by exploiting improper handling of static resources. The potential ramifications include unauthorized access to configuration files, user data, and other sensitive information, which could lead to further exploitation of the system.

How To Fix

Minimum fixed version

3.2.13-1

This is the first release that contains the fix.

sudo apt-get install --only-upgrade libspring-java

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

If an immediate upgrade is not feasible, consider restricting access to sensitive files through server configuration. For example, you can modify the web server settings to deny access to certain directories or files that should not be publicly accessible. Additionally, implementing application-level checks to validate file paths can help mitigate the risk until a proper upgrade is performed.

Conclusion

The directory traversal vulnerability in the Pivotal Spring Framework poses significant risks to applications using the libspring-java package. It is crucial for users to upgrade to the latest version to mitigate these risks. Implementing workarounds can provide temporary relief, but a proper fix is essential for long-term security.

See every vulnerability recorded for libspring-java →

Share this vulnerability

FAQ

CVE-2014-3625 is a directory traversal vulnerability in the Pivotal Spring Framework that allows attackers to read arbitrary files on the server.

The affected versions include libspring-java versions 3.0.4 through 3.2.x before 3.2.12, 4.0.x before 4.0.8, and 4.1.x before 4.1.2.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

If an immediate upgrade is not possible, consider implementing server configuration changes to restrict access to sensitive files as a temporary workaround.

The risks include unauthorized access to sensitive files, which could lead to data breaches and further exploitation of the system.

Related vulnerabilities

Recent vulnerabilities recorded for libspring-java.

How To Fix

Minimum fixed version

3.2.13-1

This is the first release that contains the fix.

sudo apt-get install --only-upgrade libspring-java

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback