https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 06 Oct 2026 00:58:15 +0000 https://cve.radiocsirt.org/vuln/bdu:2020-02698 bdu:2020-02698 https://cve.radiocsirt.org/vuln/bdu:2020-02698 https://cve.radiocsirt.org/vuln/bit-jenkins-2020-2162 <p><strong>Affected:</strong> Bitnami: jenkins</p> <p>Jenkins 2.227 and earlier, LTS 2.204.5 and earlier does not set Content-Security-Policy headers for files uploaded as file parameters to a build, resulting in a stored XSS vulnerability.</p> <p><strong>Affected:</strong> Bitnami: jenkins</p> <p>Jenkins 2.227 and earlier, LTS 2.204.5 and earlier does not set Content-Security-Policy headers for files uploaded as file parameters to a build, resulting in a stored XSS vulnerability.</p> https://cve.radiocsirt.org/vuln/bit-jenkins-2020-2162 https://cve.radiocsirt.org/vuln/cnvd-2020-20707 cnvd-2020-20707 https://cve.radiocsirt.org/vuln/cnvd-2020-20707 https://cve.radiocsirt.org/vuln/euvd-2026-35807 EUVD-2026-35807 https://cve.radiocsirt.org/vuln/euvd-2026-35807 https://cve.radiocsirt.org/vuln/fkie_cve-2020-2162 <p>Jenkins 2.227 and earlier, LTS 2.204.5 and earlier does not set Content-Security-Policy headers for files uploaded as file parameters to a build, resulting in a stored XSS vulnerability.</p> <p>Jenkins 2.227 and earlier, LTS 2.204.5 and earlier does not set Content-Security-Policy headers for files uploaded as file parameters to a build, resulting in a stored XSS vulnerability.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2020-2162 https://cve.radiocsirt.org/vuln/ghsa-crg2-6xv3-qg5f <p><strong>Affected:</strong> Maven: org.jenkins-ci.main:jenkins-core</p> <p>Jenkins 2.227 and earlier, LTS 2.204.5 and earlier served files uploaded as file parameters to a build without specifying appropriate `Content-Security-Policy HTTP` headers. This resulted in a stored cross-site scripting (XSS) vulnerability exploitable by users with permissions to build a job with file parameters.\n\nJenkins now sets `Content-Security-Policy` HTTP headers when serving files uploaded via a file parameter to the same value as used for files in workspaces and archived artifacts not served using the Resource Root URL.\n\nThe system property `hudson.model.DirectoryBrowserSupport.CSP` can be set to override the value of `Content-Security-Policy` headers sent when serving these files. This is the same system property used for files in workspaces and archived artifacts unless those are served via the [Resource Root URL](https://www.jenkins.io/doc/upgrade-guide/2.204/#resource-domain-support) and works the same way for file parameters. See [Configuring Content Security Policy](https://www.jenkins.io/doc/book/security/configuring-content-security-policy) to learn more.\n\nEven when Jenkins is configured to serve files in workspaces and archived artifacts using the Resource Root URL (introduced in Jenkins 2.200), file parameters are not, and therefore still subject to `Content-Security-Policy` restrictions.</p> <p><strong>Affected:</strong> Maven: org.jenkins-ci.main:jenkins-core</p> <p>Jenkins 2.227 and earlier, LTS 2.204.5 and earlier served files uploaded as file parameters to a build without specifying appropriate `Content-Security-Policy HTTP` headers. This resulted in a stored cross-site scripting (XSS) vulnerability exploitable by users with permissions to build a job with file parameters.\n\nJenkins now sets `Content-Security-Policy` HTTP headers when serving files uploaded via a file parameter to the same value as used for files in workspaces and archived artifacts not served using the Resource Root URL.\n\nThe system property `hudson.model.DirectoryBrowserSupport.CSP` can be set to override the value of `Content-Security-Policy` headers sent when serving these files. This is the same system property used for files in workspaces and archived artifacts unless those are served via the [Resource Root URL](https://www.jenkins.io/doc/upgrade-guide/2.204/#resource-domain-support) and works the same way for file parameters. See [Configuring Content Security Policy](https://www.jenkins.io/doc/book/security/configuring-content-security-policy) to learn more.\n\nEven when Jenkins is configured to serve files in workspaces and archived artifacts using the Resource Root URL (introduced in Jenkins 2.200), file parameters are not, and therefore still subject to `Content-Security-Policy` restrictions.</p> https://cve.radiocsirt.org/vuln/ghsa-crg2-6xv3-qg5f https://cve.radiocsirt.org/vuln/gsd-2020-2162 gsd-2020-2162 https://cve.radiocsirt.org/vuln/gsd-2020-2162 https://cve.radiocsirt.org/vuln/rhba-2020:2435 <p>jenkins: CSRF protection bypass via crafted URLs jenkins: XSS in job configuration pages jenkins: Content-Security-Policy headers for files uploaded leads to XSS jenkins: improperly processes HTML content of list leads to XSS</p> <p>jenkins: CSRF protection bypass via crafted URLs jenkins: XSS in job configuration pages jenkins: Content-Security-Policy headers for files uploaded leads to XSS jenkins: improperly processes HTML content of list leads to XSS</p> https://cve.radiocsirt.org/vuln/rhba-2020:2435