Azure AdApplication · Jenkins
CVE-2023-41935
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 Azure AD Plugin 396.v86ce29279947 and earlier, except 378.380.v545b_1154b_3fb_, uses a non-constant time comparison function when checking whether the provided and expected CSRF protection nonce are equal, potentially allowing attackers to use statistical methods to obtain a valid nonce.
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 confidenceThe Jenkins Azure AD Plugin uses a non-constant time comparison function when validating CSRF protection nonces, allowing attackers to potentially exploit timing side-channels to deduce valid nonces through statistical analysis of response times.
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
Azure AdApplication
<= 348.vefd011eea_20b>= 378.vd6e2874a_69eb, <= 396.v86ce29279947CVSS 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
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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.
-
Confirm Azure AD Plugin is installedNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab and search for 'Azure AD', or check the plugin manifest file in JENKINS_HOME/plugins/azure-ad/Affected if The Azure AD Plugin is listed as installed
-
Identify the installed plugin versionIn Jenkins, go to Manage Jenkins > Manage Plugins > Installed tab, find Azure AD Plugin, and note the version number displayedAffected if The version is <= 348.vefd011eea_20b, OR >= 378.vd6e2874a_69eb AND <= 396.v86ce29279947
-
Verify plugin is actively configuredNavigate to Manage Jenkins > Configure Global Security or check if Azure AD authentication is configured under Manage Jenkins > Configure Global Security > Security RealmAffected if Azure AD authentication is configured and the plugin is in use as the security realm
The environment is affected if the Azure AD Plugin is installed with a version within the affected ranges AND Azure AD authentication is enabled in Jenkins security settings.
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.
dbcve · scopedUpdate the Jenkins Azure AD Plugin to version 378.380.v545b_1154b_3fb_ or later which implements constant-time comparison for nonce validation.
398.v71d5303b_3a_20 (Jenkins Azure AD Plugin)
- 1. Navigate to Manage Jenkins > Manage Plugins
- 2. Go to the 'Installed' tab and search for 'Azure AD' plugin
- 3. If the plugin is listed, check the current version number
- 4. Go to the 'Available' tab to see if a newer version is available, or check the Jenkins plugin repository directly
- 5. If version 398.v71d5303b_3a_20 or later is available, click 'Download now and install after restart'
- 6. After download completes, restart Jenkins to apply the update
- 7. Verify the plugin version has been updated to 398.v71d5303b_3a_20 or later
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Azure Ad
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.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 $1,936.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-41935 — 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-2023-41935 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