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.

This advisory announces vulnerabilities in the following Jenkins deliverables:

*   Jenkins (core)
*   update-center2

**Descriptions****XSS vulnerability in plugin manager**

**SECURITY-3037 / CVE-2023-27898**  
**Severity (CVSS):** High  
**Description:**

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.

**Temporary plugin file created with insecure permissions**

**SECURITY-2823 / CVE-2023-27899**  
**Severity (CVSS):** High  
**Description:**

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.

**DoS vulnerability in bundled Apache Commons FileUpload library**

**SECURITY-3030 / CVE-2023-24998 (upstream issue), CVE-2023-27900 (MultipartFormDataParser), CVE-2023-27901 (StaplerRequest)**  
**Severity (CVSS):** Medium  
**Description:**

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.

**Workspace temporary directories accessible through directory browser**

**SECURITY-1807 / CVE-2023-27902**  
**Severity (CVSS):** Medium  
**Description:**

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.

**Temporary file parameter created with insecure permissions**

**SECURITY-3058 / CVE-2023-27903**  
**Severity (CVSS):** Low  
**Description:**

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.

**Information disclosure through error stack traces related to agents**

**SECURITY-2120 / CVE-2023-27904**  
**Severity (CVSS):** Low  
**Description:**

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.

**XSS vulnerability in update-center2**

**SECURITY-3063 / CVE-2023-27905**  
**Severity (CVSS):** Medium  
**Description:**

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.

**Severity**

*   SECURITY-1807: Medium
*   SECURITY-2120: Low
*   SECURITY-2823: High
*   SECURITY-3030: Medium
*   SECURITY-3037: High
*   SECURITY-3058: Low
*   SECURITY-3063: Medium

**Affected Versions**

*   Jenkins weekly up to and including 2.393
*   Jenkins LTS up to and including 2.375.3
*   **update-center2** up to and including 3.14

**Fix**

*   Jenkins weekly should be updated to version 2.394
*   Jenkins LTS should be updated to version 2.375.4 or 2.387.1
*   **update-center2** should be updated to version 3.15

These versions include fixes to the vulnerabilities described above. All prior versions are considered to be affected by these vulnerabilities unless otherwise indicated.

**Credit**

The Jenkins project would like to thank the reporters for discovering and reporting these vulnerabilities:

*   **Ilay Goldman and Yakir Kadkoda from Aqua Security** for SECURITY-3037, SECURITY-3063
*   **Jakob Ackermann** for SECURITY-3030
*   **James Nord, CloudBees, Inc.** for SECURITY-2823
*   **Kevin Guerroudj, CloudBees, Inc.** for SECURITY-3058
*   **Markus Winter, SAP SE** for SECURITY-1807

CVE-2023-27904: Jenkins Security Advisory 2023-03-08

Jenkins update-center2 3.13 and 3.14 renders the required Jenkins core version on plugin download index pages without sanitization, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers able to provide a plugin for hosting.

CVE-2023-27905: Jenkins Security Advisory 2023-03-08

Jenkins 2.393 and earlier, LTS 2.375.3 and earlier shows temporary directories related to job workspaces, which allows attackers with Item/Workspace permission to access their contents.

CVE-2023-27902: Jenkins Security Advisory 2023-03-08

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 Security Advisory 2023-03-08

IBM Spectrum Symphony 7.3 is vulnerable to HTTP header injection, caused by improper validation of input by the HOST headers. This could allow an attacker to conduct various attacks against the vulnerable system, including cross-site scripting, cache poisoning or session hijacking. IBM X-Force ID: 247030.

CVE-2023-24975: IBM Spectrum Symphony HOST header injection CVE-2023-24975 Vulnerability Report

HCL Verse is susceptible to a Cross Site Scripting (XSS) vulnerability. By tricking a user into clicking a crafted URL, a remote unauthenticated attacker could execute script in a victim's web browser to perform operations as the victim and/or steal the victim's cookies, session tokens, or other sensitive information.

 

 Loading...

Skip to page contentSkip to chat

Skip to page contentSkip to chat

CVE-2021-27788: Knowledge Article View HCL - Customer Support

