https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Wed, 30 Sep 2026 16:05:41 +0000 https://vulnerability.circl.lu/vuln/fkie_cve-2026-91048 <p>The jdbc shell command scope shipped no org.apache.karaf.command.acl.jdbc.cfg. Karaf&#39;s command guard (SecuredSessionFactoryImpl) treats a command with no matching ACL rule as allowed, so any authenticated shell session (including one holding only the viewer role) could run every jdbc:* command. jdbc:ds-create stores a fully attacker-controlled JDBC URL into a pax-jdbc-config factory Configuration with no validation. pax-jdbc-config reactively turns that into a live DataSource. Several JDBC drivers run code or SQL at connection time based on URL parameters (e.g. H2 INIT=RUNSCRIPT), so a viewer-level shell user could reach arbitrary code execution, bypassing the admin-role gate that already protects shell:exec. This is a privilege-escalation-to-RCE chain, not merely an &#34;admin misconfiguration&#34;.</p> <p>The same applies to jms:* shell commands.</p> <p>The jdbc shell command scope shipped no org.apache.karaf.command.acl.jdbc.cfg. Karaf&#39;s command guard (SecuredSessionFactoryImpl) treats a command with no matching ACL rule as allowed, so any authenticated shell session (including one holding only the viewer role) could run every jdbc:* command. jdbc:ds-create stores a fully attacker-controlled JDBC URL into a pax-jdbc-config factory Configuration with no validation. pax-jdbc-config reactively turns that into a live DataSource. Several JDBC drivers run code or SQL at connection time based on URL parameters (e.g. H2 INIT=RUNSCRIPT), so a viewer-level shell user could reach arbitrary code execution, bypassing the admin-role gate that already protects shell:exec. This is a privilege-escalation-to-RCE chain, not merely an &#34;admin misconfiguration&#34;.</p> <p>The same applies to jms:* shell commands.</p> https://vulnerability.circl.lu/vuln/fkie_cve-2026-91048 https://vulnerability.circl.lu/vuln/ghsa-pq4f-45cw-mm5m <p>The jdbc shell command scope shipped no org.apache.karaf.command.acl.jdbc.cfg. Karaf&#39;s command guard (SecuredSessionFactoryImpl) treats a command with no matching ACL rule as allowed, so any authenticated shell session (including one holding only the viewer role) could run every jdbc:* command. jdbc:ds-create stores a fully attacker-controlled JDBC URL into a pax-jdbc-config factory Configuration with no validation. pax-jdbc-config reactively turns that into a live DataSource. Several JDBC drivers run code or SQL at connection time based on URL parameters (e.g. H2 INIT=RUNSCRIPT), so a viewer-level shell user could reach arbitrary code execution, bypassing the admin-role gate that already protects shell:exec. This is a privilege-escalation-to-RCE chain, not merely an &#34;admin misconfiguration&#34;.</p> <p>The same applies to jms:* shell commands.</p> <p>The jdbc shell command scope shipped no org.apache.karaf.command.acl.jdbc.cfg. Karaf&#39;s command guard (SecuredSessionFactoryImpl) treats a command with no matching ACL rule as allowed, so any authenticated shell session (including one holding only the viewer role) could run every jdbc:* command. jdbc:ds-create stores a fully attacker-controlled JDBC URL into a pax-jdbc-config factory Configuration with no validation. pax-jdbc-config reactively turns that into a live DataSource. Several JDBC drivers run code or SQL at connection time based on URL parameters (e.g. H2 INIT=RUNSCRIPT), so a viewer-level shell user could reach arbitrary code execution, bypassing the admin-role gate that already protects shell:exec. This is a privilege-escalation-to-RCE chain, not merely an &#34;admin misconfiguration&#34;.</p> <p>The same applies to jms:* shell commands.</p> https://vulnerability.circl.lu/vuln/ghsa-pq4f-45cw-mm5m