Outdated Jenkins

The Jenkins automation server, or plugins installed on it, are older than the releases that fix publicly documented security vulnerabilities.

SeverityHigh
CVSS 3.18.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H Open in the calculator
CVSS 4.09.2 CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N Open in the calculator
CWECWE-1395: Dependency on Vulnerable Third-Party Component
OWASP Top 10A03:2025 Software Supply Chain Failures
MITRE ATT&CKT1190 Exploit Public-Facing Application, T1210 Exploitation of Remote Services
CategoryOutdated Components

Description

The Jenkins controller, or one or more of its plugins, is running a release older than the versions named in published Jenkins security advisories. Jenkins core and its large plugin ecosystem receive security fixes frequently, and the advisories regularly cover cross-site scripting, cross-site request forgery, missing permission checks and credential exposure, and at times flaws that allow files to be read or code to be run on the controller. Fixes are delivered in new weekly and Long-Term Support (LTS) releases rather than as patches for older releases, so an installation that has not been upgraded stays exposed.

Jenkins controllers usually hold credentials for source code repositories, artefact registries, cloud accounts and deployment targets, and can run code on every connected agent. Exploiting a flaw in core or a plugin may therefore let an attacker read stored secrets, run commands on the controller or its agents, alter build jobs to insert malicious code into software the organisation builds and ships, and move into the environments its pipelines deploy to. In CVE-2024-23897, for example, the command line interface parser replaced an argument beginning with @ with the contents of the named file: unauthenticated attackers could read the first lines of files on the controller, or whole files where anonymous read access was granted, and in some configurations could reach code execution using secrets read this way. Many flaws need an authenticated user, but low-privileged accounts are often easy to obtain where access is granted broadly, and the real exposure depends on the specific missing fixes, the plugins installed, whether anonymous read access or self sign-up is enabled and whether the instance faces the internet.

The core version is normally identified from the X-Jenkins HTTP response header, which Jenkins returns on most pages, or from the page footer, and is compared with the advisories. Plugin versions are not usually visible without authentication, so outdated plugins are confirmed from the plugin manager or from the security warnings that Jenkins shows administrators when an installed component is named in a published advisory. Some advisories cover plugins for which no fix has been released; these remain vulnerable however recently they were updated.

Remediation

Bring Jenkins core and every plugin up to date, and keep them there:

  • Upgrade the controller to the latest release of the LTS line, or of the weekly line if that is a deliberate choice, and update all plugins through the plugin manager in the same change window, as plugin updates often depend on a recent core. Check the Java version that the new release requires before upgrading.
  • After the upgrade, review the security warnings shown under Manage Jenkins. Remove any plugin that an advisory lists as having no fix, and any plugin that is no longer needed, as each installed plugin adds attack surface.
  • Subscribe to the Jenkins security advisories and schedule regular updates, since new advisories are published often. Test upgrades on a staging copy of the controller where builds are business-critical.

Reduce exposure while upgrades are prepared: keep the controller off the internet unless it must be reachable, restrict access to it through a VPN or an IP allowlist, disable anonymous read access and self sign-up, and block the command line interface endpoint at the reverse proxy where it is not used. If there is reason to think the instance was exploited, rotate the credentials stored in Jenkins after upgrading, as secrets read before the fix remain valid. Confirm the fix by checking the version in the X-Jenkins header and in the plugin manager against the latest advisories, and by confirming that no security warnings remain.

References


Add This Finding to Your Library

In Pental this write-up is in Settings, Library. Add to my library copies it into your own, rated in your firm's CVSS version, ready to put in your own words.

Free trial  ·  No card required

Only need the reporting? Our reporting tool is free and open source, with the same library.


More Patching and Outdated Software Findings

Every Patching and Outdated Software finding