According to its its self-reported version number, the version of Jenkins running on the remote web server is Jenkins LTS prior to 2.375.4 or Jenkins weekly prior to 2.394. It is, therefore, affected by multiple vulnerabilities:

  - Apache Commons FileUpload before 1.5 does not limit the number of request parts to be processed resulting     in the possibility of an attacker triggering a DoS with a malicious upload or series of uploads. Note     that, like all of the file upload limits, the new configuration option (FileUploadBase#setFileCountMax) is     not enabled by default and must be explicitly configured. (CVE-2023-24998)

  - High Jenkins 2.270 through 2.393 (both inclusive), LTS 2.277.1 through 2.375.3 (both inclusive) does not     escape the Jenkins version a plugin depends on when rendering the error message stating its     incompatibility with the current version of Jenkins in the plugin manager. This results in a stored cross-     site scripting (XSS) vulnerability exploitable by attackers able to provide plugins to the configured     update sites and have this message shown by Jenkins instances. Exploitation does not require the     manipulated plugin to be installed. Jenkins 2.394, LTS 2.375.4, and LTS 2.387.1 escapes the Jenkins     version a plugin depends on when rendering the error message stating its incompatibility with the current     version of Jenkins. Due to how Jenkins community update sites serve plugin metadata based on the reported     Jenkins core version, it is unlikely that a reasonably up to date Jenkins instance shows the vulnerable     error message in the plugin manager at all. At least one of the following conditions needs to be met: The     Jenkins version used is older than about 13 months (before 2.333 or LTS 2.319.2 as of publication of this     advisory), as all more recent releases of Jenkins receive update site metadata that only includes     compatible versions of plugins. Jenkins has been downgraded from a newer version, and no updated update     site metadata has been requested since, so Jenkins will still display available plugins compatible with     the previously newer version of Jenkins. Custom update site URLs (i.e., not     https://updates.jenkins.io/update-center.json) are configured, and those update sites behave differently.
    We expect that most of these will host a fairly small set of vetted plugins (e.g., an organization's     approved or internal plugins), preventing exploitation through their restrictive inclusion process.
    Jenkins community update sites no longer publish plugin releases with invalid Jenkins core dependencies     since 2023-02-15. This prevents exploitation through those update sites even on versions of Jenkins older     than 13 months. Additionally, the Jenkins security team has confirmed that no plugin release with a core     dependency manipulated to exploit this vulnerability has ever been published by the Jenkins project.
    (CVE-2023-27898)

  - High Jenkins creates a temporary file when a plugin is uploaded from an administrator's computer. Jenkins     2.393 and earlier, LTS 2.375.3 and earlier creates this temporary file in the system temporary directory     with the default permissions for newly created files. If these permissions are overly permissive, they may     allow attackers with access to the Jenkins controller file system to read and write the file before it is     installed in Jenkins, potentially resulting in arbitrary code execution. This vulnerability only affects     operating systems using a shared temporary directory for all users (typically Linux). Additionally, the     default permissions for newly created files generally only allows attackers to read the temporary file.
    Jenkins 2.394, LTS 2.375.4, and LTS 2.387.1 creates the temporary file with more restrictive permissions.
    As a workaround, you can set a different path as your default temporary directory using the Java system     property java.io.tmpdir, if you're concerned about this issue but unable to immediately update Jenkins.
    (CVE-2023-27899)

  - Medium Jenkins 2.393 and earlier, LTS 2.375.3 and earlier is affected by the Apache Commons FileUpload     library's vulnerability CVE-2023-24998. This library is used to process uploaded files via the Stapler web     framework (usually through StaplerRequest#getFile) and MultipartFormDataParser in Jenkins. This allows     attackers to cause a denial of service (DoS) by sending crafted requests to HTTP endpoints processing file     uploads. Jenkins 2.394, LTS 2.375.4, and LTS 2.387.1 limits the number of request parts to be processed to     1000. Specific endpoints receiving only simple form submissions have a lower limit. While the Apache     Commons FileUpload dependency has been updated previously in the 2.392 weekly release, the Jenkins-     specific changes in 2.394 are necessary for Jenkins to be protected. Some Jenkins forms can be very     complex, and these limits apply to all fields and not just fields representing uploaded files. As a     result, legitimate submissions of complex forms that include (possible) file uploads may be affected by     these limits. If that happens, these limits can be changed by setting the Java system properties     hudson.util.MultipartFormDataParser.FILEUPLOAD_MAX_FILES and     org.kohsuke.stapler.RequestImpl.FILEUPLOAD_MAX_FILES to a bigger value, or to -1 to completely disable     them. These releases of Jenkins also introduce additional Java system properties that can be set to     restrict request sizes: hudson.util.MultipartFormDataParser.FILEUPLOAD_MAX_FILE_SIZE and     org.kohsuke.stapler.RequestImpl.FILEUPLOAD_MAX_FILE_SIZE allow limiting the size (in bytes) of individual     fields that can be processed in one multipart/form-data request.
    hudson.util.MultipartFormDataParser.FILEUPLOAD_MAX_SIZE and     org.kohsuke.stapler.RequestImpl.FILEUPLOAD_MAX_SIZE allow limiting the total request size (in bytes) that     can be processed in one multipart/form-data request. By default, Jenkins does not set these size limits.
    Setting these system properties can offer additional protection, but comes at a greater risk of impacting     legitimate use (e.g., when uploading huge file parameters). (CVE-2023-27900, CVE-2023-27901)

  - Medium Jenkins uses temporary directories adjacent to workspace directories, usually with the @tmp name     suffix, to store temporary files related to the build. In pipelines, these temporary directories are     adjacent to the current working directory when operating in a subdirectory of the automatically allocated     workspace. Jenkins-controlled processes, like SCMs, may store credentials in these directories. Jenkins     2.393 and earlier, LTS 2.375.3 and earlier shows these temporary directories when viewing job workspaces,     which allows attackers with Item/Workspace permission to access their contents. Jenkins 2.394, LTS     2.375.4, and LTS 2.387.1 does not list these temporary directories in job workspaces. As a workaround, do     not grant Item/Workspace permission to users who lack Item/Configure permission, if you're concerned about     this issue but unable to immediately update Jenkins. The Java system property     hudson.model.DirectoryBrowserSupport.allowTmpEscape can be set to true to restore the previous behavior.
    (CVE-2023-27902)

  - Low When triggering a build from the Jenkins CLI, Jenkins creates a temporary file on the controller if a     file parameter is provided through the CLI's standard input. Jenkins 2.393 and earlier, LTS 2.375.3 and     earlier creates this temporary file in the default temporary directory with the default permissions for     newly created files. If these permissions are overly permissive, they may allow attackers with access to     the Jenkins controller file system to read and write the file before it is used in the build. This     vulnerability only affects operating systems using a shared temporary directory for all users (typically     Linux). Additionally, the default permissions for newly created files generally only allows attackers to     read the temporary file. Jenkins 2.394, LTS 2.375.4, and LTS 2.387.1 creates the temporary file with more     restrictive permissions. As a workaround, you can set a different path as your default temporary directory     using the Java system property java.io.tmpdir, if you're concerned about this issue but unable to     immediately update Jenkins. (CVE-2023-27903)

  - Low Jenkins 2.393 and earlier, LTS 2.375.3 and earlier prints an error stack trace on agent-related pages     when agent connections are broken. This stack trace may contain information about Jenkins configuration     that is otherwise inaccessible to attackers. Jenkins 2.394, LTS 2.375.4, and LTS 2.387.1 does not display     error stack traces when agent connections are broken. (CVE-2023-27904)

  - Medium update-center2 is the tool used to generate the Jenkins update sites hosted on updates.jenkins.io.
    While it is designed for use by the Jenkins project for this purpose, others may be using it to operate     their own self-hosted update sites. update-center2 3.13 and 3.14 renders the required Jenkins core version     on plugin download index pages (pages like this). This version is taken from plugin metadata without being     sanitized. This results in a stored cross-site scripting (XSS) vulnerability exploitable by attackers able     to provide a plugin for hosting. The following preconditions must both be satisfied for this to be     exploitable in a self-hosted update-center2: The generation of download pages needs to be enabled (i.e.,     the --download-links-directory argument needs to be set). A custom download page template must be used     (--index-template-url argument), and the template used must not prevent JavaScript execution through     Content-Security-Policy. The default template prevents exploitation by declaring a restrictive Content-     Security-Policy. update-center2 3.15 filters out plugin releases with invalid Jenkins core dependencies.
    Administrators hosting their own update sites using update-center2 or a fork thereof are advised to update     it, or integrate the commit 091ef999. This change has been deployed to Jenkins community update sites on     2023-02-15. The Jenkins project has distributed a single plugin release, that exploited this vulnerability     in a harmless way to demonstrate the issue, for two hours on 2023-01-16. No other plugin releases that     exploit this vulnerability have been published. (CVE-2023-27905)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote Redhat Enterprise Linux 8 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2023:3663 advisory.

    Jenkins is a continuous integration server that monitors executions of repeated jobs, such as building a     software project or jobs run by cron.

    Security Fix(es):

    * xstream: Denial of Service by injecting recursive collections or maps based on element's hash values     raising a stack overflow (CVE-2022-41966)

    * json-smart: Uncontrolled Resource Consumption vulnerability in json-smart (Resource Exhaustion)     (CVE-2023-1370)

    * springframework: Security Bypass With Un-Prefixed Double Wildcard Pattern (CVE-2023-20860)

    * log4j1-chainsaw, log4j1-socketappender: DoS via hashmap logging (CVE-2023-26464)

    * Jenkins: XSS vulnerability in plugin manager (CVE-2023-27898)

    * Jenkins: Temporary plugin file created with insecure permissions (CVE-2023-27899)

    * jenkins-2-plugin: workflow-job: Stored XSS vulnerability in Pipeline: Job Plugin (CVE-2023-32977)

    * http2-server: Invalid HTTP/2 requests cause DoS (CVE-2022-2048)

    * springframework: BCrypt skips salt rounds for work factor of 31 (CVE-2022-22976)

    * jettison: parser crash by stackoverflow (CVE-2022-40149)

    * jackson-databind: deep wrapper array nesting wrt UNWRAP_SINGLE_VALUE_ARRAYS (CVE-2022-42003)

    * jackson-databind: use of deeply nested arrays (CVE-2022-42004)

    * jettison: Uncontrolled Recursion in JSONArray (CVE-2023-1436)

    * jenkins-2-plugin: pipeline-utility-steps: Arbitrary file write vulnerability on agents in Pipeline     Utility Steps Plugin (CVE-2023-32981)

    * jettison: memory exhaustion via user-supplied XML or JSON data (CVE-2022-40150)

    * Jenkins: Temporary file parameter created with insecure permissions (CVE-2023-27903)

    * Jenkins: Information disclosure through error stack traces related to agents (CVE-2023-27904)

    For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and     other related information, refer to the CVE page(s) listed in the References section.

Tenable has extracted the preceding description block directly from the Red Hat Enterprise Linux security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote Red Hat Enterprise Linux CoreOS 4 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2023:1655 advisory.

  - Spring Security, versions 5.7 prior to 5.7.5, and 5.6 prior to 5.6.9, and older unsupported versions could     be susceptible to a privilege escalation under certain conditions. A malicious user or attacker can modify     a request initiated by the Client (via the browser) to the Authorization Server which can lead to a     privilege escalation on the subsequent approval. This scenario can happen if the Authorization Server     responds with an OAuth2 Access Token Response containing an empty scope list (per RFC 6749, Section 5.1)     on the subsequent request to the token endpoint to obtain the access token. (CVE-2022-31690)

  - Spring Security, versions 5.7 prior to 5.7.5 and 5.6 prior to 5.6.9 could be susceptible to authorization     rules bypass via forward or include dispatcher types. Specifically, an application is vulnerable when all     of the following are true: The application expects that Spring Security applies security to forward and     include dispatcher types. The application uses the AuthorizationFilter either manually or via the     authorizeHttpRequests() method. The application configures the FilterChainProxy to apply to forward and/or     include requests (e.g. spring.security.filter.dispatcher-types = request, error, async, forward, include).
    The application may forward or include the request to a higher privilege-secured endpoint.The application     configures Spring Security to apply to every dispatcher type via     authorizeHttpRequests().shouldFilterAllDispatcherTypes(true) (CVE-2022-31692)

  - A security issue was discovered in kube-apiserver that allows an aggregated API server to redirect client     traffic to any URL. This could lead to the client performing unexpected actions as well as forwarding the     client's API server credentials to third parties. (CVE-2022-3172)

  - Apache Commons Text performs variable interpolation, allowing properties to be dynamically evaluated and     expanded. The standard format for interpolation is ${prefix:name}, where prefix is used to locate an     instance of org.apache.commons.text.lookup.StringLookup that performs the interpolation. Starting with     version 1.5 and continuing through 1.9, the set of default Lookup instances included interpolators that     could result in arbitrary code execution or contact with remote servers. These lookups are: - script -     execute expressions using the JVM script execution engine (javax.script) - dns - resolve dns records -     url - load values from urls, including from remote servers Applications using the interpolation defaults     in the affected versions may be vulnerable to remote code execution or unintentional contact with remote     servers if untrusted configuration values are used. Users are recommended to upgrade to Apache Commons     Text 1.10.0, which disables the problematic interpolators by default. (CVE-2022-42889)

  - A sandbox bypass vulnerability involving map constructors in Jenkins Script Security Plugin     1228.vd93135a_2fb_25 and earlier allows attackers with permission to define and run sandboxed scripts,     including Pipelines, to bypass the sandbox protection and execute arbitrary code in the context of the     Jenkins controller JVM. (CVE-2023-24422)

  - HAProxy before 2.7.3 may allow a bypass of access control because HTTP/1 headers are inadvertently lost in     some situations, aka request smuggling. The HTTP header parsers in HAProxy may accept empty header field     names, which could be used to truncate the list of HTTP headers and thus make some headers disappear after     being parsed and processed for HTTP/1.0 and HTTP/1.1. For HTTP/2 and HTTP/3, the impact is limited because     the headers disappear before being parsed and processed, as if they had not been sent by the client. The     fixed versions are 2.7.3, 2.6.9, 2.5.12, 2.4.22, 2.2.29, and 2.0.31. (CVE-2023-25725)

  - Jenkins 2.270 through 2.393 (both inclusive), LTS 2.277.1 through 2.375.3 (both inclusive) does not escape     the Jenkins version a plugin depends on when rendering the error message stating its incompatibility with     the current version of Jenkins, resulting in a stored cross-site scripting (XSS) vulnerability exploitable     by attackers able to provide plugins to the configured update sites and have this message shown by Jenkins     instances. (CVE-2023-27898)

  - Jenkins 2.393 and earlier, LTS 2.375.3 and earlier creates a temporary file in the default temporary     directory with the default permissions for newly created files when uploading a plugin for installation,     potentially allowing attackers with access to the Jenkins controller file system to read and write the     file before it is used, potentially resulting in arbitrary code execution. (CVE-2023-27899)

  - Jenkins 2.393 and earlier, LTS 2.375.3 and earlier creates a temporary file in the default temporary     directory with the default permissions for newly created files when uploading a file parameter through the     CLI, potentially allowing attackers with access to the Jenkins controller file system to read and write     the file before it is used. (CVE-2023-27903)

  - Jenkins 2.393 and earlier, LTS 2.375.3 and earlier prints an error stack trace on agent-related pages when     agent connections are broken, potentially revealing information about Jenkins configuration that is     otherwise inaccessible to attackers. (CVE-2023-27904)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The version of Jenkins Enterprise or Jenkins Operations Center running on the remote web server is 2.346.x prior to 2.346.40.0.8. It is, therefore, affected by multiple vulnerabilities including the following:

  - DoS vulnerability in bundled Apache Commons FileUpload library (CVE-2023-24998, CVE-2023-27900,     CVE-2023-27901)

  - XSS vulnerability in plugin manager (CVE-2023-27898)

  - Temporary plugin file created with insecure permissions (CVE-2023-27899)

  - Workspace temporary directories accessible through directory browser (CVE-2023-27902)

  - Temporary file parameter created with insecure permissions (CVE-2023-27903)

  - Information disclosure through error stack traces related to agents (CVE-2023-27904)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote Redhat Enterprise Linux 7 / 8 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2023:1655 advisory.

    Red Hat OpenShift Container Platform is Red Hat's cloud computing Kubernetes application platform solution     designed for on-premise or private cloud deployments.

    This advisory contains the RPM packages for Red Hat OpenShift Container Platform 4.10.56. See the     following advisory for the container images for this release:

    https://access.redhat.com/errata/RHSA-2023:1656

    Security Fix(es):

    * apache-commons-text: variable interpolation RCE (CVE-2022-42889)

    * spring-security-oauth2-client: Privilege Escalation in spring-security-oauth2-client (CVE-2022-31690)

    * spring-security: Authorization rules can be bypassed via forward or include dispatcher types in Spring     Security (CVE-2022-31692)

    * jenkins-2-plugins/script-security: Sandbox bypass vulnerability in Script Security Plugin     (CVE-2023-24422)

    * Jenkins: XSS vulnerability in plugin manager (CVE-2023-27898)

    * Jenkins: Temporary plugin file created with insecure permissions (CVE-2023-27899)

    * kube-apiserver: Aggregated API server can cause clients to be redirected (SSRF) (CVE-2022-3172)

    * Jenkins: Temporary file parameter created with insecure permissions (CVE-2023-27903)

    * Jenkins: Information disclosure through error stack traces related to agents (CVE-2023-27904)

    For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and     other related information, refer to the CVE page(s) listed in the References section.

Tenable has extracted the preceding description block directly from the Red Hat Enterprise Linux security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

ID	Name	Product	Family	Published	Updated	Severity
172394	Jenkins LTS < 2.375.4 / Jenkins weekly < 2.394 Multiple Vulnerabilities	Nessus	CGI abuses	3/9/2023	6/4/2024	critical
194242	RHEL 8 : jenkins and jenkins-2-plugins (RHSA-2023:3663)	Nessus	Red Hat Local Security Checks	4/28/2024	11/7/2024	critical
189435	RHCOS 4 : OpenShift Container Platform 4.10.56 (RHSA-2023:1655)	Nessus	Red Hat Local Security Checks	1/24/2024	1/26/2024	critical
172368	Jenkins Enterprise and Operations Center 2.346.x < 2.346.40.0.8 Multiple Vulnerabilities (CloudBees Security Advisory 2023-03-08)	Nessus	CGI abuses	3/9/2023	6/4/2024	critical
194304	RHEL 7 / 8 : OpenShift Container Platform 4.10.56 (RHSA-2023:1655)	Nessus	Red Hat Local Security Checks	4/28/2024	11/7/2024	critical

Detections

Analytics

Plugins Search

critical

critical

critical

critical

critical