# CVE-2018-1271: Path Traversal in org.springframework:spring-core

> Attackers can read arbitrary files on Windows servers if Spring MVC is configured to serve static resources from the file system.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/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:** Yes
- **Published:** 6 Apr 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-g8hw-794c-4j9g

## What is CVE-2018-1271?

CVE-2018-1271 is a medium-severity path traversal vulnerability in Oracle Application Testing Suite, published on 6 Apr 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Spring Framework, versions 5.0 prior to 5.0.5 and versions 4.3 prior to 4.3.15 and older unsupported versions, allow applications to configure Spring MVC to serve static resources (e.g. CSS, JS, images). When static resources are served from a file system on Windows (as opposed to the classpath, or the ServletContext), a malicious user can send a request using a specially crafted URL that can lead a directory traversal attack.

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

## Which versions are affected by CVE-2018-1271?

4 open source packages ship an affected version, including org.springframework:spring-core. It affects 28 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.springframework:spring-core` | Maven | All versions | 4.3.15 |
| `org.springframework:spring-core` | Maven | All versions | 4.3.15 |
| `org.springframework:spring-core` | Maven | From 5.0.0 | 5.0.5 |
| `org.springframework:spring-core` | Maven | From 5.0.0 | 5.0.5 |

Products: Oracle Application Testing Suite, Oracle Big Data Discovery, Oracle Communications Converged Application Server, Oracle Communications Diameter Signaling Router, Oracle Communications Performance Intelligence Center, Oracle Communications Policy Management, Oracle Communications Services Gatekeeper, Oracle Enterprise Manager Ops Center, Oracle Goldengate for Big Data, Oracle Health Sciences Information Manager, Oracle Healthcare Master Person Index, Oracle Insurance Calculation Engine, Oracle Insurance Rules Palette, Oracle Primavera Gateway, Oracle Rapid Planning, Oracle Retail Back Office, Oracle Retail Central Office, Oracle Retail Customer Insights, Oracle Retail Integration Bus, Oracle Retail Open Commerce Platform and 8 more.

## How do I fix CVE-2018-1271?

Upgrade org.springframework:spring-core to a fixed version for your release line: 4.3.15 or 5.0.5.

## Is CVE-2018-1271 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-1271 exists.

Public exploit code:

- Spring MVC Framework - Local File Inclusion (nuclei): http/cves/2018/CVE-2018-1271.yaml

## Other vulnerabilities in Oracle Application Testing Suite

- [CVE-2026-35290](https://insights.sbomify.com/CVE-2026-35290/): Auth bypass in Oracle Application Testing Suite (critical 9.8)
- [CVE-2026-46876](https://insights.sbomify.com/CVE-2026-46876/): Auth bypass in Oracle Application Testing Suite (critical 9.8)
- [CVE-2026-46924](https://insights.sbomify.com/CVE-2026-46924/): Auth bypass in Oracle Application Testing Suite (critical 9.8)
- [CVE-2019-2904](https://insights.sbomify.com/CVE-2019-2904/): Auth bypass in Enterprise Repository (critical 9.8)
- [CVE-2018-1275](https://insights.sbomify.com/CVE-2018-1275/): Spring Framework has Improperly Implemented Security Check for Standard (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-1271 and fix it if it is affected.

What it is: CVE-2018-1271 is a medium-severity path traversal vulnerability in Oracle Application Testing Suite, published on 6 Apr 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-1271 exists.

Affected packages and fixed versions:
- org.springframework:spring-core (Maven): affected all versions; fixed in 4.3.15
- org.springframework:spring-core (Maven): affected all versions; fixed in 4.3.15
- org.springframework:spring-core (Maven): affected from 5.0.0; fixed in 5.0.5
- org.springframework:spring-core (Maven): affected from 5.0.0; fixed in 5.0.5

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-2018-1271/ (Markdown: https://insights.sbomify.com/CVE-2018-1271/index.md)
```

## Sources

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

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