JenkinsApplication
CVE-2014-3663
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 · uneditedJenkins before 1.583 and LTS before 1.565.3 allows remote authenticated users with the Job/CONFIGURE permission to bypass intended restrictions and create or destroy arbitrary jobs via unspecified 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 confidenceJenkins before 1.583 and LTS before 1.565.3 contains an authorization bypass vulnerability where authenticated users with only Job/CONFIGURE permission (intended to allow configuring existing jobs) can bypass restrictions to create new jobs or destroy existing arbitrary jobs, enabling privilege escalation beyond intended access controls.
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.565.2<= 1.582
OpenshiftApplication
<= 3.1CVSS 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
- M
- Authentication
- Single
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:S/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 versionNavigate to Manage Jenkins > About Jenkins or run: java -jar jenkins.war --version. Alternatively, check the version displayed on the login page or in the footer of the Jenkins web interface.Affected if The installed version is Jenkins <= 1.565.2 (LTS) or Jenkins <= 1.582 (weekly release), or Openshift Enterprise/Gear 3.1 or earlier that bundles Jenkins.
-
Verify authorization strategyGo to Manage Jenkins > Configure Global Security. Check the 'Authorization' section to see which authorization strategy is selected (Matrix-based security, Project-based Matrix Authorization Strategy, or Legacy mode).Affected if Matrix-based or Project-based Matrix authorization is configured with separate Job/CONFIGURE permissions granted to users who do NOT have Job/CREATE permissions.
-
Review user permission matrixIn the authorization configuration, examine the permission matrix for each user or group. Specifically look for Job/CONFIGURE permission granted without corresponding Job/CREATE permission.Affected if Users or groups have Job/CONFIGURE permission enabled but lack Job/CREATE permission, creating the vulnerability condition.
-
Audit job creation logsCheck Jenkins logs (Manage Jenkins > System Log) and the 'audit trail' plugin if installed, for JobCreation events. Look for job creation events by users who should not have create permissions.Affected if New jobs exist that were created by users who only have Job/CONFIGURE permission in the authorization matrix.
-
Audit job deletion logsReview Jenkins logs and audit trail for Job deletion events. Look for Job/DESTROY events from users who should not have delete permissions on those jobs.Affected if Jobs have been deleted by users who only have Job/CONFIGURE permission and should not have Job/DELETE access to those jobs.
A user is affected if running Jenkins version 1.565.2 or earlier (LTS) or 1.582 or earlier (weekly), and the authorization matrix grants Job/CONFIGURE permission separately from Job/CREATE, allowing privilege escalation.
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.583 or later (or LTS 1.565.3 or later) to remediate this authorization bypass vulnerability.
Fix this in Jenkins
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing3.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 $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-3663 — 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-2014-3663 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