A missing permission check in Jenkins Azure Credentials Plugin 253.v887e0f9e898b and earlier allows attackers with Overall/Read permission to enumerate credentials IDs of credentials stored in Jenkins.

This advisory announces vulnerabilities in the following Jenkins deliverables:

*   Azure Credentials Plugin
*   Email Extension Plugin
*   JUnit Plugin
*   Pipeline: Build Step Plugin
*   Synopsys Coverity Plugin

**Descriptions****Stored XSS vulnerability in JUnit Plugin**

**SECURITY-3032 / CVE-2023-25761**  
**Severity (CVSS):** High  
**Affected plugin: junit**  
**Description:**

JUnit Plugin 1166.va\_436e268e972 and earlier does not escape test case class names in JavaScript expressions.

This results in a stored cross-site scripting (XSS) vulnerability exploitable by attackers able to control test case class names in the JUnit resources processed by the plugin.

JUnit Plugin 1166.1168.vd6b\_8042a\_06de escapes affected test case class names in JavaScript expressions.

**Stored XSS vulnerability in Pipeline: Build Step Plugin**

**SECURITY-3019 / CVE-2023-25762**  
**Severity (CVSS):** High  
**Affected plugin: pipeline-build-step**  
**Description:**

Pipeline: Build Step Plugin 2.18 and earlier does not escape job names in a JavaScript expression used in the Pipeline Snippet Generator.

This results in a stored cross-site scripting (XSS) vulnerability exploitable by attackers able to control job names.

Pipeline: Build Step Plugin 2.18.1 escapes job names in the affected JavaScript expression.

**XSS vulnerability in bundled email templates in Email Extension Plugin**

**SECURITY-2931 / CVE-2023-25763**  
**Severity (CVSS):** High  
**Affected plugin: email-ext**  
**Description:**

Email Extension Plugin bundled multiple preconfigured templates for notification emails. The Email Template Testing feature can be used to see what these and other templates would look like based on a given build.

Email Extension Plugin 2.93 and earlier does not escape various fields included in those email templates, like build display name, user display name, and the names of tests.

This results in a stored cross-site scripting (XSS) vulnerability exploitable by attackers able to control affected fields.

Email Extension Plugin 2.93.1 escapes affected fields in bundled email templates.

**Stored XSS vulnerability in custom email templates in Email Extension Plugin**

**SECURITY-2934 / CVE-2023-25764**  
**Severity (CVSS):** High  
**Affected plugin: email-ext**  
**Description:**

Email Extension Plugin allows defining custom email templates using Config File Provider plugin as Jelly or Groovy files. The Email Template Testing feature can be used to see what these templates would look like based on a given build by specifying the managed: name prefix.

Email Extension Plugin 2.93 and earlier does not escape, sanitize, or sandbox rendered email template output or log output generated during template rendering.

This results in a stored cross-site scripting (XSS) vulnerability exploitable by attackers able to create or change custom email templates.

Email Extension Plugin 2.93.1 renders email template previews inside a sandboxed iframe.

**Script Security sandbox bypass vulnerability in Email Extension Plugin**

**SECURITY-2939 / CVE-2023-25765**  
**Severity (CVSS):** High  
**Affected plugin: email-ext**  
**Description:**

Email Extension Plugin allows defining custom email templates using Config File Provider plugin as Jelly or Groovy files. When defined inside a folder, email templates need to be subject to Script Security protection (sandboxed execution or full-script approval).

In Email Extension Plugin 2.93 and earlier, templates defined inside a folder were not subject to Script Security protection.

This vulnerability allows attackers able to define email templates in folders to bypass the sandbox protection and execute arbitrary code in the context of the Jenkins controller JVM.

Email templates defined in folders are subject to sandbox protection in Email Extension Plugin 2.93.1.

**Missing permission checks in Azure Credentials Plugin allow enumerating credentials IDs**

**SECURITY-1757 / CVE-2023-25766**  
**Severity (CVSS):** Medium  
**Affected plugin: azure-credentials**  
**Description:**

Azure Credentials Plugin 253.v887e0f9e898b and earlier does not perform permission checks in several HTTP endpoints.

This allows attackers with Overall/Read permission to enumerate credentials IDs of credentials stored in Jenkins. Those can be used as part of an attack to capture the credentials using another vulnerability.

An enumeration of credentials IDs in Azure Credentials Plugin 254.v64da\_8176c83a requires Overall/Administer permission.

**CSRF vulnerability and missing permission checks in Azure Credentials Plugin**

