How severe is CVE-2013-0329?

No CVSS score has been assigned to CVE-2013-0329 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2013-0329?

CVE-2013-0329 affects the following packages: org.jenkins-ci.main:jenkins-core (Maven), org.jenkins-ci.main:jenkins-core (Maven). Ecosystems affected: Maven.

How do I fix CVE-2013-0329?

Update org.jenkins-ci.main:jenkins-core to 1.502 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-0329 is resolved across your whole dependency graph.

How do I detect CVE-2013-0329 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jenkins-ci.main:jenkins-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2013-0329 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2013-0329?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2013-0329 can be triaged on real exposure rather than presence alone.

Is CVE-2013-0329 actively exploited in the wild?

No public exploit code has been indexed for CVE-2013-0329 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2013-0329?

CVE-2013-0329 has an EPSS (Exploit Prediction Scoring System) score of 2.3%, placing it in the 83th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was CVE-2013-0329 published, and has it been updated?

CVE-2013-0329 was published on May 5, 2022 and was last updated on December 3, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

CVE-2013-0329 — jenkins-core

CVE-2013-0329 is a security vulnerability in org.jenkins-ci.main:jenkins-core. A fix is available for org.jenkins-ci.main:jenkins-core — see the affected versions and patch details below.

Jenkins Cross-Site Request Forgery vulnerability

Published

May 5, 2022

Updated

Dec 3, 2024

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Sep 20, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

2.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs83th percentile — riskier than 83% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

2 pkgs affected

☕org.jenkins-ci.main:jenkins-core☕org.jenkins-ci.main:jenkins-core

Real-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

Unspecified vulnerability in Jenkins before 1.502 and LTS before 1.480.3 allows remote attackers to bypass the CSRF protection mechanism via unknown attack vectors.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.jenkins-ci.main:jenkins-core`	≥ 1.481&&< 1.502	1.502`org.jenkins-ci.main:jenkins-core:1.502`
☕Maven	`org.jenkins-ci.main:jenkins-core`	all versions	1.480.3`org.jenkins-ci.main:jenkins-core:1.480.3`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jenkins-ci.main:jenkins-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jenkins-ci.main:jenkins-core to 1.502 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-0329 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2013-0329 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2013-0329. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Product	Fixed in	Advisory
RHEL 6 Version of OpenShift Enterprise	`jenkins-0:1.502-1.el6op`	RHSA-2013:0638

Frequently Asked Questions

Unspecified vulnerability in Jenkins before 1.502 and LTS before 1.480.3 allows remote attackers to bypass the CSRF protection mechanism via unknown attack vectors.

O3 Security · Impact-Aware SCA

Is CVE-2013-0329 in your dependencies?

O3 Security finds CVE-2013-0329 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works