CVE-2023-41935

CVE-2023-41935 is a high-severity vulnerability in Jenkins Azure Ad with a CVSS 3.x base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-697.

Key facts

Description

Jenkins 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.

Frequently asked questions

What is CVE-2023-41935?
Jenkins 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.
How severe is CVE-2023-41935?
CVE-2023-41935 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.
Is CVE-2023-41935 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (48th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2023-41935?
CVE-2023-41935 affects Jenkins Azure Ad. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2023-41935?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2023-41935 published?
CVE-2023-41935 was published on 2023-09-06 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Jenkins Azure Ad

All CVEs affecting Jenkins Azure Ad →

Other CWE-697 vulnerabilities

Browse all CWE-697 vulnerabilities →