CSRF protection in Jenkins - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to enable CSRF protection in Jenkins configuration.

Jenkins

jenkins.security.csrf[1] = true

Drag options to blanks, or click blank then click option'

A.enable

B.crumbIssuer

C.csrf

D.protection

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect property names like '.enable' or '.csrf'.

Setting jenkins.security.csrf.crumbIssuer enables CSRF protection in Jenkins by configuring the crumb issuer.

2fill in blank

medium

Complete the code to configure the CSRF crumb issuer class in Jenkins.

Jenkins

jenkins.security.csrf.crumbIssuerClass = '[1]'

Drag options to blanks, or click blank then click option'

ADefaultCrumbIssuer

BNoCrumbIssuer

CStrictCrumbIssuer

DSimpleCrumbIssuer

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing classes that do not exist or disable CSRF protection.

The DefaultCrumbIssuer class is the standard crumb issuer for CSRF protection in Jenkins.

3fill in blank

hard

Fix the error in the Jenkins pipeline script to correctly handle CSRF protection token.

Jenkins

def crumb = jenkins.model.Jenkins.instance.crumbIssuer.[1]()
httpRequest authentication: 'token', url: 'http://example.com/api', headers: [[name: 'Jenkins-Crumb', value: crumb]]

Drag options to blanks, or click blank then click option'

AgetCrumb

BretrieveCrumb

CgenerateCrumb

DfetchCrumb

Attempts:

3 left

💡 Hint

Common Mistakes

Using method names that do not exist in Jenkins API.

The method getCrumb() is used to get the CSRF crumb token from Jenkins.

4fill in blank

hard

Fill both blanks to configure Jenkins to disable CSRF protection and set crumb exclusion.

Jenkins

jenkins.security.csrf[1] = false
jenkins.security.csrf.crumbExclusion[2] = []

Drag options to blanks, or click blank then click option'

A.csrf

B.exclude

C.exclusions

D.crumb

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect property names that cause errors.

Setting jenkins.security.csrf.csrf to false disables CSRF protection.
Setting crumbExclusion.exclusions to an empty list clears crumb exclusions.

5fill in blank

hard

Fill all three blanks to create a Jenkins pipeline step that sends a POST request with CSRF token header.

Jenkins

def crumb = jenkins.model.Jenkins.instance.crumbIssuer.[1]()
httpRequest httpMode: '[2]', url: 'http://example.com/api', headers: [[name: '[3]', value: crumb]]

Drag options to blanks, or click blank then click option'

AgetCrumb

BPOST

CJenkins-Crumb

DfetchCrumb

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong method names or header names causing request failure.

The getCrumb() method fetches the CSRF token.
The HTTP method is POST for sending data.
The header name for CSRF token is Jenkins-Crumb.

Practice

1. What is the main purpose of CSRF protection in Jenkins?

easy

A. To backup Jenkins configuration automatically

B. To speed up Jenkins build times

C. To encrypt Jenkins user passwords

D. To prevent unauthorized web requests from other sites

Solution

1. Step 1: Understand CSRF meaning

   CSRF stands for Cross Site Request Forgery, which means unauthorized commands sent from a user that the web app trusts.

2. Step 2: Identify Jenkins CSRF protection role

   Jenkins uses CSRF protection to stop these unauthorized web requests from other sites.

3. Final Answer:

   To prevent unauthorized web requests from other sites -> Option D

4. Quick Check:

   CSRF protection = prevent unauthorized requests [OK]

Hint: CSRF stops fake requests from other websites [OK]

Common Mistakes:

• Confusing CSRF with password encryption
• Thinking CSRF speeds up builds
• Assuming CSRF backs up Jenkins data

2. Which Jenkins setting enables CSRF protection?

easy

A. Enable 'Prevent Cross Site Request Forgery exploits'

B. Disable 'Prevent Cross Site Request Forgery exploits'

C. Enable 'Allow anonymous read access'

D. Disable 'Enable security'

Solution

1. Step 1: Locate CSRF protection setting

   In Jenkins global security settings, there is an option named 'Prevent Cross Site Request Forgery exploits'.

2. Step 2: Choose correct action to enable protection

   To enable CSRF protection, you must turn ON (enable) this setting.

3. Final Answer:

   Enable 'Prevent Cross Site Request Forgery exploits' -> Option A

4. Quick Check:

   Enable CSRF protection = turn on prevent exploits [OK]

Hint: Turn ON 'Prevent Cross Site Request Forgery exploits' [OK]

Common Mistakes:

• Disabling the CSRF protection setting
• Confusing with anonymous access settings
• Disabling overall security disables CSRF too

3. Given this Jenkins API call snippet:

curl -X POST http://jenkins.example.com/job/test/build \
  --header "Jenkins-Crumb: abc123" \
  --user user:token

What is the purpose of the Jenkins-Crumb header?

medium

A. It passes the CSRF protection token

B. It specifies the build job name

C. It authenticates the user credentials

D. It sets the API version

Solution

1. Step 1: Understand Jenkins-Crumb header role

   The Jenkins-Crumb header carries a token called a crumb, which Jenkins uses to verify requests are safe from CSRF attacks.

2. Step 2: Identify purpose in API call

   In API calls, this crumb token must be included to pass CSRF protection checks.

3. Final Answer:

   It passes the CSRF protection token -> Option A

4. Quick Check:

   Jenkins-Crumb = CSRF token header [OK]

Hint: Jenkins-Crumb header sends CSRF token in API calls [OK]

Common Mistakes:

• Thinking Jenkins-Crumb is user authentication
• Confusing it with job name or API version
• Omitting crumb causes CSRF errors

4. You get a 403 Forbidden error when triggering a Jenkins job via API. You suspect CSRF protection is causing it. What is the most likely fix?

medium

A. Disable CSRF protection in Jenkins settings

B. Add the Jenkins-Crumb token header to your API request

C. Use HTTP GET instead of POST for the API call

D. Increase Jenkins build timeout

Solution

1. Step 1: Identify cause of 403 error

   403 Forbidden often means Jenkins rejected the request due to missing or invalid CSRF token.

2. Step 2: Apply correct fix for CSRF error

   Adding the Jenkins-Crumb token header to the API request satisfies CSRF protection and avoids 403 errors.

3. Final Answer:

   Add the Jenkins-Crumb token header to your API request -> Option B

4. Quick Check:

   403 + CSRF = add crumb header [OK]

Hint: Add crumb header to fix 403 CSRF errors [OK]

Common Mistakes:

• Disabling CSRF protection (unsafe)
• Using GET instead of POST incorrectly
• Changing unrelated settings like timeout

5. You want to automate Jenkins job triggers from a script safely with CSRF protection enabled. Which approach is best?

hard

A. Disable CSRF protection temporarily during automation

B. Send requests without authentication but with crumb header

C. Use Jenkins API token and include the Jenkins-Crumb header in requests

D. Use HTTP GET requests to avoid CSRF checks

Solution

1. Step 1: Understand safe automation with CSRF

   Disabling CSRF protection is unsafe. Automation must authenticate and pass CSRF tokens.

2. Step 2: Combine authentication and CSRF token

   Using Jenkins API token for authentication plus including the Jenkins-Crumb header ensures safe, authorized requests.

3. Final Answer:

   Use Jenkins API token and include the Jenkins-Crumb header in requests -> Option C

4. Quick Check:

   Safe automation = auth + crumb header [OK]

Hint: Authenticate and send crumb header for safe automation [OK]

Common Mistakes:

• Disabling CSRF protection (security risk)
• Sending crumb without authentication
• Using GET to bypass CSRF (not reliable)