# CVE-2018-1230: Cross-site request forgery in Spring Batch Admin

> Remote attackers can perform unauthorized actions via CSRF due to missing protection in the end-of-life Spring Batch Admin application.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 21 Mar 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-cc6v-qwhf-8v7q

## What is CVE-2018-1230?

CVE-2018-1230 is a high-severity vulnerability in Spring Batch Admin, published on 21 Mar 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Pivotal Spring Batch Admin, all versions, does not contain cross site request forgery protection. A remote unauthenticated user could craft a malicious site that executes requests to Spring Batch Admin. This issue has not been patched because Spring Batch Admin has reached end of life.

Weakness: CWE-352 (Cross-Site Request Forgery)

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

It affects 1 product.


Products: Pivotal Software Spring Batch Admin.

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

No fix has been published for CVE-2018-1230 yet. Limit exposure of the affected software until one is available.

## Is CVE-2018-1230 being exploited?

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

## Other vulnerabilities in Spring Batch Admin

- [CVE-2018-1229](https://insights.sbomify.com/CVE-2018-1229/): Cross-site Scripting in Pivotal Spring Batch Admin (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-1230 is a high-severity vulnerability in Spring Batch Admin, published on 21 Mar 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2018-1230 in the wild and no public exploit code.

Affected product: Spring Batch Admin. No package-level version data is available, so check the vendor advisory linked from the reference page.

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

## Sources

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

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