# CVE-2018-1306: Exposure of Sensitive Information in Apache Pluto

> Remote attackers can obtain sensitive configuration data via path information leakage in the Apache Pluto demo portlet file upload feature.

- **Severity:** High 7.5 (`CVSS:3.0/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:** Yes
- **Published:** 27 Jun 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-v49x-8hvm-q347

## What is CVE-2018-1306?

CVE-2018-1306 is a high-severity vulnerability in Apache Pluto, published on 27 Jun 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The PortletV3AnnotatedDemo Multipart Portlet war file code provided in Apache Pluto version 3.0.0 could allow a remote attacker to obtain sensitive information, caused by the failure to restrict path information provided during a file upload. An attacker could exploit this vulnerability to obtain configuration data and other sensitive information.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

2 open source packages ship an affected version, including org.apache.portals.pluto:pluto-container. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.apache.portals.pluto:pluto-container` | Maven | From 3.0.0 | 3.0.1 |
| `org.apache.portals.pluto:pluto-container` | Maven | From 3.0.0 | 3.0.1 |

Products: Apache Pluto.

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

Upgrade org.apache.portals.pluto:pluto-container to 3.0.1 or later.

## Is CVE-2018-1306 being exploited?

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

Public exploit code:

- Apache Portals Pluto 3.0.0 - Remote Code Execution (exploitdb)
- https://github.com/JJSO12/Apache-Pluto-3.0.0--CVE-2018-1306 (github_poc): https://github.com/JJSO12/Apache-Pluto-3.0.0--CVE-2018-1306

## Other vulnerabilities in Apache Pluto

- [CVE-2021-36737](https://insights.sbomify.com/CVE-2021-36737/): XSS in V3 Demo Portlet (medium 6.1)
- [CVE-2021-36738](https://insights.sbomify.com/CVE-2021-36738/): XSS vulnerability in the JSP version of the Apache Pluto Applicant MVCBean CDI portlet (medium 6.1)
- [CVE-2021-36739](https://insights.sbomify.com/CVE-2021-36739/): XSS vulnerability in the MVCBean JSP portlet maven archetype (medium 6.1)
- [CVE-2019-0186](https://insights.sbomify.com/CVE-2019-0186/): Cross-site Scripting in Apache Pluto Chatroom demo (medium 6.1)
- [CVE-2020-15250](https://insights.sbomify.com/CVE-2020-15250/): Information disclosure in JUnit4 (medium 4.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-1306 is a high-severity vulnerability in Apache Pluto, published on 27 Jun 2018. 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-2018-1306 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.apache.portals.pluto:pluto-container (Maven): affected from 3.0.0; fixed in 3.0.1
- org.apache.portals.pluto:pluto-container (Maven): affected from 3.0.0; fixed in 3.0.1

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

## Sources

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

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