**SECURITY-1756 / CVE-2023-25767 (CSRF), CVE-2023-25768 (missing permission check)**  
**Severity (CVSS):** Medium  
**Affected plugin: azure-credentials**  
**Description:**

Azure Credentials Plugin 253.v887e0f9e898b and earlier does not perform permission checks in methods implementing form validation.

This allows attackers with Overall/Read permission to connect to an attacker-specified web server.

Additionally, these form validation methods do not require POST requests, resulting in a cross-site request forgery (CSRF) vulnerability.

These form validation methods require POST requests and Overall/Administer permission in Azure Credentials Plugin 254.v64da\_8176c83a.

**Missing permission checks in Synopsys Coverity Plugin allow enumerating credentials IDs**

**SECURITY-2793 (1) / CVE-2023-23850**  
**Severity (CVSS):** Medium  
**Affected plugin: synopsys-coverity**  
**Description:**

Synopsys Coverity Plugin 3.0.2 and earlier does not perform permission checks in several HTTP endpoints.

This allows attackers with Overall/Read permission to enumerate credentials IDs of credentials stored in Jenkins. Those can be used as part of an attack to capture the credentials using another vulnerability.

An enumeration of credentials IDs in Synopsys Coverity Plugin 3.0.3 requires the appropriate permissions.

**CSRF vulnerability and missing permission checks in Synopsys Coverity Plugin allow capturing credentials**

**SECURITY-2793 (2) / CVE-2023-23847 (CSRF), CVE-2023-23848 (missing permission check)**  
**Severity (CVSS):** High  
**Affected plugin: synopsys-coverity**  
**Description:**

Synopsys Coverity Plugin 3.0.2 and earlier does not perform permission checks in several HTTP endpoints.

This allows attackers with Overall/Read permission to connect to an attacker-specified HTTP server using attacker-specified credentials IDs obtained through another method, capturing credentials stored in Jenkins.

Additionally, these HTTP endpoints do not require POST requests, resulting in a cross-site request forgery (CSRF) vulnerability.

Synopsys Coverity Plugin 3.0.3 requires POST requests and the appropriate permissions for the affected HTTP endpoints.

**Severity**

*   SECURITY-1756: Medium
*   SECURITY-1757: Medium
*   SECURITY-2793 (1): Medium
*   SECURITY-2793 (2): High
*   SECURITY-2931: High
*   SECURITY-2934: High
*   SECURITY-2939: High
*   SECURITY-3019: High
*   SECURITY-3032: High

**Affected Versions**

*   **Azure Credentials Plugin** up to and including 253.v887e0f9e898b
*   **Email Extension Plugin** up to and including 2.93
*   **JUnit Plugin** up to and including 1166.va\_436e268e972
*   **Pipeline: Build Step Plugin** up to and including 2.18
*   **Synopsys Coverity Plugin** up to and including 3.0.2

**Fix**

*   **Azure Credentials Plugin** should be updated to version 254.v64da\_8176c83a
*   **Email Extension Plugin** should be updated to version 2.93.1
*   **JUnit Plugin** should be updated to version 1166.1168.vd6b\_8042a\_06de
*   **Pipeline: Build Step Plugin** should be updated to version 2.18.1
*   **Synopsys Coverity Plugin** should be updated to version 3.0.3

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:

*   **Daniel Beck, CloudBees, Inc.** for SECURITY-2793 (1), SECURITY-2793 (2)
*   **Kevin Guerroudj, CloudBees, Inc.** for SECURITY-3019, SECURITY-3032
*   **Wadeck Follonier, CloudBees, Inc.** for SECURITY-1756, SECURITY-1757
*   **Yaroslav Afenkin, CloudBees, Inc.** for SECURITY-2931, SECURITY-2939
*   **Yaroslav Afenkin, CloudBees, Inc. and independently, Valdes Che Zogou** for SECURITY-2934

CVE-2023-25766: Jenkins Security Advisory 2023-02-15

A missing permission check in Jenkins Azure Credentials Plugin 253.v887e0f9e898b and earlier allows attackers with Overall/Read permission to connect to an attacker-specified web server.

CVE-2023-25768: Jenkins Security Advisory 2023-02-15

Jenkins Email Extension Plugin 2.93 and earlier does not escape various fields included in bundled email templates, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers able to control affected fields.

CVE-2023-25763: Jenkins Security Advisory 2023-02-15

In Jenkins Email Extension Plugin 2.93 and earlier, templates defined inside a folder were not subject to Script Security protection, allowing attackers able to define email templates in folders to bypass the sandbox protection and execute arbitrary code in the context of the Jenkins controller JVM.

