<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Wed, 07 Oct 2026 15:46:20 +0000</lastBuildDate>
    <item>
      <title>cnvd-2017-17220</title>
      <link>https://cve.radiocsirt.org/vuln/cnvd-2017-17220</link>
      <description>cnvd-2017-17220</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cnvd-2017-17220</guid>
    </item>
    <item>
      <title>EUVD-2026-80795</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-80795</link>
      <description>EUVD-2026-80795</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-80795</guid>
    </item>
    <item>
      <title>fkie_cve-2017-1000085</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2017-1000085</link>
      <description>&lt;p&gt;Subversion Plugin connects to a user-specified Subversion repository as part of form validation (e.g. to retrieve a list of tags). This functionality improperly checked permissions, allowing any user with Item/Build permission (but not Item/Configure) to connect to any web server or Subversion server and send credentials with a known ID, thereby possibly capturing them. Additionally, this functionality did not require POST requests be used, thereby allowing the above to be performed without direct access to Jenkins via Cross-Site Request Forgery attacks.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Subversion Plugin connects to a user-specified Subversion repository as part of form validation (e.g. to retrieve a list of tags). This functionality improperly checked permissions, allowing any user with Item/Build permission (but not Item/Configure) to connect to any web server or Subversion server and send credentials with a known ID, thereby possibly capturing them. Additionally, this functionality did not require POST requests be used, thereby allowing the above to be performed without direct access to Jenkins via Cross-Site Request Forgery attacks.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2017-1000085</guid>
    </item>
    <item>
      <title>GHSA-hrwc-pqfm-g6qf — Jenkins Subversion Plugin Cross-Site Request Forgery vulnerability</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-hrwc-pqfm-g6qf</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Maven: org.jenkins-ci.plugins:subversion&lt;/p&gt;
&lt;p&gt;Subversion Plugin connects to a user-specified Subversion repository as part of form validation (e.g. to retrieve a list of tags). This functionality improperly checked permissions, allowing any user with Item/Build permission (but not Item/Configure) to connect to any web server or Subversion server and send credentials with a known ID, thereby possibly capturing them. Additionally, this functionality did not require POST requests be used, thereby allowing the above to be performed without direct access to Jenkins via Cross-Site Request Forgery attacks. As of version 2.9, this functionality properly checks permissions and is only available via POST.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Maven: org.jenkins-ci.plugins:subversion&lt;/p&gt;
&lt;p&gt;Subversion Plugin connects to a user-specified Subversion repository as part of form validation (e.g. to retrieve a list of tags). This functionality improperly checked permissions, allowing any user with Item/Build permission (but not Item/Configure) to connect to any web server or Subversion server and send credentials with a known ID, thereby possibly capturing them. Additionally, this functionality did not require POST requests be used, thereby allowing the above to be performed without direct access to Jenkins via Cross-Site Request Forgery attacks. As of version 2.9, this functionality properly checks permissions and is only available via POST.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-hrwc-pqfm-g6qf</guid>
    </item>
    <item>
      <title>gsd-2017-1000085</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2017-1000085</link>
      <description>gsd-2017-1000085</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2017-1000085</guid>
    </item>
    <item>
      <title>RHBA-2017:2642 — Red Hat Bug Fix Advisory: OpenShift Container Platform 3.6.1 bug fix and enhancement update</title>
      <link>https://cve.radiocsirt.org/vuln/rhba-2017:2642</link>
      <description>&lt;p&gt;jenkins-plugin-subversion: CSRF vulnerability and insufficient permission checks allow capturing credentials (SECURITY-303) jenkins-plugin-pipeline-build-step: Missing check of Item/Build permission (SECURITY-433) jenkins-plugin-git: CSRF vulnerability allows capturing credentials (SECURITY-528) jenkins-plugin-workflow-cps: Arbitrary code execution due to incomplete sandbox protection (SECURITY-551)&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;jenkins-plugin-subversion: CSRF vulnerability and insufficient permission checks allow capturing credentials (SECURITY-303) jenkins-plugin-pipeline-build-step: Missing check of Item/Build permission (SECURITY-433) jenkins-plugin-git: CSRF vulnerability allows capturing credentials (SECURITY-528) jenkins-plugin-workflow-cps: Arbitrary code execution due to incomplete sandbox protection (SECURITY-551)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhba-2017:2642</guid>
    </item>
  </channel>
</rss>
