dbcve.org
Servicenow DevopsApplication · Jenkins

CVE-2023-3442

HIGH · 7.5 CVSS v3.1 Published 2023-07-26
Fix available
A fix is available. Upgrade to 1.38.1 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
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.

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 confidence

A missing authorization vulnerability in the Jenkins Plug-in for ServiceNow DevOps versions prior to 1.38.1 allows unauthorized users to access sensitive information due to insufficient access controls. This is a classic broken access control (OWASP A01) vulnerability where proper authorization checks are not enforced before revealing data.

MitigationUpdate the Jenkins Plug-in for ServiceNow DevOps to version 1.38.1 or later to resolve the missing authorization check. No changes are required on ServiceNow Now Platform instances.

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
Servicenow DevopsApplication
Affected:< 1.38.1

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm the ServiceNow DevOps plugin is installed
    Navigate to Jenkins > Manage Jenkins > Manage Plugins, then click on the 'Installed' tab and search for 'Servicenow Devops' or 'ServiceNow DevOps' in the list of installed plugins
    Affected if the plugin named 'Servicenow DevOps' or 'ServiceNow DevOps' appears in the installed plugins list
  2. Retrieve the installed plugin version
    In the same plugin list (Jenkins > Manage Jenkins > Manage Plugins > Installed), locate the ServiceNow DevOps plugin and note the version number displayed in the 'Version' column
    Affected if a version number is displayed for the plugin (indicating it is installed)
  3. Compare the version against the vulnerable range
    Take the installed version number from step 2 and compare it numerically or lexicographically to version 1.38.1. For example, versions like 1.38.0, 1.37.0, 1.30.2 are all less than 1.38.1.
    Affected if the installed version is less than 1.38.1 (for example, 1.38.0, 1.37.1, 1.30.0, etc.)

The environment is affected if the ServiceNow DevOps plugin is installed and its installed version is numerically lower than 1.38.1.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 1.38.1 or later
Fixed in 1.38.1
Interim mitigation

Update the Jenkins Plug-in for ServiceNow DevOps to version 1.38.1 or later to resolve the missing authorization check. No changes are required on ServiceNow Now Platform instances.

Recommended fix High confidence

1.38.1

  1. Access your Jenkins server and log in with administrator credentials
  2. Navigate to Manage Jenkins > Manage Plugins
  3. Go to the Available tab or Installed tab
  4. Locate the 'ServiceNow DevOps' plugin
  5. Update the plugin to version 1.38.1 (or install if not present)
  6. Restart Jenkins if required for the plugin update to take effect
  7. Verify the plugin version is showing 1.38.1 in the installed plugins list
  8. No changes are required on ServiceNow Now Platform instances

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Servicenow Devops Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-3442 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-3442 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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