CVE-2023-25765: Jenkins Security Advisory 2023-02-15

Jenkins Email Extension Plugin 2.93 and earlier does not escape, sanitize, or sandbox rendered email template output or log output generated during template rendering, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers able to create or change custom email templates.

CVE-2023-25764: Jenkins Security Advisory 2023-02-15

Jenkins Pipeline: Build Step Plugin 2.18 and earlier does not escape job names in a JavaScript expression used in the Pipeline Snippet Generator, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers able to control job names.

CVE-2023-25762: Jenkins Security Advisory 2023-02-15

Jenkins JUnit Plugin 1166.va_436e268e972 and earlier does not escape test case class names in JavaScript expressions, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers able to control test case class names in the JUnit resources processed by the plugin.

CVE-2023-25761: Jenkins Security Advisory 2023-02-15

A vulnerability classified as problematic was found in PHPCrazy 1.1.1. This vulnerability affects unknown code of the file admin/admin.php?action=users&mode=info&user=2. The manipulation of the argument username leads to cross site scripting. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. VDB-221086 is the identifier assigned to this vulnerability.

CVE-2023-0840

All versions of the package github.com/usememos/memos/server are vulnerable to Cross-site Scripting (XSS) due to insufficient checks on external resources, which allows malicious actors to introduce links starting with a javascript: scheme.

**Cross Site Scripting in usememos/memos**

Moderate severity GitHub Reviewed Published Feb 15, 2023 to the GitHub Advisory Database • Updated Feb 15, 2023

GHSA-9w8x-5hv5-r6gw: Cross Site Scripting in usememos/memos

@@ -38,6 +38,10 @@ func (s \*Server) registerResourceRoutes(g \*echo.Group) { }  
resourceCreate.CreatorID \= userID // Only allow those external links with http prefix. if resourceCreate.ExternalLink != "" && !strings.HasPrefix(resourceCreate.ExternalLink, "http") { return echo.NewHTTPError(http.StatusBadRequest, "Invalid external link") } resource, err := s.Store.CreateResource(ctx, resourceCreate) if err != nil { return echo.NewHTTPError(http.StatusInternalServerError, "Failed to create resource").SetInternal(err) @@ -188,13 +192,7 @@ func (s \*Server) registerResourceRoutes(g \*echo.Group) { return echo.NewHTTPError(http.StatusInternalServerError, "Failed to fetch resource").SetInternal(err) }  
c.Response().Writer.WriteHeader(http.StatusOK) c.Response().Writer.Header().Set("Content-Type", resource.Type) c.Response().Writer.Header().Set(echo.HeaderContentSecurityPolicy, "default-src 'self'") if \_, err := c.Response().Writer.Write(resource.Blob); err != nil { return echo.NewHTTPError(http.StatusInternalServerError, "Failed to write resource blob").SetInternal(err) } return nil return c.Stream(http.StatusOK, resource.Type, bytes.NewReader(resource.Blob)) })  
g.PATCH("/resource/:resourceId", func(c echo.Context) error { @@ -296,16 +294,15 @@ func (s \*Server) registerResourcePublicRoutes(g \*echo.Group) { } resource, err := s.Store.FindResource(ctx, resourceFind) if err != nil { return echo.NewHTTPError(http.StatusInternalServerError, fmt.Sprintf("Failed to fetch resource ID: %v", resourceID)).SetInternal(err) return echo.NewHTTPError(http.StatusInternalServerError, fmt.Sprintf("Failed to find resource by ID: %v", resourceID)).SetInternal(err) }  
resourceType := strings.ToLower(resource.Type) if strings.HasPrefix(resourceType, "text") || (strings.HasPrefix(resourceType, "application") && resourceType != "application/pdf") { resourceType \= echo.MIMETextPlain } c.Response().Writer.Header().Set(echo.HeaderCacheControl, "max-age=31536000, immutable") c.Response().Writer.Header().Set(echo.HeaderContentSecurityPolicy, "default-src 'self'") if strings.HasPrefix(resourceType, "video") || strings.HasPrefix(resourceType, "audio") { resourceType := strings.ToLower(resource.Type) if strings.HasPrefix(resourceType, "text") { resourceType \= echo.MIMETextPlainCharsetUTF8 } else if strings.HasPrefix(resourceType, "video") || strings.HasPrefix(resourceType, "audio") { http.ServeContent(c.Response(), c.Request(), resource.Filename, time.Unix(resource.UpdatedTs, 0), bytes.NewReader(resource.Blob)) return nil }

Tag

#xss