CVE-2023-3442 is a high-severity (CVSS 7.7) CWE-862 vulnerability in io.jenkins.plugins:servicenow-devops. A fix is available for io.jenkins.plugins:servicenow-devops — see the affected versions and patch details below.
Missing Authorization in Jenkins plug-in for ServiceNow DevOps
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2023-3442.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
io.jenkins.plugins:servicenow-devopsReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
A missing authorization vulnerability exists in versions of the Jenkins Plug-in for ServiceNow DevOps prior to 1.38.1 that, if exploited successfully, could cause the unwanted exposure of sensitive information. To address this issue, apply the 1.38.1 version of the Jenkins plug-in for ServiceNow DevOps on your Jenkins server. No changes are required on your instances of the Now Platform.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | io.jenkins.plugins:servicenow-devops | all versions | 1.38.1io.jenkins.plugins:servicenow-devops:1.38.1 |
Affected Products
servicenow devopsjenkinsDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.jenkins.plugins:servicenow-devops, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update io.jenkins.plugins:servicenow-devops to 1.38.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-3442 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.
Frequently Asked Questions
Is CVE-2023-3442 in your dependencies?
Find it across Maven, including transitive dependencies.