CVE-2018-1229 — spring-batch-admin-manager
MEDIUMCVE-2018-1229 is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in org.springframework.batch:spring-batch-admin-manager. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.
Cross-site Scripting in Pivotal Spring Batch Admin
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.springframework.batch:spring-batch-admin-managerReal-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
Pivotal Spring Batch Admin, all versions, contains a stored XSS vulnerability in the file upload feature. An unauthenticated malicious user with network access to Spring Batch Admin could store an arbitrary web script that would be executed by other users. This issue has not been patched because Spring Batch Admin has reached end of life.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.springframework.batch:spring-batch-admin-manager | all versions | No fix |
Affected Products
spring batch adminpivotal_softwareDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework.batch:spring-batch-admin-manager, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of org.springframework.batch:spring-batch-admin-manager for CVE-2018-1229. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.
Frequently Asked Questions
Is CVE-2018-1229 in your dependencies?
Find it across Maven, including transitive dependencies.