JenkinsApplication
CVE-2013-0329
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedUnspecified 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThis is a Cross-Site Request Forgery (CSRF) protection bypass vulnerability in Jenkins. The unspecified attack vectors allow remote attackers to circumvent the CSRF tokens that normally prevent malicious cross-site requests from being executed with an authenticated user's session.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
JenkinsApplication
<= 1.480.2<= 1.501CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Jenkins installation locationLocate the Jenkins installation: check for /var/lib/jenkins (Linux), C:\Program Files\Jenkins (Windows), or a custom installation directory. Also check if running as a service or standalone WAR file.Affected if Jenkins is installed but the location is unknown, preventing version verification.
-
Check Jenkins version via web interfaceAccess the Jenkins dashboard (typically http://localhost:8080) and look for the Jenkins version displayed at the bottom of the page, or navigate to /api/json to find the 'version' field in the JSON response.Affected if The displayed version is 1.480.2 or earlier, or 1.501 or earlier.
-
Check Jenkins version via CLI or fileIf the web interface is unavailable, check the jenkins.war file's modification date, or run 'java -jar jenkins.war --version' if the WAR file is accessible. On Linux, check /usr/share/jenkins or the installed package version with dpkg -l jenkins or rpm -q jenkins.Affected if The version command returns a version <= 1.480.2 or <= 1.501.
-
Confirm CSRF protection is in useVerify that Jenkins is running with its web UI enabled (default port 8080). CSRF protection applies to any Jenkins instance with the web interface accessible, as this is where cross-site requests could be forged.Affected if Jenkins is accessible via HTTP/HTTPS and accepts API or UI requests.
A user is affected if their Jenkins instance version is 1.480.2 or earlier, or 1.501 or earlier, and the web interface is enabled.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade Jenkins to version 1.502 or later (or LTS 1.480.3 or later) to obtain the patched CSRF protection mechanism.
Fix this in Jenkins
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-0329 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2013-0329 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data