https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 21:13:18 +0000 https://cve.radiocsirt.org/vuln/bdu:2024-00180 bdu:2024-00180 https://cve.radiocsirt.org/vuln/bdu:2024-00180 https://cve.radiocsirt.org/vuln/certfr-2024-avi-0225 certfr-2024-avi-0225 https://cve.radiocsirt.org/vuln/certfr-2024-avi-0225 https://cve.radiocsirt.org/vuln/euvd-2026-243603 EUVD-2026-243603 https://cve.radiocsirt.org/vuln/euvd-2026-243603 https://cve.radiocsirt.org/vuln/fkie_cve-2022-46337 <p>A cleverly devised username might bypass LDAP authentication checks. In LDAP-authenticated Derby installations, this could let an attacker fill up the disk by creating junk Derby databases. In LDAP-authenticated Derby installations, this could also allow the attacker to execute malware which was visible to and executable by the account which booted the Derby server. In LDAP-protected databases which weren&#39;t also protected by SQL GRANT/REVOKE authorization, this vulnerability could also let an attacker view and corrupt sensitive data and run sensitive database functions and procedures.</p> <p>Mitigation:</p> <p>Users should upgrade to Java 21 and Derby 10.17.1.0.</p> <p>Alternatively, users who wish to remain on older Java versions should build their own Derby distribution from one of the release families to which the fix was backported: 10.16, 10.15, and 10.14. Those are the releases which correspond, respectively, with Java LTS versions 17, 11, and 8.</p> <p>A cleverly devised username might bypass LDAP authentication checks. In LDAP-authenticated Derby installations, this could let an attacker fill up the disk by creating junk Derby databases. In LDAP-authenticated Derby installations, this could also allow the attacker to execute malware which was visible to and executable by the account which booted the Derby server. In LDAP-protected databases which weren&#39;t also protected by SQL GRANT/REVOKE authorization, this vulnerability could also let an attacker view and corrupt sensitive data and run sensitive database functions and procedures.</p> <p>Mitigation:</p> <p>Users should upgrade to Java 21 and Derby 10.17.1.0.</p> <p>Alternatively, users who wish to remain on older Java versions should build their own Derby distribution from one of the release families to which the fix was backported: 10.16, 10.15, and 10.14. Those are the releases which correspond, respectively, with Java LTS versions 17, 11, and 8.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2022-46337 https://cve.radiocsirt.org/vuln/ghsa-rcjc-c4pj-xxrp <p><strong>Affected:</strong> Maven: org.apache.derby:derby</p> <p>A cleverly devised username might bypass LDAP authentication checks. In LDAP-authenticated Derby installations, this could let an attacker fill up the disk by creating junk Derby databases. In LDAP-authenticated Derby installations, this could also allow the attacker to execute malware which was visible to and executable by the account which booted the Derby server. In LDAP-protected databases which weren&#39;t also protected by SQL GRANT/REVOKE authorization, this vulnerability could also let an attacker view and corrupt sensitive data and run sensitive database functions and procedures.</p> <p>Mitigation:</p> <p>Users should upgrade to Java 21 and Derby 10.17.1.0.</p> <p>Alternatively, users who wish to remain on older Java versions should build their own Derby distribution from one of the release families to which the fix was backported: 10.16, 10.15, and 10.14. Those are the releases which correspond, respectively, with Java LTS versions 17, 11, and 8.</p> <p><strong>Affected:</strong> Maven: org.apache.derby:derby</p> <p>A cleverly devised username might bypass LDAP authentication checks. In LDAP-authenticated Derby installations, this could let an attacker fill up the disk by creating junk Derby databases. In LDAP-authenticated Derby installations, this could also allow the attacker to execute malware which was visible to and executable by the account which booted the Derby server. In LDAP-protected databases which weren&#39;t also protected by SQL GRANT/REVOKE authorization, this vulnerability could also let an attacker view and corrupt sensitive data and run sensitive database functions and procedures.</p> <p>Mitigation:</p> <p>Users should upgrade to Java 21 and Derby 10.17.1.0.</p> <p>Alternatively, users who wish to remain on older Java versions should build their own Derby distribution from one of the release families to which the fix was backported: 10.16, 10.15, and 10.14. Those are the releases which correspond, respectively, with Java LTS versions 17, 11, and 8.</p> https://cve.radiocsirt.org/vuln/ghsa-rcjc-c4pj-xxrp https://cve.radiocsirt.org/vuln/gsd-2022-46337 gsd-2022-46337 https://cve.radiocsirt.org/vuln/gsd-2022-46337 https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-46337 <p><strong>Affected:</strong> Ubuntu:16.04:LTS: derby, Ubuntu:18.04:LTS: derby, Ubuntu:20.04:LTS: derby, Ubuntu:22.04:LTS: derby, Ubuntu:24.04:LTS: derby, Ubuntu:25.10: derby, Ubuntu:26.04:LTS: derby</p> <p>A cleverly devised username might bypass LDAP authentication checks. In LDAP-authenticated Derby installations, this could let an attacker fill up the disk by creating junk Derby databases. In LDAP-authenticated Derby installations, this could also allow the attacker to execute malware which was visible to and executable by the account which booted the Derby server. In LDAP-protected databases which weren&#39;t also protected by SQL GRANT/REVOKE authorization, this vulnerability could also let an attacker view and corrupt sensitive data and run sensitive database functions and procedures. Mitigation: Users should upgrade to Java 21 and Derby 10.17.1.0. Alternatively, users who wish to remain on older Java versions should build their own Derby distribution from one of the release families to which the fix was backported: 10.16, 10.15, and 10.14. Those are the releases which correspond, respectively, with Java LTS versions 17, 11, and 8.</p> <p><strong>Affected:</strong> Ubuntu:16.04:LTS: derby, Ubuntu:18.04:LTS: derby, Ubuntu:20.04:LTS: derby, Ubuntu:22.04:LTS: derby, Ubuntu:24.04:LTS: derby, Ubuntu:25.10: derby, Ubuntu:26.04:LTS: derby</p> <p>A cleverly devised username might bypass LDAP authentication checks. In LDAP-authenticated Derby installations, this could let an attacker fill up the disk by creating junk Derby databases. In LDAP-authenticated Derby installations, this could also allow the attacker to execute malware which was visible to and executable by the account which booted the Derby server. In LDAP-protected databases which weren&#39;t also protected by SQL GRANT/REVOKE authorization, this vulnerability could also let an attacker view and corrupt sensitive data and run sensitive database functions and procedures. Mitigation: Users should upgrade to Java 21 and Derby 10.17.1.0. Alternatively, users who wish to remain on older Java versions should build their own Derby distribution from one of the release families to which the fix was backported: 10.16, 10.15, and 10.14. Those are the releases which correspond, respectively, with Java LTS versions 17, 11, and 8.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-46337 https://cve.radiocsirt.org/vuln/wid-sec-w-2024-0537 <p>Ein entfernter anonymer Angreifer kann mehrere Schwachstellen in IBM Business Automation Workflow ausnutzen, um Sicherheitsmaßnahmen zu umgehen oder einen Denial-of-Service-Zustand zu verursachen.</p> <p>Ein entfernter anonymer Angreifer kann mehrere Schwachstellen in IBM Business Automation Workflow ausnutzen, um Sicherheitsmaßnahmen zu umgehen oder einen Denial-of-Service-Zustand zu verursachen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2024-0537