<?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>Tue, 06 Oct 2026 14:10:46 +0000</lastBuildDate>
    <item>
      <title>CVE-2020-11980</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2020-11980</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Apache Karaf&lt;/p&gt;
&lt;p&gt;In Karaf, JMX authentication takes place using JAAS and authorization takes place using ACL files. By default, only an &amp;#34;admin&amp;#34; can actually invoke on an MBean. However there is a vulnerability there for someone who is not an admin, but has a &amp;#34;viewer&amp;#34; role. In the &amp;#39;etc/jmx.acl.cfg&amp;#39;, such as role can call get*. It&amp;#39;s possible to authenticate as a viewer role + invokes on the MLet getMBeansFromURL method, which goes off to a remote server to fetch the desired MBean, which is then registered in Karaf. At this point the attack fails as &amp;#34;viewer&amp;#34; doesn&amp;#39;t have the permission to invoke on the MBean. Still, it could act as a SSRF style attack and also it essentially allows a &amp;#34;viewer&amp;#34; role to pollute the MBean registry, which is a kind of privilege escalation. The vulnerability is low as it&amp;#39;s possible to add a ACL to limit access. Users should update to Apache Karaf 4.2.9 or newer.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Apache Karaf&lt;/p&gt;
&lt;p&gt;In Karaf, JMX authentication takes place using JAAS and authorization takes place using ACL files. By default, only an &amp;#34;admin&amp;#34; can actually invoke on an MBean. However there is a vulnerability there for someone who is not an admin, but has a &amp;#34;viewer&amp;#34; role. In the &amp;#39;etc/jmx.acl.cfg&amp;#39;, such as role can call get*. It&amp;#39;s possible to authenticate as a viewer role + invokes on the MLet getMBeansFromURL method, which goes off to a remote server to fetch the desired MBean, which is then registered in Karaf. At this point the attack fails as &amp;#34;viewer&amp;#34; doesn&amp;#39;t have the permission to invoke on the MBean. Still, it could act as a SSRF style attack and also it essentially allows a &amp;#34;viewer&amp;#34; role to pollute the MBean registry, which is a kind of privilege escalation. The vulnerability is low as it&amp;#39;s possible to add a ACL to limit access. Users should update to Apache Karaf 4.2.9 or newer.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2020-11980</guid>
    </item>
  </channel>
</rss>
