CVE-2018-1306 — pluto-container
HIGHCVE-2018-1306 is a high-severity (CVSS 7.5) Information Exposure vulnerability in org.apache.portals.pluto:pluto-container. 2 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for org.apache.portals.pluto:pluto-container — see the affected versions and patch details below.
Exposure of Sensitive Information in Apache Pluto
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
org.apache.portals.pluto:pluto-containerReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.apache.portals.pluto:pluto-container | ≥ 3.0.0&&< 3.0.1 | 3.0.1org.apache.portals.pluto:pluto-container:3.0.1 |
Affected Products
plutoapacheResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Apache Portals Pluto 3.0.0 - Remote Code Execution
by Che-Chun Kuo · Sep 13, 2018
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.portals.pluto:pluto-container, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.portals.pluto:pluto-container to 3.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-1306 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.
Frequently Asked Questions
Is CVE-2018-1306 in your dependencies?
Find it across Maven, including transitive dependencies.