The help page in GigaVUE-FM, when using GigaVUE-OS software version 5.0 202, does not require an authenticated user. An attacker could enforce a user into inserting malicious JavaScript code into the URI, that could lead to a Reflected Cross site Scripting.

Affected resources: 

*   GigaVUE-FM with operative system GigaVUE-OS 5.0 202.

Description: 

INCIBE has coordinated the publication of a vulnerability in Gigamon GigaVUE-FM, which has been discovered by Albert Sanchez Miñano.

CVE-2023-0746 has been assigned to this vulnerability. A CVSS v3.1 base score of 6,3  has been calculated; the CVSS vector string is AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L. The vulnerability type is **CWE-79**: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting').

Solution: 

It is recommended to update to the latest available version of GigaVUE-OS.

Detail: 

The help page in GigaVUE-FM, when using GigaVUE-OS software version 5.0 202, does not require an authenticated user.  An attacker could enforce a user into inserting malicious JavaScript code into the URI, that could lead to a Reflected Cross site Scripting.

If you have any information regarding this advisory, please contact INCIBE as indicated in the 'CVE assignment and publication'.

CVE-2023-0746: XSS Vulnerability in GigaVue-FM

Cross-site Scripting (XSS) - Stored in GitHub repository osticket/osticket prior to v1.16.6.

@@ -156,9 +156,10 @@ private function updatePerms($vars, &$errors=array()) {

}

  

function update($vars, &$errors) {

if (!$vars\['name'\])

$name = Format::sanitize($vars\['name'\]);

if (!$name)

$errors\['name'\] = \_\_('Name required');

elseif (($r\=Role::lookup(array('name'\=>$vars\['name'\])))

elseif (($r\=Role::lookup(array('name'\=>$name)))

&& $r\->getId() != $vars\['id'\])

$errors\['name'\] = \_\_('Name already in use');

elseif (!$vars\['perms'\] || !count($vars\['perms'\]))

@@ -167,8 +168,8 @@ function update($vars, &$errors) {

if ($errors)

return false;

  

$this\->name = $vars\['name'\];

$this\->notes = $vars\['notes'\];

$this\->name = $name;

$this\->notes = Format::sanitize($vars\['notes'\]);

  

$this\->updatePerms($vars\['perms'\], $errors);

CVE-2023-1319: xss: Roles · osTicket/osTicket@9fb01bc

Cross-site Scripting (XSS) - Reflected in GitHub repository osticket/osticket prior to v1.16.6.

@@ -31,7 +31,7 @@ function getAdvancedSearchDialog($key=false, $context='advsearch') {

$search = new AdhocSearch(array(

'root' => 'T',

'staff\_id' => $thisstaff\->getId(),

'parent\_id' => @$\_GET\['parent\_id'\] ?: 0,

'parent\_id' => (int) @$\_GET\['parent\_id'\] ?: 0,

));

if ($search\->parent\_id) {

$search\->flags |= SavedSearch::FLAG\_INHERIT\_COLUMNS;

@@ -168,7 +168,7 @@ function createSearch() {

'title' => \_\_('Add Queue'),

'root' => 'T',

'staff\_id' => $thisstaff\->getId(),

'parent\_id' => $\_GET\['pid'\],

'parent\_id' => (int) $\_GET\['pid'\],

));

$this\->\_tryAgain($search);

}

CVE-2023-1315: xss: Search parent_id · osTicket/osTicket@ec60439

Cross-site Scripting (XSS) - Generic in GitHub repository osticket/osticket prior to v1.16.6.

@@ -366,10 +366,10 @@ function get\_db\_input($index, $vars, $quote=true) {

  

static function get\_path\_info() {

if(isset($\_SERVER\['PATH\_INFO'\]))

return $\_SERVER\['PATH\_INFO'\];

return htmlentities($\_SERVER\['PATH\_INFO'\]);

  

if(isset($\_SERVER\['ORIG\_PATH\_INFO'\]))

return $\_SERVER\['ORIG\_PATH\_INFO'\];

return htmlentities($\_SERVER\['ORIG\_PATH\_INFO'\]);

  

//TODO: conruct possible path info.

Tag

#xss