# CVE-2013-2034: Jenkins Cross-Site Request Forgery vulnerabilities

> Remote attackers can hijack administrator sessions to execute arbitrary code or deploy binaries via CSRF, requiring admin interaction.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 14 May 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-fg4r-f9j2-36mw

## What is CVE-2013-2034?

CVE-2013-2034 is a medium-severity vulnerability in n/a, published on 14 May 2014. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

Multiple cross-site request forgery (CSRF) vulnerabilities in Jenkins before 1.514, LTS before 1.509.1, and Enterprise 1.466.x before 1.466.14.1 and 1.480.x before 1.480.4.1 allow remote attackers to hijack the authentication of administrators for requests that (1) execute arbitrary code or (2) initiate deployment of binaries to a Maven repository via unspecified vectors.

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

## Which versions are affected by CVE-2013-2034?

4 open source packages ship an affected version, including org.jenkins-ci.main:jenkins-core. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jenkins-ci.main:jenkins-core` | Maven | All versions | 1.509.1 |
| `org.jenkins-ci.main:jenkins-core` | Maven | All versions | 1.509.1 |
| `org.jenkins-ci.main:jenkins-core` | Maven | From 1.513 | 1.514 |
| `org.jenkins-ci.main:jenkins-core` | Maven | From 1.513 | 1.514 |

Products: Cloudbees Jenkins.

## How do I fix CVE-2013-2034?

Upgrade org.jenkins-ci.main:jenkins-core to a fixed version for your release line: 1.509.1 or 1.514.

## Is CVE-2013-2034 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2012-0785](https://insights.sbomify.com/CVE-2012-0785/): Hash collision attack vulnerability in Jenkins (high 7.5)
- [CVE-2012-6073](https://insights.sbomify.com/CVE-2012-6073/): Jenkins affected by Open Redirect Vulnerability (medium 5.8)
- [CVE-2012-6072](https://insights.sbomify.com/CVE-2012-6072/): Jenkins allows HTTP Injection and Response Splitting (medium 4.3)
- [CVE-2012-0324](https://insights.sbomify.com/CVE-2012-0324/): Jenkins allows Cross-Site Scripting (XSS) (medium 4.3)
- [CVE-2012-0325](https://insights.sbomify.com/CVE-2012-0325/): Jenkins allows Cross-Site Scripting (XSS) (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-2034 and fix it if it is affected.

What it is: CVE-2013-2034 is a medium-severity vulnerability in n/a, published on 14 May 2014. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2013-2034 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jenkins-ci.main:jenkins-core (Maven): affected all versions; fixed in 1.509.1
- org.jenkins-ci.main:jenkins-core (Maven): affected all versions; fixed in 1.509.1
- org.jenkins-ci.main:jenkins-core (Maven): affected from 1.513; fixed in 1.514
- org.jenkins-ci.main:jenkins-core (Maven): affected from 1.513; fixed in 1.514

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

## Sources

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

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